Date: Wed, 28 Jan 2009 16:49:58 -0500 From: Jaime <jaime@snowmoon.com> To: FreeBSD-Questions@freebsd.org Cc: Dan Nelson <dnelson@allantgroup.com> Subject: Re: Quantum tape drive Message-ID: <ae4324ed0901281349j2755e251hc924559cb511687d@mail.gmail.com> In-Reply-To: <20090128212739.GB74728@Grumpy.DynDNS.org> References: <ae4324ed0901281136v80fd634t1cbed1f73170c2ef@mail.gmail.com> <20090128202349.GD63837@dan.emsphone.com> <ae4324ed0901281238u4f1a1ddo400407115e6491f2@mail.gmail.com> <20090128212739.GB74728@Grumpy.DynDNS.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 28, 2009 at 4:27 PM, David Kelly <dkelly@hiwaay.net> wrote: > You list -v as a tar option. Is tar sticking on a file? I just added that to my script in order to see what was going on. I didn't use it a week ago. I'm dumping straight to the tar drive. Look at the tar command again and you'll see /dev/sa0 in there. :) > Another question is whether or not tar could be getting caught in a hard > link or symbolic link infinite loop? Look for duplicates in the output. > uniq(1) should be of assistance. Perhaps uniq needs a sort(1) to > preprocess, I forget? Not a bad thought. However, I'm certain that there is no recursion going on. The delays are happening too early on for that. Also, this script works well if I target an external HD but never finishes on the tape. Thanks for the idea. I hadn't considered it before. Jaime
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ae4324ed0901281349j2755e251hc924559cb511687d>