From: David Arendt <admin@prnet.org>
To: bo.li.liu@oracle.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: extended attributes wiredness
Date: Tue, 27 Nov 2012 20:20:54 +0100 [thread overview]
Message-ID: <50B51296.3010103@prnet.org> (raw)
In-Reply-To: <20121127074625.GA31592@liubo.cn.oracle.com>
Hi,
I have now tested a gentoo reinstall with a recompile of nfs-utils. By
observing how the directory /var/lib/nfs is created, I found a rather
simple way to reproduce the problem:
dd if=/dev/zero of=test.img bs=8192 count=81920
81920+0 records in
81920+0 records out
671088640 bytes (671 MB) copied, 1.52943 s, 439 MB/s
losetup /dev/loop0 test.img
mkfs.btrfs /dev/loop0
WARNING! - Btrfs v0.20-rc1-37-g91d9eec IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using
SMALL VOLUME: forcing mixed metadata/data groups
Created a data/metadata chunk of size 8388608
fs created label (null) on /dev/loop0
nodesize 4096 leafsize 4096 sectorsize 4096 size 640.00MB
Btrfs v0.20-rc1-37-g91d9eec
mount /dev/loop0 /mnt
btrfs subvolume create /mnt/test
Create subvolume '/mnt/test'
mkdir /mnt/test/test1
/root/x/testxattr /mnt/test/test1
processing file /mnt/test/test1
cp -a /mnt/test/test1 /mnt/test/test2
/root/x/testxattr /mnt/test/test2
processing file /mnt/test/test2
processing attribute system.posix_acl_default
lgetxattr failed: No data available
Might it be a bug in coreutils ?
Thanks in advance,
David Arendt
On 11/27/12 08:46, Liu Bo wrote:
> Hi,
>
> (cc btrfs Mailing list to notify others.)
>
> Thanks for the helpful test.img.
>
> Well...after deeper debug, I'm sure that it's not a btrfs bug,
> at least not a btrfs acl/xattr bug.
>
> The debug tree shows
>
> item 10 key (257 INODE_ITEM 0) itemoff 3387 itemsize 160
> inode generation 6 transid 6 size 102 block group 0 mode 40755 links 1
> item 11 key (257 INODE_REF 256) itemoff 3372 itemsize 15
> inode ref index 2 namelen 5 name: test1
> item 12 key (257 XATTR_ITEM 367492571) itemoff 3318 itemsize 54
> location key (0 UNKNOWN.0 0) type 8
> namelen 24 datalen 0 name: system.posix_acl_default
> ^^^^^^^^^^^
> item 13 key (257 XATTR_ITEM 2038346239) itemoff 3237 itemsize 81
> location key (0 UNKNOWN.0 0) type 8
> namelen 23 datalen 28 name: system.posix_acl_access
> data ^B
>
> ==========
>
> so extended attribute "system.posix_acl_default" here has not data, which'll
> make filesystems(not just btrfs) return -ENODATA.
>
> I guess some userspace applications may make it like that.
>
> thanks,
> liubo
>
> On Mon, Nov 26, 2012 at 06:38:06AM +0100, David Arendt wrote:
>> Hi,
>>
>> I don't know if your xattr patch was meant to fix this issue, but I have
>> just tested kernel 3.7-rc7 with your patch applied on another directory
>> having the problem and I still have the weird behaviour.
>>
>> Thanks in advance,
>> David Arendt
next prev parent reply other threads:[~2012-11-27 19:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 17:45 extended attributes wiredness David Arendt
2012-11-23 20:43 ` Garry T. Williams
2012-11-23 21:09 ` David Arendt
2012-11-24 3:39 ` Liu Bo
2012-11-24 7:17 ` David Arendt
2012-11-25 20:15 ` David Arendt
2012-11-26 2:54 ` Liu Bo
2012-11-26 5:38 ` David Arendt
2012-11-27 7:46 ` Liu Bo
2012-11-27 16:53 ` David Arendt
2012-11-27 19:20 ` David Arendt [this message]
2012-11-28 10:54 ` Liu Bo
2012-11-28 11:12 ` Rock Lee
2012-11-28 17:11 ` David Arendt
2012-11-27 21:18 ` David Arendt
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=50B51296.3010103@prnet.org \
--to=admin@prnet.org \
--cc=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).