Hi,
Standard for linux is to use BSD semantics.
It is a compile-time-option for scsi-devices located in
scsi/st_options.h called ST_SYSV, change it to 1 and you get SYSV
semantics.
But this should not be aproblem, since i run 5 linux-amanda-servers
with the default-setting, without problems for 3 years or more now.
Christoph
"John R. Jackson" schrieb:
>
> >Can the error appear through a bad termination of the scsi bus???
>
> Bad termination can cause just about anything, so yes.
>
> >> $ mt -f /dev/nst0 rewind
> >> $ mt -f /dev/nst0 fsf 1
> >> $ dd if=3D/dev/nst0 bs=3D32k count=3D1 > /tmp/block.0
> >> $ ls -l /tmp/block.0
> >> $ head -4 < /tmp/block.0
> >
> >The result of this command is: AMANDA: TAPEEND DATE X it is a 32k file
>
> That's very odd. It implies the tape is "empty", i.e. has no Amanda
> data on it at all. Yet amrestore saw at least some stuff, just not what
> it expected.
>
> Are you sure Amanda wrote anything to this tape?
>
> >The problem happens on all tapes i use.
>
> Then I'd start testing that drive and all the associated hardware.
>
> The only other thing I can think of is that you have your software
> (driver) configured to use BSD tape semantics instead of SYSV. That could
> cause some odd behavior. I don't know enough about Linux to tell you
> what to look for, though.
>
> >roshan=
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
