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]

Message-ID: <4AF1D42A.6000304@redhat.com>
Date:	Wed, 04 Nov 2009 13:21:14 -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:
> Hello,
> 
> After updating my gentoo machine (new udev, lvm2) and rebooting, my initrd was 
> broken (i had CONFIG_SYSFS_DEPRECATED and CONFIG_SYSFS_DEPRECATEDV2 activated) 
> and the new udev didn't like these settings.
> So I received a warning regarding this issue. Unfortunately I had set the init 
> bootparameter to init=/sbin/bootchartd. And when i was returning from getting 
> a cup of coffee. Bootchartd was spamming my console telling me: No space left 
> on the device (or similar). When i was seeing this i had instantly a VERY bad 
> feeling about what was going on there.
> 
> So i put in the rescuecd, chrooted into my old system, built a new kernel 
> without these deprecated options, rebooted again.
> 
> This time fsck.ext4 was telling me: No such file or directory while trying to 
> open /dev/vg/root, the superblock could not be read.

This looks more like a storage problem tnan an ext4 problem.

> That's the story how I managed to corrupt my superblock and probably also it's 
> backups.

Why do you say you have a corrupted superblock?

I suppose I'd try booting a live/rescue cd, and just manually run e2fsck
against your root device, as a starter - and capture any interesting output.

Any sort of kernel or fsck logs indicating more of what actually went
wrong would be Very helpful here.

-Eric

--
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