Hi,
Amanda started returning these results a couple of days ago...
FAILED AND STRANGE DUMP DETAILS:
/-- gemini sda5 lev 0 FAILED [/sbin/dump returned 3]
sendbackup: start [gemini:sda5 level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/sbin/restore -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
| DUMP: Date of this level 0 dump: Thu May 17 03:01:30 2001
| DUMP: Date of last level 0 dump: the epoch
| DUMP: Dumping /dev/sda5 (/home) to standard output
| DUMP: Label: none
| DUMP: mapping (Pass I) [regular files]
| DUMP: mapping (Pass II) [directories]
| DUMP: estimated 3210845 tape blocks.
| DUMP: Volume 1 started at: Thu May 17 03:01:45 2001
| DUMP: dumping (Pass III) [directories]
| DUMP: dumping (Pass IV) [regular files]
| DUMP: 4.66% done, finished in 1:42
| DUMP: 12.08% done, finished in 1:12
| DUMP: 20.04% done, finished in 0:59
? DUMP: bread: lseek fails
...
So I took the server down to runlevel 1, e2fsck'd the drive checking for
physical bad blocks as well as damaged inodes etc. It said that it found a
problem with 1 file, which it repaired. Brought it back up, and the next
night had the same problem. Thought it might have been related to 1 very
large, recently saved file (1.3G), but made it much smaller (400M) and it's
still happening.
Anything I can check for? Is there anyway I can identify where on the disk
it's failing, and try removing that file?
Thanks,
Chris Herrmann
Far Edge Technology
p. 02 99553640
f. 02 99547994
m. 0403 393309
http://www.faredge.com.au
