All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: Metadata corruption detected at xfs_attr3_leaf_write_verify / Internal error xfs_attr3_leaf_write_verify
Date: Tue, 8 Dec 2015 16:14:15 -0600	[thread overview]
Message-ID: <56675637.2050608@sandeen.net> (raw)
In-Reply-To: <20151208205759.GE19802@dastard>



On 12/8/15 2:57 PM, Dave Chinner wrote:
> On Tue, Dec 08, 2015 at 04:20:01PM +0100, Dietmar Putz wrote:
>> similar reports are existing :
>> http://oss.sgi.com/archives/xfs/2015-11/msg00459.html
>> https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1468039
> 
> Following a  couple of clicky links in that bug leads to:
> 
> http://oss.sgi.com/archives/xfs/2015-06/msg00457.html
> 
> in which I comment:
> 
> | Probably fixed by commit c88547a ("xfs: fix directory hash ordering
> | bug"), which also affected attributes in leaf format.
> 
> Hence this was probably fixed in 3.15 and pushed back to 3.13.11i
> via th eupstream stable kernel process. I have no idea if the ubuntu
> maintainers have added that fix to their kernel...

But:

> After upgrade to kernel 3.19.0-39 the error message turns from "Internal error xfs_attr3_leaf_write_verify...." to 
> "Metadata corruption detected at xfs_attr3_leaf_write_verify..." as shown below for gluster-ger-ber-11-int.

and that's 3.19 ...?  (and repair found nothing on-disk?)

-Eric

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

  reply	other threads:[~2015-12-08 22:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 15:20 Metadata corruption detected at xfs_attr3_leaf_write_verify / Internal error xfs_attr3_leaf_write_verify Dietmar Putz
2015-12-08 17:01 ` Eric Sandeen
2015-12-08 20:57 ` Dave Chinner
2015-12-08 22:14   ` Eric Sandeen [this message]
2015-12-08 22:52     ` Dave Chinner

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=56675637.2050608@sandeen.net \
    --to=sandeen@sandeen.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.