Thanks to the following people for responding to my question
about the "dump: bread: lseek fails" problem:
Todd, Derek, Sean, Steve, Earl, Agnes, Ronald, Jeff, Anthony, Dave,
Vladimir, Olivier, Jonathan
The response was almost unanimous. I have a bad disk.
Martin Meadows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
get your data off that disk *now* if you can!!! This is a sign of emminent
disk failure.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I've run into that trouble before -- the problem was with the corrupted
filesystem. Try bringing the machine to singleuser and run fsck
on the unmounted filesystem.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The filesystem structure has probably got corrupted. I'd unmount it
and run fsck on it (a *forced* fsck that ignores the 'clean' flag - cant
remember what the 4.x option is).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You might try running fsck on the disk. This can sometimes remove
this problem.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You might want to unmount the file system and run fsck on it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I'd say you have a disk failure in progress.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You have a failing or corrupt disk
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I thing it's a "block read" error on the disk. Maybe you should use format
to analyze the disk.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I'd suggest running fsck
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Check your console for messages, you are getting disk errors on the partition
you are trying to dump.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hi Martin. When I've seen this in the past, either there's a problem with the
filesystem, which a newfs can fix, or the disk is going bad. Either way, get a
good backup PDQ. At this stage, tar should still work.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I believe that this means that your /home2 fs is corrupted and you should fsck
it. It may be because there are some bad spots on your disk in the /home2 area.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In my experience, this has indicated an imminent hard disk failure for
the partition in question. The 'bread' is a block read.
If you have Sun support, gather all necessary backup tapes, call Sun
for a replacement hard drive, order a pizza, and hunker down for a
few hours of system restoration.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:51 CDT