linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian <hiryuu@envisiongames.net>
To: linux-kernel@vger.kernel.org
Subject: Disk errors and Reiserfs
Date: Sun, 16 Sep 2001 19:29:27 -0400	[thread overview]
Message-ID: <200109162329.f8GNTY918084@demai05.mw.mediaone.net> (raw)

Device 08:11 not ready.
 I/O error: dev 08:11, sector 26908624
Device 08:11 not ready.
 I/O error: dev 08:11, sector 121208
Device 08:11 not ready.
 I/O error: dev 08:11, sector 26908624
Device 08:11 not ready.
 I/O error: dev 08:11, sector 278936
vs-13050: reiserfs_update_sd: i/o failure occurred trying to update [487 
175497 0x0 SD] stat data<6>Device 08:11 not ready.
 I/O error: dev 08:11, sector 75432
vs-13050: reiserfs_update_sd: i/o failure occurred trying to update [260 
487 0x0 SD] stat data<6>Device 08:11 not ready.
 I/O error: dev 08:11, sector 65680
journal-712: buffer write failed
kernel BUG at prints.c:332!

Basically, one of the server's drives (not the root one, though) stopped 
responding.  It seems better after a power cycle, but it definately 
appeared to be a hardware problem.

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.

You can't kill the processes; you can't unmount the partition; you 
consequently can't reboot the box in any normal manner.  The box was in a 
pretty broken, unusable state.

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?

Thank you
	-- Brian

             reply	other threads:[~2001-09-16 23:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-16 23:29 Brian [this message]
2001-09-17  0:40 ` Disk errors and Reiserfs Alan Cox
2001-09-17  2:32   ` Brian
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=200109162329.f8GNTY918084@demai05.mw.mediaone.net \
    --to=hiryuu@envisiongames.net \
    --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).