From: Russell King <rmk@arm.linux.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: EXT3-fs error (device ide0(3,77)) in ext3_new_inode: error 28
Date: Mon, 20 May 2002 13:51:57 +0100 [thread overview]
Message-ID: <20020520135157.A22815@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0205201400490.11918-100000@sylfest.hiof.no> <20020520131320.B22425@flint.arm.linux.org.uk>
On Mon, May 20, 2002 at 01:13:20PM +0100, Russell King wrote:
> On Mon, May 20, 2002 at 02:07:34PM +0200, Jens Christian Skibakk wrote:
> > When I unpack a tar-archive containing many files (about halv a million)
> > this errors occures in the dmesg output:
> > EXT3-fs error (device ide0(3,77)) in ext3_new_inode: error 28
>
> ENOSPC - you're out of inodes
>
> > and the program complins about: No space left on device, but df -h shows
> > that there is over 1G free on the hd.
>
> try df -i (for inodes)
>
> > After this error occurs the hd contains errors and need to be checked.
>
> That's a bug in ext3 - it has (apparantly) been fixed in the CVS version.
BTW, it might be a good idea to post the output of:
tune2fs -l <device>
(from your message above, <device> should be /dev/hdb13 ?)
I've seen one instance where mke2fs got the inode allocation wrong.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-05-20 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 12:07 EXT3-fs error (device ide0(3,77)) in ext3_new_inode: error 28 Jens Christian Skibakk
2002-05-20 12:13 ` Russell King
2002-05-20 12:51 ` Russell King [this message]
2002-05-20 12:23 ` Morten Helgesen
2002-05-20 13:40 ` Jens-Christian Skibakk
2002-05-20 13:50 ` Lionel Bouton
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=20020520135157.A22815@flint.arm.linux.org.uk \
--to=rmk@arm.linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.