public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: David Zafman <david.zafman@inktank.com>
Cc: ceph-devel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: RESEND: xattr issue with 3.11 kernel
Date: Sat, 5 Oct 2013 07:04:11 +1000	[thread overview]
Message-ID: <20131004210411.GJ4446@dastard> (raw)
In-Reply-To: <ED5C1C84-614E-4EBB-A966-BBCD9CE89373@inktank.com>

On Fri, Oct 04, 2013 at 01:48:17PM -0700, David Zafman wrote:
> 
> <<Plain Text>>
> 
> This was also seen on a customized 3.10 kernel, but didn't reproduce on the Ubuntu 13.04 packaged 3.8 kernel.
> 
> $ cat /etc/issue
> Ubuntu 13.04 \n \l
> $ uname -a
> Linux ubuntu 3.11.0-031100-generic #201309021735 SMP Mon Sep 2 21:36:21 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> $ mount | grep /mnt
> /dev/sdb on /mnt type xfs (rw)
> $ ./xattr-test.sh /mnt/foo 10240
> 8
> 16
> 32
> 64
> 128
> 256
> 512
> 1024
> 2048
> setfattr: /mnt/foo: Structure needs cleaning
> failure to remove user.test1557
> 
> ffff88003a005000: 46 c4 4f 2f 00 00 06 b5 46 c4 4f a6 00 00 06 b4  F.O/....F.O.....
> ffff88003a005010: 46 c4 4f a7 00 00 06 b3 46 c4 4f a8 00 00 06 b2  F.O.....F.O.....
> ffff88003a005020: 46 c4 4f a9 00 00 06 b1 46 c4 4f aa 00 00 06 b0  F.O.....F.O.....
> ffff88003a005030: 46 c4 4f ab 00 00 06 af 46 c4 4f ac 00 00 06 ae  F.O.....F.O.....
> XFS (sdb): Internal error xfs_da_do_buf(2) at line 2694 of file /home/apw/COD/linux/fs/xfs/xfs_da_btree.c.  Caller 0xffffffffa0304423
> 
> CPU: 0 PID: 35058 Comm: setfattr Not tainted 3.11.0-031100-generic #201309021735
> Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/31/2013
>  0000000000000001 ffff8800354ab9f8 ffffffff81720fca 0000000000000007
>  ffff88003a27b800 ffff8800354aba18 ffffffffa02cd27f ffffffffa0304423
>  0000000000000001 ffff8800354aba58 ffffffffa02cd2ee 0000000000000002
> Call Trace:
>  [<ffffffff81720fca>] dump_stack+0x46/0x58
>  [<ffffffffa02cd27f>] xfs_error_report+0x3f/0x50 [xfs]
>  [<ffffffffa0304423>] ? xfs_da3_node_read+0x23/0xd0 [xfs]
>  [<ffffffffa02cd2ee>] xfs_corruption_error+0x5e/0x90 [xfs]
>  [<ffffffffa030438a>] xfs_da_read_buf+0x1ba/0x230 [xfs]
>  [<ffffffffa0304423>] ? xfs_da3_node_read+0x23/0xd0 [xfs]
>  [<ffffffffa0332127>] ? xfs_trans_log_buf+0x97/0x100 [xfs]
>  [<ffffffffa0304423>] xfs_da3_node_read+0x23/0xd0 [xfs]
>  [<ffffffffa030608c>] xfs_da3_blk_unlink.isra.13+0x16c/0x1e0 [xfs]
>  [<ffffffffa030633f>] xfs_da3_join+0x9f/0x240 [xfs]
>  [<ffffffffa02e6872>] xfs_attr_node_removename+0x192/0x300 [xfs]

You are probably hitting the problem fixed in commit 997def2 ("xfs:
fix node forward in xfs_node_toosmall") which went into 3.12-rc3.
Can you test that this fixes your problem, ad if so, we'll need to
push it back to -stable kernels..

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2013-10-04 21:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 20:48 RESEND: xattr issue with 3.11 kernel David Zafman
2013-10-04 21:04 ` Dave Chinner [this message]
2013-10-04 22:16   ` David Zafman
2013-10-05  3:21     ` Dave Chinner
2013-10-07 20:38       ` Ben Myers

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=20131004210411.GJ4446@dastard \
    --to=david@fromorbit.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=david.zafman@inktank.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