From: Pavel Machek <pavel@suse.cz>
To: Chris Mason <mason@suse.com>,
viro@math.psu.edu, kernel list <linux-kernel@vger.kernel.org>,
jack@atrey.karlin.mff.cuni.cz
Cc: torvalds@transmeta.com
Subject: Re: [patch] linux likes to kill bad inodes
Date: Wed, 25 Apr 2001 22:01:20 +0200 [thread overview]
Message-ID: <20010425220120.A1540@bug.ucw.cz> (raw)
In-Reply-To: <20010422141042.A1354@bug.ucw.cz> <302200000.988205393@tiny>
In-Reply-To: <302200000.988205393@tiny>; from Chris Mason on Wed, Apr 25, 2001 at 09:29:53AM -0400
Hi!
> > Hi!
> >
> > I had a temporary disk failure (played with acpi too much). What
> > happened was that disk was not able to do anything for five minutes
> > or so. When disk recovered, linux happily overwrote all inodes it
> > could not read while disk was down with zeros -> massive disk
> > corruption.
> >
> > Solution is not to write bad inodes back to disk.
> >
>
> Wouldn't we rather make it so bad inodes don't get marked dirty at all?
I guess this is cheaper: we can mark inode dirty at 1000 points, but
you only write it at one point.
But I'm no FS expert.
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
next prev parent reply other threads:[~2001-04-25 20:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-22 12:10 [patch] linux likes to kill bad inodes Pavel Machek
2001-04-25 13:29 ` Chris Mason
2001-04-25 20:01 ` Pavel Machek [this message]
2001-04-25 20:28 ` Chris Mason
2001-04-26 9:28 ` Pavel Machek
2001-04-26 9:33 ` Jan Kara
2001-04-26 22:28 ` Pavel Machek
2001-04-27 14:36 ` Chris Mason
2001-04-27 22:07 ` Andreas Dilger
2001-04-27 22:14 ` Linus Torvalds
2001-04-30 22:28 ` Alan Cox
2001-04-30 22:33 ` David S. Miller
2001-04-30 23:22 ` Linus Torvalds
[not found] <no.id>
2001-04-27 23:30 ` Andreas Dilger
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=20010425220120.A1540@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=jack@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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.