xfs
[Top] [All Lists]

Re: easily reproducible filesystem crash on rebuilding array

To: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
Subject: Re: easily reproducible filesystem crash on rebuilding array
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Sat, 20 Dec 2014 10:06:05 +1100
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20141219125720.56c5f74d@xxxxxxxxxxxxxx>
References: <20141211123936.1f3d713d@xxxxxxxxxxxxxxxxxxxx> <20141215130715.4dfaaa8e@xxxxxxxxxxxxxxxxxxxx> <20141215132500.13210fdb@xxxxxxxxxxxxxxxxxxxx> <20141215201036.GQ24183@dastard> <20141216123405.111c7ac0@xxxxxxxxxxxxxxxxxxxx> <20141216195815.GB15665@dastard> <20141218164042.15220bf3@xxxxxxxxxxxxxxxxxxxx> <20141218225843.GB24183@dastard> <20141219125720.56c5f74d@xxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Fri, Dec 19, 2014 at 12:57:20PM +0100, Emmanuel Florac wrote:
> Le Fri, 19 Dec 2014 09:58:43 +1100 vous écriviez:
> 
> > 
> > Where's the XFS error output? This is just the output from the
> > dump_stack() call in the xfs error message code...
> 
> Where is it supposed to display its errors? I thought it to be
> in /var/log/messages....

Depends on how you system is configured. have you turned down the
dmesg error level?

> > Still, that's implying a write IO error being reporte din IO
> > completion, not a read error, and that's different to the previous
> > issue you've reported. It's also indicative of an error coming from
> > the storage, not XFS...
> >
> > Do these problems *only* happen during or after a RAID rebuild?
> 
> Only while the rebuild process is running. All works fine afterwards.

Which pretty much points to a RAID controller rebuild bug.

> > > Phase 7 - verify and correct link counts...
> > > resetting inode 4294866029 nlinks from 2 to 5
> > > resetting inode 150323855504 nlinks from 13 to 12
> > > Metadata corruption detected at block 0x10809dc640/0x1000
> > > libxfs_writebufr: write verifer failed on bno 0x10809dc640/0x1000
> > > Metadata corruption detected at block 0x10809dc640/0x1000
> > > libxfs_writebufr: write verifer failed on bno 0x10809dc640/0x1000
> > > done
> > 
> > I'd suggest you should be upgrading xfsprogs, because that's an
> > error that shouldn't happen at the end of a repair. If the latest
> > version (3.2.2) doesn't fix this problem, then please send me a
> > compressed metadump so I can work out what corruption xfs_repair
> > isn't fixing properly.
> 
> It was 3.2.2 this time. However it seems to have fixe it anyway;
> running it a second time displays nothing special.
> Is a metadump of a clean filesystem of any use?

Not really.

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

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