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 09:55:13 -0500 [thread overview]
Message-ID: <20090121145513.GH31253@mit.edu> (raw)
In-Reply-To: <576cb9750901210619u3d2abfdclb818f0946f7bc663@mail.gmail.com>
On Wed, Jan 21, 2009 at 03:19:28PM +0100, Victor Pelt wrote:
> Hey,
>
> i tried to switch my root partition to ext4 (from reiserfs) but i ran
> into problems when copying over all the data that it says 'no space
> left on the device'
> i'm running 2.6.28-gentoo-r1 (based on 2.6.28.1 if i'm not mistaken)
>
> rootfs 5044188 4310972 476980 91% / <= file
> system that is 'full'
>
> i like to use that last 470MB if possible
>
> fsck didn't help (tried that)
If this is the problem I think it is, it's fixed in patches that were
merged for 2.6.29 (in -rc1), and you can work around it via umounting
and remounting the filesystem (or in case of the root filesystem,
rebooting).
However, when you said "fsck didn't help", what exactly did you mean
by that? That fsck didn't show any problems, when you ran it while
the filesystem was mounted? Did you actually reboot and force an
fsck, and then found that you were still getting ENOSPC errors?
I assume you have tried writing as root, and that quotas are disabled?
- Ted
P.S. If it is the problem I think it is, upgrading 2.6.29-rcX should
fix the problem, as would using the ext4-stable branch in the ext4 git
tree, or applying the patches in the for-stable branch of the ext4 git
tree:
http://git.kernel.org/?p=linux/kernel/git/tytso/ext4.git
next prev parent reply other threads:[~2009-01-21 14:55 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 [this message]
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
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=20090121145513.GH31253@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