On Wed, May 10, 2006 at 03:40:12PM +0200, Andreas_Hallmann wrote:
> On Wed, May 10, 2006 at 08:58:12AM -0400, Jon LaBadie wrote:
> 
> > > The SCSI Specs speficy that "ASC/ASCQ: Write append position error" is a
> > > more precise version of the message "media error".
> > > 
> 
> > Only from googling:
> > 
> >     E6076 - Write append error
> > 
> >     Problem
> >     If a WRITE or WRITE FILEMARKS command fails because the append
> >     point was unreadable, this error occurs.
> > 
> 
> Found that too, for an IBM tape drive IIRC.
> 
> This is my best candidate. My drive does read after write checks.
> 
> I would love to have a pointer to some scsi-generic explanation of thoose
> ASC/ASCQ error codes. I only found code tables so far.
> 

Yeah, I only found tables of numeric codes and messages, no explanations.
Maybe "scsi.org"  :)


> > And one said some "platforms" gave this error when a write was attempted
> > in the middle of an existing tape file rather than at its end.
> 
> The term "platforms" must be kidding. These are SCSI error codes which are by 
> definition
> platform independent. Moreover reusing a tape we always do exactly that.
> Or should it mean, we tried to write a tape file while another wasn't 
> finished?
> I don't believe amanda behaves that way.

I took it to mean if a write starts in the middle of a tapefile.
For example, write a file, backup 2 records (tape blks),
start writing again.  Amanda doesn't do that, it writes to
an end of file, then starts a new file after an EOF.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)