Date: Wed, 28 Jan 2009 15:38:43 -0500 From: Jaime <jaime@snowmoon.com> To: Dan Nelson <dnelson@allantgroup.com> Cc: freebsd-questions@freebsd.org Subject: Re: Quantum tape drive Message-ID: <ae4324ed0901281238u4f1a1ddo400407115e6491f2@mail.gmail.com> In-Reply-To: <20090128202349.GD63837@dan.emsphone.com> References: <ae4324ed0901281136v80fd634t1cbed1f73170c2ef@mail.gmail.com> <20090128202349.GD63837@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 28, 2009 at 3:23 PM, Dan Nelson <dnelson@allantgroup.com> wrote: > > In the last episode (Jan 28), Jaime said: >> /usr/bin/tar -cvpX /usr/local/etc/backups/skiplist-relative.txt -f /dev/sa0 -C / . > > If nothing else, I suggest bumping up your blocksize. The default for tar > (10k) is pretty small for modern tape drives. Try -b 128 (for a 64k block > size). Another optimization would be to put a buffering program in between > tar and your tape drive to decouple disk reads from tape writes. misc/team, > misc/buffer, and misc/cstream in ports are good for this. Thanks. Would this decrease the ability of other Unixes being able to read the tape? For example, using pax (which can read tar archives) or GNU's tar? Sadly, I forgot to mention something in my last message. Sorry. When reading from the tape using tar (bsdtar from FreeBSD 6.2 -- and, yes, I'm preparing a cvsup as I write this :) ) the tape drive's Alarm and Fault LEDs are lit up and then camcontrol devlist no longer shows the tape drive. After I wrote to the tape via a quick boot into Knoppix, I found that FreeBSD's tar command could list the files on the tape. So maybe that is in the past now. Maybe not. I should have mentioned it earlier. Sorry. Any other thoughts before I try to OS update and the larger block size? Jaime
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ae4324ed0901281238u4f1a1ddo400407115e6491f2>