linux-kernel - Re: Fw: 2.6.27 & ext4 strangeness

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: <20090131000917.GB27950@mit.edu>
Date:	Fri, 30 Jan 2009 19:09:17 -0500
From:	Theodore Tso <tytso@....edu>
To:	Alex Buell <alex.buell@...ted.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Fw: 2.6.27 & ext4 strangeness

On Fri, Jan 30, 2009 at 07:47:02PM +0000, Alex Buell wrote:
> 
> As this has happened three times in the last 24 hours, I thought I'd
> report this. Whenever my laptop locks up, I have to powercycle. After
> rebooting, and fsck.ext4 reports a clean filesystem, often I get a 'no
> space on device' error even though I have plenty of disk space left.
> Another reboot with a forced fsck.ext4 cures this, every time. This only
> happens with ext4 filesystems used as the root filesystem. 

If you can reproduce this, can you send me the output of "df /; df -i
/; dumpe2fs /dev/XXX" (where XXX is your root device) before you
reboot and force an fsck?  And then can you send me the output of "df
/ ; df -i /; dumpe2fs /dev/XXX" after the 2nd reboot and forced fsck.
I've never seen anything like this, so I don't know what to make of it.

It also would be interesting to see if you can reproduce it running a
kernel from the ext4-stable branch of the ext4 tree:

   git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
   http://git.kernel.org/?p=linux/kernel/git/tytso/ext4.git

This has all of the ext4 fixes that is in the latest mainline, based
on the 2.6.28 kernel.

Thanks for reporting your observations,

							- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/