From: Russell King <rmk+ext3@arm.linux.org.uk>
To: Alec Smith <alec@shadowstar.net>
Cc: linux-kernel@vger.kernel.org, ext3-users@redhat.com
Subject: Re: ext3 corruption
Date: Fri, 12 Jul 2002 16:52:33 +0100 [thread overview]
Message-ID: <20020712165233.B10576@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0207121127001.7507-100000@bugs.home.shadowstar.net>; from alec@shadowstar.net on Fri, Jul 12, 2002 at 11:32:44AM -0400
On Fri, Jul 12, 2002 at 11:32:44AM -0400, Alec Smith wrote:
> Over the last month or so, I've noticed the following error showing up
> repeatedly in my system logs under kernel 2.4.18-ac3 and more recently
> under 2.4.19-rc1:
>
> EXT3-fs error (device ide0(3,3)) in ext3_new_inode: error 28
Erm, that looks like the old "out of inodes, return -ENOSPC and mark the
filesystem read only" bug I found several months ago. iirc, there have
been 3 recent issues (in the last three months) that I'm aware of:
1. running out of free blocks.
2. running out of free inodes.
3. i_nlink accounting goofup.
I've got patches from akpm for (1) and (3), but not (2). I'd be nice to
have all three solved for 2.4.19.
--
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-07-12 15:49 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 15:32 ext3 corruption Alec Smith
2002-07-12 15:52 ` Russell King [this message]
2002-07-12 19:51 ` Andrew Morton
2002-07-12 16:02 ` Alan Cox
[not found] <Pine.LNX.4.33.0207121337500.8654-100000@coffee.psychology.mcmaster.ca>
2002-07-12 19:05 ` Alec Smith
2002-07-12 20:11 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2006-07-13 20:32 Molle Bestefich
2006-08-08 23:47 ` Molle Bestefich
2006-08-09 1:33 ` Sergio Monteiro Basto
2006-08-09 10:36 ` Molle Bestefich
2006-08-09 11:33 ` linux-os (Dick Johnson)
2006-08-09 15:22 ` Molle Bestefich
2006-08-09 15:38 ` Michael Loftis
2006-08-09 18:28 ` Molle Bestefich
2006-08-09 18:41 ` Mws
2006-08-09 20:17 ` Duane Griffin
2006-08-09 20:47 ` Molle Bestefich
[not found] ` <e9e943910608091527t3b88da7eo837f6adc1e1e6f98@mail.gmail.com>
2006-08-09 23:09 ` Molle Bestefich
2006-08-10 0:08 ` Duane Griffin
2006-08-10 21:00 ` Molle Bestefich
2006-08-12 16:38 ` Theodore Tso
2006-08-12 17:24 ` Molle Bestefich
2006-08-12 21:47 ` Theodore Tso
2006-08-13 19:21 ` Molle Bestefich
2006-08-14 3:23 ` Kyle Moffett
2006-08-14 15:34 ` Theodore Tso
2006-08-14 17:21 ` Molle Bestefich
2006-08-10 3:06 ` Jim Crilly
2006-08-10 9:48 ` Molle Bestefich
2006-08-10 11:41 ` linux-os (Dick Johnson)
2006-08-10 12:21 ` Molle Bestefich
2006-08-10 12:19 ` Helge Hafting
2006-08-10 13:00 ` Molle Bestefich
2006-08-10 14:40 ` gmu 2k6
2006-09-24 8:56 ` Molle Bestefich
2006-09-25 12:27 ` Helge Hafting
2006-10-02 2:40 ` Molle Bestefich
2006-10-02 3:24 ` Gene Heskett
2006-10-02 6:50 ` Kyle Moffett
2006-08-10 16:10 ` John Stoffel
2006-08-10 19:10 ` Molle Bestefich
2006-08-11 8:06 ` Helge Hafting
2006-08-11 13:26 ` Horst H. von Brand
2006-08-12 8:54 ` Molle Bestefich
2006-08-12 10:31 ` Molle Bestefich
2006-08-17 1:27 ` Horst H. von Brand
2006-08-17 13:46 ` Molle Bestefich
2006-08-10 8:32 ` Bernd Petrovitsch
2006-08-10 7:44 ` Denis Vlasenko
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=20020712165233.B10576@flint.arm.linux.org.uk \
--to=rmk+ext3@arm.linux.org.uk \
--cc=alec@shadowstar.net \
--cc=ext3-users@redhat.com \
--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.