Date: Tue, 27 Jan 2009 11:53:38 +0100
From: Pavel Machek <pavel@suse.cz>
To: Theodore Tso <tytso@mit.edu>, Victor Pelt <victor.pelt@gmail.com>,
       linux-kernel@vger.kernel.org
Subject: Re: ext4 no space left
Message-ID: <20090127105338.GA21011@elf.ucw.cz>
References: <576cb9750901210619u3d2abfdclb818f0946f7bc663@mail.gmail.com> <20090121145513.GH31253@mit.edu> <576cb9750901210718u32aa98ecy87e7298a0f3444f@mail.gmail.com> <20090121170423.GJ31253@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090121170423.GJ31253@mit.edu>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1171
Lines: 24

On Wed 2009-01-21 12:04:23, Theodore Tso wrote:
> On Wed, Jan 21, 2009 at 04:18:35PM +0100, Victor Pelt wrote:
> > i set the number mounted counter to 31, which forced fsck to run on
> > the next reboot. I rebooted, fsck didn't show any erros, but i still
> > got the no space left error when i tried to copy files to the
> > partition.
> 
> OK, if a reboot didn't help, I'll bet I know what happened.  E2fsprogs
> changed the default default inode ratio, which means that number of
> inodes being created is half what it was previously.  If you do a "df
> -i", you'll probably see that you have exhausted the number of inodes
> in the filesystem.

Actually it would be cool if df warned about low inode free space by
default. "df -i" is an old trap, but still effective to these days
:-).
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/