Okay here's another confusion: Why do the block-limits change each time 
kernel module st gets loaded:

Sep  7 10:02:53 valhalla kernel: st0: Block limits 4931 - 13329843 bytes.
Sep  7 10:28:34 valhalla kernel: st0: Block limits 17664 - 11931656 bytes.
Sep  7 12:10:27 valhalla kernel: st0: Block limits 512 - 43129 bytes.

What do those numbers mean??

Regards,

Brian

On Fri 06 Sep 02 16:59, Jon LaBadie wrote:
> On Fri, Sep 06, 2002 at 11:01:45AM +0200, Brian Jonnes wrote:
> > Hi all,
> >
> > I'm getting this in my kern.log's:
> >
> > ---
> > Sep  6 00:45:01 valhalla kernel: st: Version 20020205, bufsize 32768, wrt
> > 30720, max init. bufs 4, s/g segs 16 Sep  6 00:45:01 valhalla kernel:
> > Attached scsi tape st0 at scsi0, channel 0, id 0, lun 0 Sep  6 00:45:01
> > valhalla kernel: st0: Block limits 25976 - 6841632 bytes. Sep  6 01:18:39
> > valhalla kernel: st0: Error with sense data: Info fld=0x10200, Deferred
> > st09:00: sense key Medium Error Sep  6 01:18:39 valhalla kernel:
> > Additional sense indicates Sequential positioning error Sep  6 01:30:01
> > valhalla kernel: st: Unloaded.
> > ---
> >
> > This was from an amdump, which failed after 64kb written.
> >
> > A little bit later, running an amcheck:
> > ---
> > Sep  6 09:54:45 valhalla kernel: st: Version 20020205, bufsize 32768, wrt
> > 30720, max init. bufs 4, s/g segs 16 Sep  6 09:54:45 valhalla kernel:
> > Attached scsi tape st0 at scsi0, channel 0, id 0, lun 0 Sep  6 09:54:45
> > valhalla kernel: st0: Block limits 11268 - 112641 bytes. Sep  6 10:09:45
> > valhalla kernel: scsi : aborting command due to timeout : pid 72600,
> > scsi0, channel 0, id 0, lun 0 Read (6) 01 00 00 40 00 Sep  6 10:09:45
> > valhalla kernel: hdd: irq timeout: status=0xc0 { Busy } Sep  6 10:09:45
> > valhalla kernel: hdd: ATAPI reset complete
> > Sep  6 10:09:45 valhalla kernel: hdd: irq timeout: status=0x80 { Busy }
> > Sep  6 10:09:46 valhalla kernel: hdd: ATAPI reset complete
> > Sep  6 10:09:46 valhalla kernel: hdd: irq timeout: status=0x80 { Busy }
> > Sep  6 10:09:46 valhalla kernel: st0: Error 27070000 (sugg. bt 0x20,
> > driver bt 0x7, host bt 0x7). Sep  6 10:20:01 valhalla kernel: st:
> > Unloaded.
> > ---
> >
> > Pulled the tape out, plugged it back in, and now its dumping fine. Can
> > anyone make sense of this?
>
> I don't use your systems but ISTR people mentioning using mt to set the
> block size to 32K.
>
> > BTW is there a way of getting amanda to put level 0's in "degraded mode"?
> > I'd still like full dumps when I have to manually run amdump.
>
> level 0 and degraded mode?  Aren't these non-sequitors?  I thought degraded
> mode meant falling back to incrementals because there was no place to put
> the level 0's.  I.e. the tape was not working and the holding disk did not
> have enough unreserved space to hold the level 0's.  So where would you
> like amanda to put your huge level 0's if it can't put it to tape or to
> disk?
>
> What's your holding disk space and reserve % situation?

-- 
Init Systems  -  Linux consulting
031 767-0139    082 769-2320    brian AT init.co DOT za