>can anyone give me a short explanation of the bread, short read and lseek
>error messages here?
>
> DUMP: bread: lseek fails
>? DUMP: bread: lseek fails
>? DUMP: short read error from /dev/sda10: [block
>-1572797648]: count=4096, got=0
Dump works with what are called inodes and raw disk addresses (block
numbers). There is an inode for every file system object (e.g. file,
directory, symlink). In there is the list of disk blocks describing
where the data is stored.
Dump uses a routine called bread ("block read" in its own code) that
takes a disk block number from the inode, calls lseek on the disk to
position it and then does a read to get the data.
This error says that the disk block number dump got from via the inode
and tried to use was bogus (-1572797648) and so when bread tried to
lseek to that spot, that failed, and so did the read, which requested
4096 bytes but got back zero.
As I said before, this situation can happen on a live file system where
the OS has changed the disk block allocation information while dump is
trying to use it.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
