Date: Tue, 10 Mar 2009 07:46:43 +0300 From: Anonymous <swell.k@gmail.com> To: Pegasus Mc Cleaft <ken@mthelicon.com> Cc: current@freebsd.org Subject: Re: bsdtar lockup on Current-03/10/2009 Message-ID: <86mybuasss.fsf@gmail.com> References: <200903100104.53847.ken__6247.10998167775$1236647281$gmane$org@mthelicon.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Pegasus Mc Cleaft <ken@mthelicon.com> writes: > Hi Current & Hackers, > > I was wondering if anyone else is seeing this problem: Any use of bsdtar to > create a new archive causes the process to be unresponsive to all signals and > consumes 100% cpu time. The machine I am testing on is a Core 2 quad running > in AMD64 (8 gigs ram, zfs boot, root, et al.) > > I have tried disabling the zil and prefetch as a precaution but can still > cause the failure by doing the command below(trying to eliminate zfs writes as > being the problem): > #tar -cvf /dev/null * > > Unarchiving from tar seems to work OK. The bug may have been introduced a few > days ago. I just noticed my machine doing this tonight when I tried to do a > portupgrade and the creation of the backups locked up. > > Thanks, > Peg This was already reported in bin/132452. Can you go to src/usr.bin/tar and update it up before r189514 such as r189513? BTW, do you have same problem with `rsync -X' on ZFS partition?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86mybuasss.fsf>