Amanda-Users

lseek kernel bug

2009-05-08 11:58:07
Subject: lseek kernel bug
From: "Stefan G. Weichinger" <sgw AT amanda DOT org>
To: "Amanda user's group" <amanda-users AT amanda DOT org>
Date: Fri, 08 May 2009 17:45:36 +0200
I have an emergency call from a german customer, the goal is to restore
files from an Ultrium drive.

Suse 10.2, amanda 2.5.2p1, tar (GNU tar) 1.15.1 ...

I get no results with amrestore, no scsi-errors ...

positioning via "mt fsf" fails

$ mt -f /dev/nst0 fsf
mt: /dev/nst0: Input/output error

and reading files with dd as well, I am only able to read the first
archive, the second fails:

$ dd if=/dev/nst0 of=file.2 bs=32k skip=1
dd: warning: working around lseek kernel bug for file (/dev/nst0)
  of mt_type=0x72 -- see <sys/mtio.h> for the list of types
dd: reading `/dev/nst0': Input/output error
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.00931095 s, 0.0 kB/s


The first file only contains binary data, I am unable to read it with
any tools (dump/zip/restore/tar/ ... the DLE should have been dumped
without sw-compression, the drive does hw-compression.

Does anyone know about that lseek bug?

Any help welcome, thanks, Stefan

<Prev in Thread] Current Thread [Next in Thread>