ACL issue (Was Re: HEADS UP: ZFSv28 is in!)
Steve Wills
swills at FreeBSD.org
Sun Mar 6 16:43:13 UTC 2011
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/06/11 11:30, Jeremy Chadwick wrote:
> On Sun, Mar 06, 2011 at 08:23:42AM -0800, Jeremy Chadwick wrote:
>> On Sun, Mar 06, 2011 at 11:06:09AM -0500, Steve Wills wrote:
>>
>> Sorry, I should have been more clear -- my investigation wasn't to
>> determine if the issue you're reporting was a bug or not, but more along
>> the lines of "hmm, where is userland getting EOPNOTSUPP from in the
>> kernel in this situation?" It could be that some piece hasn't been
>> implemented somewhere yet (more an "incomplete" than a bug :-) ).
>>
>> I tend to trace source the way I did above in hopes that someone (kernel
>> dev, etc.) will chime in and go "Oh, yes, THAT... let me tell you about
>> that!" It's also for educational purposes; I figure sharing the innards
>> along with some simple descriptions might help people feel more
>> comfortable (vs. thinking everything is a black box; don't let the magic
>> smoke out!). Sometimes digging through the code helps.
Definitely. I had started looking at cp(1) source, but got a bit lost.
>>>> This leaves me with some ideas; just tossing them out here...
>>>>
>>>> 1. Maybe/somehow this is caused by swap being used as the backing
>>>> type/store for md(4)? Try using "mdconfig -t malloc -o reserve"
>>>> instead, temporarily anyway.
>>>
>>> Seems to be the same.
>>
>> I'm not too surprised, but at least that rules out swap vs.
>> non-block-device stuff being somehow responsible.
>>
>> I'm not a user of ACLs myself, but Robert Watson might know what's up
>> with this, or where to go looking. I've CC'd him here.
>>
>>>> 2. Are you absolutely 100% sure the kernel you're using was built
>>>> with "options UFS_ACL" defined in it? Doing a "strings -a
>>>> /boot/kernel/kernel | grep UFS_ACL" should suffice.
>>>>
>>>
>>> Yep, it does:
>>>
>>> % strings -a /boot/kernel/kernel | grep UFS_ACL
>>> options UFS_ACL
>>>
>>> (My kernel config is just "include GENERIC" then a bunch of "nooptions"
>>> for KDB, DDB, GDB, INVARIANTS, WITNESS, etc.)
>>
>> Cool, good to rule out the obvious. Thanks.
>>
>> The only other thing I can think of off the top of my head would be to
>> "ktrace -t+ -i" the cp -p, then provide output of kdump -s -t+ after.
>> I wouldn't say go about this quite yet (it may not even help determine
>> what's going on); maybe wait for Robert to take a look first.
>
> It would help if I actually added Robert to the CC list, wouldn't it?
> :-)
>
That's OK, kib@ enlightened me (via IRC) that the issue is that I failed
to enable NFSv4 ACLs on the FS. I had tried this, but somehow got an
error, and then when I tried again I had the wrong ACL type (POSIX.1e).
Steve
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)
iQEcBAEBAgAGBQJNc7mdAAoJEPXPYrMgexuhhZUIAId0nmh4YTJbjzv3NDmxXVt3
16ZIx+wOQON9Sln0vrpKIDJGk95KzvuLnbVBPg7Oxhaa11llkEeYFFqMEVWn6Esa
hqwDe5yYJYWWyF7ulCmHDbAE2gEF5q2rVy0KrV+aI9x5DLeB607dpmZqVV6TeQky
mQb1zOcw165galYhI3S4juPK6z5nq5pnTc+l05590CcAkWtxOFwQjlDZiQtrxdg2
YhFhtrMeGubRdKtJyG0r17kJzlGCBwIYBg7SgnmORVB64W0N0zkVcC+ZrIhioR6Z
FoucxqelZ4VDt6IlmxZ3DzTNUGKWulCeCrus8+lDBPL1M92AfFgMF89i5n0Ot8Y=
=302p
-----END PGP SIGNATURE-----
More information about the freebsd-fs
mailing list