On Thu, Mar 15, 2001 at 05:57:09PM +0000, Raymond Bramwell wrote:
It is possible you're trying to dump a corrupted filesystem.
If the filesystem checks out OK, could it be you're trying to
dump an active filesystem? Dump gets down and dirty with the
details of the filesystem, and if the filesystem has changed
between the time dump reads a reference and the time it
picks up the referenced data, it may wind up interpreting
what's now, for example, just plain data, as further filesystem
references (block numbers, offsets, and so on).
If that only happens once in a while, perhaps it is tolerable.
Alternately, you might consider trying GNU tar. This is
a FAQ on this list.
The "timed out" is disquieting. I've seen such errors mostly
when there is failing hardware. Failing hardware, of course,
is a quick recipe for filesystem corruption. You might want
to take a look at your logs, and see if you're encountering
"timed out" at other times.
I use a scanner that looks for this message on all machines
several times a day, and emails me the result, if it finds
any new ones. Most cost-effective way I've found yet to catch
failing hard drives before they do much damage.
If this was one of my machines I'd try to find a time I could
bring it down very soon, check the filesystems, and do a complete
read-only test of the disk surface.
> Hi there, I'm getting some strange reports in my dump summary:
>
> pluto /dev/ida/c0d0p8 lev 0 FAILED [/sbin/dump returned 3]
> pluto /dev/ida/c0d0p8 lev 0 FAILED [dump to tape failed]
>
> And here is a snippet of dump's output for this device...
>
> | DUMP: 71.14% done, finished in 2:50
> | DUMP: 72.60% done, finished in 2:40
> | DUMP: 72.94% done, finished in 2:39
> ? DUMP: bread: lseek fails
> ? DUMP: bread: lseek fails
> ? DUMP: bread: lseek fails
> ? DUMP: bread: lseek fails
> ? DUMP: bread: lseek fails
> ? DUMP: bread: lseek fails
> ? DUMP: bread: lseek fails
> ? DUMP: bread: lseek fails
> ? DUMP: bread: lseek fails
> ? DUMP: short read error from /dev/ida/c0d0p8: [block -2007777696]:
> count=4096, got=0
> ? DUMP: DUMP: bread: lseek fails
> ? DUMP: short read error from /dev/ida/c0d0p8: [block -1451271504]:
> count=4096, got=0
> ? DUMP: DUMP: bread: lseek fails
> ? bread: lseek2 fails!
> ? DUMP: short read error from /dev/ida/c0d0p8: [sector -2007777696]:
> count=512, got=0
>
> Does anyone know what the dump returned 3 error means and what can
> be done about it?
>
> Finally I'm getting the error
>
> theakston2 /dev/rd/c0d1p1 lev 0 FAILED [Request to theakston2 timed
> out.]
>
> Which seems pretty strange seeing as though amcheck was fine about it!
> Any ideas?
>
> --
> Moneyextra Limited is an independent intermediary regulated by the
> Personal
> Investment Authority. The PIA does not regulate mortgages, current or
> deposit accounts, credit cards, loans or general and medical insurance.
> Moneyextra Limited, One Temple Back East, Temple Quay, Bristol BS1 6DX
>
--
-----------------------------------------------------------------
Dan Wilder <[EMAIL PROTECTED]> Technical Manager & Correspondent
SSC, Inc. P.O. Box 55549 Phone: 206-782-7733 x123
Seattle, WA 98155-0549 URL http://www.linuxjournal.com/
-----------------------------------------------------------------
