From: Theodore Tso <tytso@mit.edu>
To: Alex Buell <alex.buell@munted.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fw: 2.6.27 & ext4 strangeness
Date: Fri, 30 Jan 2009 19:09:17 -0500 [thread overview]
Message-ID: <20090131000917.GB27950@mit.edu> (raw)
In-Reply-To: <20090130194702.5a2ca774@lithium.local.net>
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
next prev parent reply other threads:[~2009-01-31 4:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 19:47 Fw: 2.6.27 & ext4 strangeness Alex Buell
2009-01-31 0:09 ` Theodore Tso [this message]
2009-01-31 10:05 ` Alex Buell
2009-02-03 14:54 ` Alex Buell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090131000917.GB27950@mit.edu \
--to=tytso@mit.edu \
--cc=alex.buell@munted.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox