On Jan 28, 2009, at 4:47 PM, Warren Block wrote:
There's also the issue of terminator power, which may have been
supplied by the old drive but not by the new one.
Yes, usually a jumper is available. Also used to be one-shot fuses
before the Raychem self-reseting PTC Polyswitch fuses.
--
On Wed, 28 Jan 2009, Jaime wrote:
On Wed, Jan 28, 2009 at 4:51 PM, Wojciech Puchar
wrote:
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
On Wed, Jan 28, 2009 at 05:06:55PM -0500, Jaime wrote:
> On Wed, Jan 28, 2009 at 4:51 PM, Wojciech Puchar
> >
> > TERMINATION PROBLEM
>
> I was thinking of that... I shut down the server and checked the
> usual suspects (terminator on the cable, SCSI IDs, etc.) but didn't
> find anything out of p
On Wed, Jan 28, 2009 at 4:51 PM, Wojciech Puchar
wrote:
>> 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.
>
>
On Wed, Jan 28, 2009 at 03:49:39PM -0600, Dan Nelson wrote:
> In the last episode (Jan 28), Jaime said:
> >
> > 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?
>
> It shouldn't. At w
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?
no just use -b in other unices too :)
When reading from the tape using tar (bsdt
I am trying to replace an older DLT tape drive (which doesn't like to
eject tapes any more) with a new Quantum DLT-4 drive. Its connected
by internal SCSI and seems to be set up right. But after DAYS of
running a tar command, its still not done backing up 60GB. The old
drive could backup 70-8
On Wed, Jan 28, 2009 at 4:27 PM, David Kelly 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/s
In the last episode (Jan 28), Jaime said:
> On Wed, Jan 28, 2009 at 3:23 PM, Dan Nelson 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 blocksiz
On Wed, Jan 28, 2009 at 03:38:43PM -0500, Jaime wrote:
> >
> > In the last episode (Jan 28), Jaime said:
> >> /usr/bin/tar -cvpX /usr/local/etc/backups/skiplist-relative.txt -f
> >> /dev/sa0 -C / .
[...]
> Any other thoughts before I try to OS update and the larger block size?
You list -v
On Wed, Jan 28, 2009 at 3:23 PM, Dan Nelson 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 fo
In the last episode (Jan 28), Jaime said:
> I am trying to replace an older DLT tape drive (which doesn't like to
> eject tapes any more) with a new Quantum DLT-4 drive. Its connected
> by internal SCSI and seems to be set up right. But after DAYS of
> running a tar command, its still not done b
12 matches
Mail list logo
