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: Helge Hafting <helge.hafting@xxxxxxxxxxxxx>
Date: Thu, 16 Jun 2005 13:52:59 +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: Debian Thunderbird 1.0.2 (X11/20050602)
Hans Reiser wrote:

>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".
>  
>
Nice.  And the way to do this right is to have the kernel merely
log the error as usual.  The user can have some daemon listening
to the log, this program may then pop up error messages with
nifty detailed explanations, start up diagnostic software
for various subsystems and so on. 

The kernel can't do GUI stuff - a GUI may or may not be present,
and the kernel cannot know.  The server may not run X at all
but I still run graphical SW on it using a workstation or X-terminal.
Or the pc may have three video cards, each running a different xserver
with different users for each.  Who to report to?

An error-reporting daemon have an easier job, it can look up the
correct (possibly remote) display in its config file for all those
cases when there isn't just _one_ display.

Helge Hafting





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