[Top] [All Lists]

Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c

To: Linux XFS <linux-xfs@xxxxxxxxxxx>
Subject: Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c
From: Federico Sevilla III <jijo@xxxxxx>
Date: Thu, 26 Feb 2009 02:47:48 +0800
In-reply-to: <1235556051.17569.4.camel@xxxxxxxxxxxxxxxxx>
Organization: F S 3 Consulting Inc.
References: <1235480661.17293.28.camel@xxxxxxxxxxxxxxxxx> <20090224224636.GF26138@disturbed> <1235556051.17569.4.camel@xxxxxxxxxxxxxxxxx>
On Wed, 2009-02-25 at 18:00 +0800, Federico Sevilla III wrote:
> On Wed, 2009-02-25 at 09:46 +1100, Dave Chinner wrote:
> > On Tue, Feb 24, 2009 at 09:04:21PM +0800, Federico Sevilla III wrote:
> > >         attempt to access beyond end of device
> > >         sda7: rw=0, want=154858897362229008, limit=3885978852
> > >         I/O error in filesystem ("sda7") meta-data dev sda7 block 
> > > 0x2262b58bf959708       ("xfs_trans_read_buf") error 5 buf count 4096
> > 
> > A corrupted extent pointer of some kind. xfs_repair should have
> > found this. Can you run xfs_repair again? If it doesn't find
> > anything, please upgrade xfs_repair to the latest version and
> > try again.

I have attached the output of xfs_repair. You are correct, it did find
errors with the file system, and repaired them. I don't know why this
wasn't caught the first time, but I guess the lesson learned here is to
re-run xfs_repair until it finds no further errors.

Does the output of xfs_repair help give you an idea of what could have
been the root cause of the crash? (I know it's a long shot, but maybe
you recognize a pattern in the messages.)

Thank you very much.


Federico Sevilla III
F S 3 Consulting Inc.

Attachment: xfs_repair_sda7.log
Description: Text Data

Attachment: signature.asc
Description: This is a digitally signed message part

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