Date: Tue, 10 Mar 2009 21:14:11 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Anonymous <swell.k@gmail.com> Cc: freebsd-current@freebsd.org Subject: ZFS/amd64/extattr lockup (was Re: bsdtar lockup on Current-03/10/2009) Message-ID: <49B73A93.8030007@freebsd.org> In-Reply-To: <86fxhkdd42.fsf@gmail.com> References: <200903100104.53847.ken__6247.10998167775$1236647281$gmane$org@mthelicon.com> <86mybuasss.fsf@gmail.com> <200903101238.20974.paul@fletchermoorland.co.uk> <86sklldth2.fsf@gmail.com> <49B7157F.7010101@freebsd.org> <86fxhkdd42.fsf@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Anonymous wrote: > Tim Kientzle <kientzle@freebsd.org> writes: >>Anonymous wrote: >>>Paul Wootton <paul@fletchermoorland.co.uk> writes: >>> >>>>Im also using ZFS and have the same problems as Peg when trying to create a >>>>tar file. >>>>This is using Current as of last yesterday (09-mar-09). >>> >>>I'm not sure but in my case ktrace shows extattr_list_link() before the lockup. >>>So, for a workaround I disabled extattr support in libarchive. Can you verify that >>>this helps you, too? >> >>Please try this, which will poke that same system >>call in a different way: >> >> rm -f foo foolink >> touch foo >> ln -s foo foolink >> lsextattr -h user foolink > > Right here. So lsextattr -h hangs for you on AMD64 using ZFS with a file that has no extended attributes. I've not been able to reproduce it on i386 with UFS (though I'm about a week out-of-date; I'm updating now). Please try this on a UFS volume so we can figure out whether this is an AMD64 problem or a ZFS problem. (format a floppy or a USB key or a swap-backed ramdisk, maybe?) Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49B73A93.8030007>