From: Theodore Tso <tytso@mit.edu>
To: Victor Pelt <victor.pelt@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext4 no space left
Date: Wed, 21 Jan 2009 15:46:46 -0500 [thread overview]
Message-ID: <20090121204645.GB9088@mit.edu> (raw)
In-Reply-To: <576cb9750901211015g3c8813e6md7c0cdd88b9dada1@mail.gmail.com>
On Wed, Jan 21, 2009 at 07:15:26PM +0100, Victor Pelt wrote:
> upgrading to 2.6.29-rc2-git1 did allow me to use most of the space but
> i still can't quite use all of it. maybe this is to be expected.
No, it's not to be expected. You should be able to use everything up
to 100% of what is reported by df. There is the 5% reserved blocks
which only root is allowed to use, but df takes that into account. So
if you can't use that last 62944k reported by df after a reboot, and
df -i reports enough inodes, that's definitely a bug in ext4.
Would you be willing to send me a compressed raw e2image file? You
can generate it as follows:
e2image -r /dev/hda2 - | bzip2 > /tmp/hda2.e2i.bz2
Ideally this should be done while the filesystem is unmounted, or
mounted read-only.
It will give me a copy of the filesystem metadata, but no data blocks.
That will allow me to try to replicate the problem on my system. It
will probably be still too large e-mail, so if you can put it up on
some web or ftp server, and send me the URL, that would be best.
Thanks!!
- Ted
next prev parent reply other threads:[~2009-01-21 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 14:19 ext4 no space left Victor Pelt
2009-01-21 14:55 ` Theodore Tso
2009-01-21 15:18 ` Victor Pelt
2009-01-21 17:04 ` Theodore Tso
2009-01-21 18:15 ` Victor Pelt
2009-01-21 20:46 ` Theodore Tso [this message]
2009-01-27 10:53 ` Pavel Machek
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=20090121204645.GB9088@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=victor.pelt@gmail.com \
/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