RE: XFS SB Validate error

["Yom, Francis" <fyom@symmsys.com>]

Hi Eric,

Here is the relevant info from syslog:

Jan 31 17:21:09 sera kernel: EFSCORRUPTED returned from file
xfs_ialloc.c line 1265

Jan 31 17:21:09 sera kernel: xfs_force_shutdown(ide0(3,9),0x8) called
from line 1020 of file xfs_trans.c.  Return address = 0xc02256df

Jan 31 17:21:09 sera gconfd (0fyom-1211): Failed to delete old file
'/home/users/0fyom/.gconf/apps/galeon/State/prefs_dialog/%gconf.xml.old'
: Unknown error 990

Jan 31 17:21:09 sera gconfd (0fyom-1211): Failed to log removal of
listener to logfile (most likely harmless, may result in a notification
weirdly reappearing): Failed:  Failed to open gconfd logfile; won't be
able to restore listeners after gconfd shutdown (Input/output error)

Jan 31 17:21:09 sera kernel: Corruption of in-memory data detected.
Shutting down filesystem: ide0(3,9)

Jan 31 17:21:09 sera kernel: Please umount the filesystem, and rectify
the problem(s)

Jan 31 17:21:09 sera gconfd (0fyom-1211): Failed to log removal of
listener to logfile (most likely harmless, may result in a notification
weirdly reappearing): Failed:  Failed to open gconfd logfile; won't be
able to restore listeners after gconfd shutdown (Input/output error)


Let me know what you think.  Many thanks for your quick reply!

Francis

-----Original Message-----
From: Eric Sandeen [mailto:sandeen@sgi.com] 
Sent: Thursday, January 31, 2002 9:38 PM
To: Yom, Francis
Cc: linux-xfs@oss.sgi.com; lord@sgi.com; spstarr@sh0n.net
Subject: Re: XFS SB Validate error


On Thu, 31 Jan 2002, Yom, Francis wrote:

> I have been very happy with XFS and had no problems with it so far.  I

> have been using this kernel for 2 weeks now, but have been working 
> with XFS since 2.4.14.  Today, while working in my XP VMWare session, 
> I got an error saying that VMWare could not contact the disk drive.  I

> went to an X console and checked my syslog and discovered that my 
> /home partition (3,9) was unmounted my XFS because of a bad 
> superblock.  I had the dreaded SB Validate problem as stated in the 
> FAQ.

Were there any messages in the log about a forced filesystem shutdown?

-Eric

Jan 31 17:21:09 sera kernel: EFSCORRUPTED returned from file xfs_ialloc.c line 1265
Jan 31 17:21:09 sera kernel: xfs_force_shutdown(ide0(3,9),0x8) called from line 1020 of file xfs_trans.c.  Return address = 0xc02256df
Jan 31 17:21:09 sera gconfd (0fyom-1211): Failed to delete old file ‘/home/users/0fyom/.gconf/apps/galeon/State/prefs_dialog/%gconf.xml.old’: Unknown error 990
Jan 31 17:21:09 sera gconfd (0fyom-1211): Failed to log removal of listener to logfile (most likely harmless, may result in a notification weirdly reappearing): Failed:  Failed to open gconfd logfile; won’t be able to restore listeners after gconfd shutdown (Input/output error)
Jan 31 17:21:09 sera kernel: Corruption of in-memory data detected.  Shutting down filesystem: ide0(3,9)
Jan 31 17:21:09 sera kernel: Please umount the filesystem, and rectify the problem(s)
Jan 31 17:21:09 sera gconfd (0fyom-1211): Failed to log removal of listener to logfile (most likely harmless, may result in a notification weirdly reappearing): Failed:  Failed to open gconfd logfile; won’t be able to restore listeners after gconfd shutdown (Input/output error)
Jan 31 17:22:19 sera named[296]: Cleaned cache of 0 RRsets