xfs-masters
[Top] [All Lists]

[xfs-masters] Re: [Ext2-devel] Re: [RFD] FS behavior (I/O failure) in ke

To: Hans Reiser <reiser@xxxxxxxxxxx>
Subject: [xfs-masters] Re: [Ext2-devel] Re: [RFD] FS behavior (I/O failure) in kernel summit
From: Pavel Machek <pavel@xxxxxx>
Date: Thu, 16 Jun 2005 23:27:28 +0200
Cc: "Theodore Ts'o" <tytso@xxxxxxx>, Kenichi Okuyama <okuyamak@xxxxxxxxxxxxxx>, Andreas Dilger <adilger@xxxxxxxxxxxxx>, fs <fs@xxxxxxxxxxxxxxxxxx>, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, linux-kernel <linux-kernel@xxxxxxxxxxxxxxx>, zhiming@xxxxxxxxxxxxxxxxx, qufuping@xxxxxxxxxxxxxxxxxx, madsys@xxxxxxxxxxxxxxxxxx, xuh@xxxxxxxxxxxxxx, koichi@xxxxxxxxxxxxxxxxx, kuroiwaj@xxxxxxxxxxxxxxxxx, okuyama@xxxxxxxxxxxxxxxxx, matsui_v@xxxxxxxxxxxxx, kikuchi_v@xxxxxxxxxxxxx, fernando@xxxxxxxxxxxxxxxxx, kskmori@xxxxxxxxxxxxxxxxx, takenakak@xxxxxxxxxxxxxxxxx, yamaguchi@xxxxxxxxxxxxxxxxx, ext2-devel@xxxxxxxxxxxxxxxxxxxxx, shaggy@xxxxxxxxxxxxxx, xfs-masters@xxxxxxxxxxx, Reiserfs developers mail-list <Reiserfs-Dev@xxxxxxxxxxx>
In-reply-to: <42B091E3.3010908@xxxxxxxxxxx>
References: <1118692436.2512.157.camel@CoolQ> <42ADC99D.5000801@xxxxxxxxxxx> <20050613201315.GC19319@xxxxxxxxxxxxxxxxxxxxx> <42AE1D4A.3030504@xxxxxxxxxxx> <42AE450C.5020908@xxxxxxxxxxxxxx> <20050615140105.GE4228@xxxxxxxxx> <42B091E3.3010908@xxxxxxxxxxx>
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.9i
Hi!

> >Kenichi-San,
> >
> >Part of the problem is that we are limited by the constraints of the
> >POSIX specification for error handling. 
> >
> Ted, if I understand you correctly, I agree with you.  ;-)
> 
> What users need is for a window to pop up saying "the usb drive is
> turned off" or "we are getting checksum errors from XXX, this may
> indicate hardware problems that require your attention".
> 
> Now that GUIs exist, and now that more errors are possible because the
> kernel is more complex, perhaps kernel error handling should be
> reconsidered.  I don't have the feeling that anyone has felt themselves
> authorized to take a deep look at how this ought to be designed.  I mean
> sure, there are sometimes console windows that things get printed into,
> but unsophisticated users basically want to be prompted if something

I believe syslog can handle this just fine. Just add some gui code to
watch syslog, and if high-enough (KERN_CRIT?) message happens, display
that message to user.

...which brings interesting question of "how to internationalize this
beast", but list of KERN_CRIT messages should be reasonably small.

                                                                Pavel
-- 
teflon -- maybe it is a trademark, but it should not be.


<Prev in Thread] Current Thread [Next in Thread>