My Amanda level 1 back-ups are failing consistanly on one of my drives.
However there is small amounts of activity going on during the time
amanda dump. Sometimes I have mtrg running in the background
backing up files and folders - do you think that is the cause of these
errors here?
Or is there some other animal causig this evil?
?
FAILED AND STRANGE DUMP DETAILS:
/-- sda10 lev 1 FAILED [/sbin/dump returned 3]
sendbackup: start [:sda10 level 1]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/sbin/restore -f... -
sendbackup: info end
| DUMP: Date of this level 1 dump: Mon Jan 22 06:14:47 2001
| DUMP: Date of last level 0 dump: Sat Jan 20 07:32:06 2001
| DUMP: Dumping /dev/sda10 (/home) to standard output
| DUMP: Label: none
| DUMP: mapping (Pass I) [regular files]
| DUMP: mapping (Pass II) [directories]
| DUMP: estimated 586178 tape blocks.
| DUMP: Volume 1 started at: Mon Jan 22 06:16:33 2001
| DUMP: dumping (Pass III) [directories]
| DUMP: dumping (Pass IV) [regular files]
? DUMP: bread: lseek fails
? DUMP: short read error from /dev/sda10: [block
-2097472760]: count=4096, got=0
? DUMP: short read error from /dev/sda10: [sector
-2097472753]: count=512, got=0
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
To: Denise Ives <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: strange dump summary - can you explain this?
>? DUMP: bread: lseek fails
>? DUMP: short read error from /dev/sda10: [block
>-2122605784]: count=2048, got=0
This is typical of dumping an active file system. In particular, if the
dump program knows it needs to read an indirect block of disk addresses
and the file is removed/reallocated and that block reused for data,
all those pointers (disk block addresses) are garbage and dump gets
real unhappy.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
