linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Pavel Machek <pavel@suse.cz>,
	viro@math.psu.edu, kernel list <linux-kernel@vger.kernel.org>
Cc: torvalds@transmeta.com
Subject: Re: [patch] linux likes to kill bad inodes
Date: Wed, 25 Apr 2001 09:29:53 -0400	[thread overview]
Message-ID: <302200000.988205393@tiny> (raw)
In-Reply-To: <20010422141042.A1354@bug.ucw.cz>



On Sunday, April 22, 2001 02:10:42 PM +0200 Pavel Machek <pavel@suse.cz>
wrote:

> 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?

-chris


  reply	other threads:[~2001-04-25 13:30 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 [this message]
2001-04-25 20:01   ` Pavel Machek
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 23:22   ` Linus Torvalds
2001-04-30 22:33 ` David S. Miller
     [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=302200000.988205393@tiny \
    --to=mason@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).