Hey Brian,

just now (on 01/07/2005 at 19:20) you wrote:

>> Humm, are you saying that amlabel works and can read the label 
>> written, but that dd doesn't/cannot?  Back to 'man dd' as it exists
>> on that Irix system would be my next suggestion.

BC> Remembering that I'd set the blocksize on the device and relabeled
BC> yesterday I tried this.

BC> samar 160# mt -f /dev/sdlt2 rewind
BC> samar 161# dd of=/dev/sdlt2 bs=32k if=./scratch
BC> 1+0 records in
BC> 1+0 records out

BC> Which worked fine.

Good to hear. What size did scratch have?
Much nicer device-name now, BTW, maybe this was the problem ... Do you
use this one (the corresponding non-rewinding device) in amanda.conf
as well ?? 

BC> I then tried to re-write the label with dd

BC> samar 170# dd of=/dev/sdlt2 obs=32k if=./scratch 
BC> 64+0 records in
BC> 1+0 records out

Ok, I see, you had a bs=512 (0.5k) when you read and wrote the same
file with bs=32k (64 times bigger now).

BC> Actually the xfsrestore file is a link to the executable in the /usr/sbin
BC> directory. It does make sense, after a fashion (why not a link for the
BC> xfsdump executable as well).

>> >samar 126# which xfsrestore
>> >/sbin/xfsrestore
>> >samar 127# which xfsdump
>> >/usr/sbin/xfsdump

As long as AMANDA actually USES it this is OK, yes.

BC> I'm now going to attempt to run amdump with a much shorter disklist
BC> and see if I can't get a rational result on this tape.

I am looking forward to the results ...

Stefan