From: Rolf Eike Beer <eike@bilbo.math.uni-mannheim.de>
To: Robert Love <rml@tech9.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.5: ext3 bug or dying drive?
Date: Fri, 6 Dec 2002 08:01:06 +0100 [thread overview]
Message-ID: <200212060801.06566@bilbo.math.uni-mannheim.de> (raw)
In-Reply-To: 1039123660.1433.12.camel@phantasy
Von Robert Love:
> Overnight, 2.5.50-mm1 took a big stinky shit:
[bad things]
> Nothing particularly interesting was going on (mostly idle X desktop).
> I woke up and noticed the fs was mounted ro. The above was in dmesg.
>
> Rebooted and ext3 replayed the journal and said a manual check was
> needed due to I/O error on the journal. Ran fsck manually, it found a
> whole bunch of orphan inodes including some scary errors like "inode
> part of corrupt orphan inode list" or similar.
>From at least (IIRC) 2.5.46 on I'm getting wrong free block counts in inodes
if I'm writing to discs. Looks like it must be a bit more than just 2 or 20
files, a kernel compile is enough in most cases. It's happening on 2
different hosts, one with SCSI, the other one with IDE. Nothing really bad
has happend until today. But if I can't create new files on a filesystem with
2 GB of free space I know it's time for an "e2fsck -f" on it.
Eike
prev parent reply other threads:[~2002-12-06 6:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 21:27 2.5: ext3 bug or dying drive? Robert Love
2002-12-05 22:03 ` Andrew Morton
2002-12-05 22:12 ` Robert Love
2002-12-05 22:21 ` Robert Love
2002-12-06 1:03 ` Barry K. Nathan
2002-12-06 7:01 ` Rolf Eike Beer [this message]
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=200212060801.06566@bilbo.math.uni-mannheim.de \
--to=eike@bilbo.math.uni-mannheim.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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