The following reply was made to PR bin/153142; it has been noted by GNATS. From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= <tr...@freebsd.org> To: Jaakko Heinonen <j...@freebsd.org> Cc: Hiroshi Fujishima <hir...@tonteki.org>, Bruce Cran <br...@cran.org.uk>, bug-follo...@freebsd.org Subject: Re: bin/153142: [zfs] ls -l outputs `ls: ./.zfs: Operation not supported' Date: Fri, 14 Jan 2011 10:07:02 +0100
Wiadomo=B6=E6 napisana przez Jaakko Heinonen w dniu 2011-01-14, o godz. = 10:00: > On 2010-12-14, Hiroshi Fujishima wrote: >>> Description: >> 1. filesystem is zfs >> 2. snapdir property is visible >> 3. top directory of file system has .a file. >>=20 >> with above condition, ls -l outputs `ls: ./.zfs: Operation not = supported' >>=20 >>> How-To-Repeat: >> backup8y# zfs create -o mountpoint=3D/test -o snapdir=3Dvisible = tank/test >> backup8y# ls -l /test >> total 0 >> dr-xr-xr-x 3 root wheel 3 Dec 14 15:46 .zfs >> backup8y# touch /test/.a >> backup8y# ls -l /test >> total 1 >> -rw-r--r-- 1 root wheel 0 Dec 14 15:46 .a >> ls: /test/.zfs: Operation not supported >> dr-xr-xr-x 3 root wheel 3 Dec 14 15:46 .zfs >=20 > ls(1) detects from the first file in the listing if the file system > supports ACLs and assumes that all files on the same file system = support > ACLs. The ".zfs" directory is special and doesn't support ACLs. Thus > ls(1) prints an error message for acl_get_link_np(3) failure. >=20 > Also, if the ".zfs" directory is the first entry of a listing, ls(1) > assumes that files on the same file system don't have ACLs and doesn't > print '+' after mode. I guess the easiest way to fix this would be to add "dummy" ACL support for ".zfs" directory - that is, to zfsctl_ops_root[], if I'm reading = this correctly. -- If you cut off my head, what would I say? Me and my head, or me and my = body? _______________________________________________ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
