Bug 55219

Summary:	when trying to backup fsf-call failed
Product:	[Unmaintained] kdat	Reporter:	O J Schumann <o.j.schumann>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	finex, grundleborg
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description O J Schumann 2003-02-26 16:49:26 UTC

Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          g++ (GCC) 3.2.2 20030109 (Debian prerelease) 
OS:          Linux

When I click the OK-Button in the Backup-Option, KDat checks the files andthen should begin to backup. But it gives an error box with: "Cannot get zo end of tape \n Backup aborted"
On STDERR I get TapeDrive::nextFile() -- ioctl( MTFSF ) failed!
and my st driver with Debug-Statments gives

st0: Spacing tape forward over 1 filemarks.
st0: Error: 28000002, cmd: 11 1 0 0 1 0 Len: 0
Info fld=0x1, Current st09:00: sense key Blank Check
Additional sense indicates End-of-data detected

mfg.
  Olaf J. Schumann

Comment 1 Lawrence E. Widman 2003-02-27 02:31:39 UTC

Subject: Re:  New: when trying to backup fsf-call failed

Olaf,

> When I click the OK-Button in the Backup-Option, KDat checks the files andthen should begin to backup. But it gives an error box with: "Cannot get zo end of tape \n Backup aborted"
> On STDERR I get TapeDrive::nextFile() -- ioctl( MTFSF ) failed!
> and my st driver with Debug-Statments gives
> 
> st0: Spacing tape forward over 1 filemarks.
> st0: Error: 28000002, cmd: 11 1 0 0 1 0 Len: 0
> Info fld=0x1, Current st09:00: sense key Blank Check
> Additional sense indicates End-of-data detected

Hmm, beats me.  I'll think about it when the kids give me some peace.

Is it possible that that particular tape is bad, that the drive heads need
cleaning, or that the tape cartridge ran out of tape?  I'm just thinking of
things that have happened to me.

What drive are you using? 

Cheers - Larry Widman

Comment 2 George Goldberg 2008-02-15 04:45:43 UTC

Does this bug still exist in a recent version of KDE, such as 4.0.1?

Comment 3 FiNeX 2009-08-26 15:32:57 UTC

Kdat is not developed and mantained anymore. All Kdat bugs are closed with the status "unmantained".