linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian <hiryuu@envisiongames.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Disk errors and Reiserfs
Date: Sun, 16 Sep 2001 22:32:18 -0400	[thread overview]
Message-ID: <200109170232.f8H2WM901390@demai05.mw.mediaone.net> (raw)
In-Reply-To: <E15imSi-00068f-00@the-village.bc.nu>
In-Reply-To: <E15imSi-00068f-00@the-village.bc.nu>

On Sunday 16 September 2001 08:40 pm, Alan Cox wrote:
> > My issue, though, is Linux did not handle it well.  Userspace actually
> > has an 'EIO' error code for this situation but, instead, any program
> > touching the mounted partition hung in a D state.
>
> Thats a reiserfs property and one you'll find in pretty much any other
> fs.

Is that the best approach?  Userspace doesn't always handle EIO well, but 
it can't do much worse than a permanent deadlock.

> > Is it possible for the kernel to handle this with enough grace that
> > you can kill the processes and unmount the partition?  (Thus allowing
> > the box to continue in a hobbled, but function manner.)  Failing that,
> > is it possible for the kernel to handle it well enough for 'shutdown'
> > to cleanly shutdown the box?
>
> Killing the process isnt neccessary, its been halted in its tracks. As
> to a clean shutdown - no chance. You've just hit a disk failure, the on
> disk state is not precisely known, writes have been lost. Nothing is
> going to make a clean shutdown possible under such circumstances.

Let me rephrase: cleanish.  At least enough to let 'shutdown' actually 
shutdown and surviving filesystems to unmount cleanly.  I guess this would 
require all file ops to that filesystem to return EIO and umount would 
drop the filesystem as-is.

	-- Brian

  reply	other threads:[~2001-09-17  2:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-16 23:29 Disk errors and Reiserfs Brian
2001-09-17  0:40 ` Alan Cox
2001-09-17  2:32   ` Brian [this message]
2001-09-17 10:45   ` Guus Sliepen
2001-09-18 10:17   ` Stephen C. Tweedie

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=200109170232.f8H2WM901390@demai05.mw.mediaone.net \
    --to=hiryuu@envisiongames.net \
    --cc=alan@lxorguk.ukuu.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 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).