[Top] [All Lists]

Re: force_shutdown experienced

To: linux-xfs@xxxxxxxxxxx
Subject: Re: force_shutdown experienced
From: Robert Sander <robert.sander@xxxxxxxxxxxxxxx>
Date: Fri, 15 Mar 2002 14:47:12 +0100
In-reply-to: <3C91F99A.5000704@xxxxxxx>
References: <news2mail-slrna93h06.1rn.gurubert-news@xxxxxxxxxxxxxxxxxxxxx> <3C91F99A.5000704@xxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.3.27i
On Fri, Mar 15, 2002 at 07:39:38AM -0600, Stephen Lord wrote:
> Well, two things happened to you - the forced shutdown, and the bug 
> which Ralf Bergs
> mentioned. That bug was fixed on Jan 17th - a current cvs kernel should 
> get you around
> that one. The bug caused the superblock to get overwritten after forced 
> shutdown.

I have heard (or better read) of the bug, but did not correlate the two.

> Note if you get the new kernel and you use ACLs you need new user space 
> utilities to go with the kernel.

Or I compile the compatability layer into the kernel. How is that

> I would unmount the filesystem and run xfs_check on it to verify it is 
> clean, but repair should have handled everything.

Yes, filesystem looks good.

> I do not think we will be able to determine the cause of the memory 
> corruption from the information we have here.

I wish I could. The machine is a Dell PowerEdge 2550 with an onboard
Perc 3/Di (the famous aacraid) and an external HW-RAID box connected via
normal Adaptec SCSI controller.

Robert Sander
Department Head
Information Systems        www.epigenomics.com        Kastanienallee 24
+493024345330                                              10435 Berlin

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