Date: Wed, 29 Dec 1999 05:23:17 -0800 From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca> To: Stan Brown <stanb@netcom.com> Cc: freebsd-stable@FreeBSD.ORG (FreeBSD Stable List) Subject: Re: Dump problem (soft updates?) Message-ID: <199912291323.FAA06712@cwsys.cwsent.com> In-Reply-To: Your message of "Wed, 29 Dec 1999 07:22:42 EST." <199912291222.EAA22783@netcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199912291222.EAA22783@netcom.com>, Stan Brown writes:
> I have a machine with 3.4 STABLE (cvsuped this weekend). I have enable
> softupdates. Last night my amanda dump failed with the following:
>
>
> /-- koala wd0s1f lev 2 FAILED [/sbin/dump returned 3]
> sendbackup: start [koala:wd0s1f level 2]
> sendbackup: info BACKUP=/sbin/dump
> sendbackup: info RECOVER_CMD=/sbin/restore -f... -
> sendbackup: info end
> | DUMP: Date of this level 2 dump: Wed Dec 29 05:22:53 1999
> | DUMP: Date of last level 1 dump: Mon Dec 27 01:17:25 1999
> | DUMP: Dumping /dev/rwd0s1f (/usr) to standard output
> | DUMP: mapping (Pass I) [regular files]
> | DUMP: mapping (Pass II) [directories]
> | DUMP: estimated 1481869 tape blocks.
> | DUMP: dumping (Pass III) [directories]
> | DUMP: dumping (Pass IV) [regular files]
> | DUMP: 2.51% done, finished in 3:14
> | DUMP: 5.66% done, finished in 2:46
> | DUMP: 8.84% done, finished in 2:34
> | DUMP: 12.01% done, finished in 2:26
> ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [block -1637719248]
> : count=8192
> ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719248
> ]: count=512
> ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719247
> ]: count=512
> ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719246
> ]: count=512
> ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719245
> ]: count=512
> ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719244
> ]: count=512
> ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719243
> ]: count=512
> ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719242
> ]: count=512
> ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719241
> ]: count=512
> ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719240
> ]: count=512
> ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719239
> ]: count=512
> ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719238
> ]: count=512
> ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719237
> ]: count=512
I had an fsck that produced messages with the same sector numbers last
night, just after a panic. As it turned out /var and /opt3, which is
normally empty and was used for the first time, were overlapping, causing
filesystem corruption. Could it be that your filesystem is corrupted as
mine was last night?
The other possibility is that the filesystem was actively being written to
while the dump was taken (very bad idea).
I think you need to perform an fsck on that filesystem to at least
verify that it is O.K.
Good thing my filesystem corruption occurred at home and not at work.
Regards, Phone: (250)387-8437
Cy Schubert Fax: (250)387-5766
Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca
ITSD
Province of BC
"e**(i*pi)+1=0"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912291323.FAA06712>