public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: xfs@oss.sgi.com
Subject: Re: easily reproducible filesystem crash on rebuilding array
Date: Sat, 20 Dec 2014 10:06:05 +1100	[thread overview]
Message-ID: <20141219230605.GF24183@dastard> (raw)
In-Reply-To: <20141219125720.56c5f74d@galadriel.home>

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@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-12-19 23:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 11:39 easily reproducible filesystem crash on rebuilding array Emmanuel Florac
2014-12-11 15:52 ` Eric Sandeen
2014-12-15 12:07 ` Emmanuel Florac
2014-12-15 12:25   ` Emmanuel Florac
2014-12-15 20:10     ` Dave Chinner
2014-12-16  7:56       ` Christoph Hellwig
2014-12-16 11:38         ` Emmanuel Florac
2014-12-16 17:21           ` Emmanuel Florac
2014-12-16 11:34       ` Emmanuel Florac
2014-12-16 19:58         ` Dave Chinner
2014-12-17 11:21           ` Emmanuel Florac
2014-12-18 15:40           ` Emmanuel Florac
2014-12-18 22:58             ` Dave Chinner
2014-12-19 11:57               ` Emmanuel Florac
2014-12-19 23:06                 ` Dave Chinner [this message]
2014-12-16 11:08     ` easily reproducible filesystem crash on rebuilding array [XFS bug in my book] Emmanuel Florac
2014-12-16 20:04       ` Dave Chinner
2015-01-13 11:21 ` easily reproducible filesystem crash on rebuilding array Emmanuel Florac
2015-01-13 13:59   ` Emmanuel Florac
     [not found] <CAH-PCH7W4yTDRhAiKQwN_wQJMx2sTitQYrLNPcLYHvJRucXBjA@mail.gmail.com>
2015-09-17  6:17 ` Emmanuel Florac
2015-09-17  7:21   ` Ferenc Kovacs
2015-09-17 11:17     ` Emmanuel Florac

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141219230605.GF24183@dastard \
    --to=david@fromorbit.com \
    --cc=eflorac@intellique.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox