eps@toaster.SFSU.EDU (Eric P. Scott) (03/11/90)
tar works fine with a locally-attached Exabyte, but I'm not having much luck across a communications channel. For example, why would tar cbf 20 /dev/nrxt0 ... work, yet tar cbf 20 - ... | dd of=/dev/nrxt0 bs=20b not? Everything seems ok, but when I read it back I get directory checksum errors. (I've tried tar with and without B, and block sizes of 8 and 20; no combination works) For that matter, dd on the input side doesn't do too well either. I can NFS-mount most of the remote filesystems I want to back up (avoiding the problem), but there are some cases where that isn't an option, and I don't want to haul the drive around. [I know about rdump, I don't want to use it.] -=EPS=-
jdi@sparky.Franz.COM (John Irwin) (03/16/90)
In article <351@toaster.SFSU.EDU> eps@cs.SFSU.EDU (Eric P. Scott) writes: >tar works fine with a locally-attached Exabyte, but I'm not having >much luck across a communications channel. > >For example, why would > tar cbf 20 /dev/nrxt0 ... >work, yet > tar cbf 20 - ... | dd of=/dev/nrxt0 bs=20b > >not? >... You need to use: tar cbf 20 - ... | dd of=/dev/nrxt0 obs=20b IE: you only want to specify the output block size, not the input and output block size. This is because of how Unix buffers pipes. -- John Irwin Franz Inc.