On Wed, Jun 07, 2000 at 01:33:57AM +0100, Niall O Broin mentioned:
> The error mentioned doesn't sound like that, but more like a partition
> thing. I would definitely concur with dismounting the partition and fsck'ing
> it.
I have to agree. I've seen it a few times when I messed up with fdisk,
and the disk tried to seek a part of the disk that didn't exist. Could
also be filesystem corruption, but that's more likely a symptom of a dodgy
disk/partition table.
> However, because of the way dump works it is a seriously bad idea to use
> dump to backup a non-quiescent filesystem. The backup may appear to work
> but you may have restore problems. I think in the worst case you may restore
> something other than what you dump - this might be regarded as bad :-)
Very much so. What dump does is a two-pass thing. The first pass, it logs
all the inodes in use by the filesystem, and where they are on disk. It
then writes that to the tape. The second pass rips the inode contents from
the disk, and spools it to tape. If you have deleted a file, between the
time it was scanned, and the time it was spooled, it'll still write it to
tape.
Stranger things happen when you truncate or add to files. Really strange.
Kate
--
"The fool must be beaten with a stick, for an intelligent person
the merest hint is sufficient" -- Zen Master Greg
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
