linux-ext4 - Re: Corrupt superblocks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 04 Nov 2009 16:24:04 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	fabian-buettner@....de
CC:	linux-ext4@...r.kernel.org
Subject: Re: Corrupt superblocks

fabian-buettner@....de wrote:

> So maybe i did harm my fs by running e2fsck -b?

If /dev/vg/root didn't exist, no filesystem was harmed in the process I
am sure.  :)

> Because running fsck afterwards gave me a lot of those Group descriptor 
> checksum fixing proposals?
> I am surprised that e2fsck just told me that my fs is clean.
> 
> Do you have a clue why an entry in my /etc/fsab like
> /dev/vg/root            /               ext4            noatime         0 0

This tells the initscripts not to try running fsck on /dev/vg/root at
all (see man fstab)

> works, while
> /dev/vg/root            /               ext4            noatime         0 1
> doesnt?

These are probably questions for your distribution; it sounds like the
initscripts are not able to point e2fsck at the proper device, at the
proper time...

-Eric

> - fabian

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html