Date: Thu, 17 Feb 2000 18:03:09 -0600 (CST) From: David La Croix <dlacroix@cowpie.acm.vt.edu> To: freebsd-questions@freebsd.org Cc: dlacroix@acm.vt.edu Subject: Dump backup continues past 100%? Message-ID: <200002180003.TAA25966@cowpie.acm.vt.edu>
next in thread | raw e-mail | index | archive | help
Anybody seen this before? > uname -a FreeBSD host 3.3-STABLE FreeBSD 3.3-STABLE #0: Wed Oct 20 11:01:18 CDT 1999 root@host:/usr/src/sys/compile/DEMO BSD i386 On this system that has been working great for a while, I've just noticed the following very very strange behavior: Dump at level 0 wants to run forever. This box is backed up by Amanda nightly, and last night's backup was attempting to do a level 0 backup on the /usr partition: /dev/wd0s2f 3775773 2731543 742169 79% /usr While the dump is running, it seems to work as normal until it reaches the 100%, when the percents continue to climb forever while the time remaining gets more and more negative. DUMP: Date of this level 0 dump: Thu Feb 17 16:39:56 2000 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rwd0s2f (/usr) to standard output DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 2829217 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 3.73% done, finished in 2:09 DUMP: 30.87% done, finished in 0:22 DUMP: 92.41% done, finished in 0:01 DUMP: 153.37% done, finished in 0:-6 DUMP: 209.36% done, finished in 0:-13 DUMP: 268.54% done, finished in 0:-18 DUMP: 325.70% done, finished in 0:-24 DUMP: 383.95% done, finished in 0:-29 DUMP: 446.80% done, finished in 0:-34 DUMP: 510.96% done, finished in 0:-40 DUMP: 575.74% done, finished in 0:-45 DUMP: 639.93% done, finished in 0:-50 DUMP: 704.17% done, finished in 0:-55 DUMP: 766.86% done, finished in -1:00 ^C DUMP: Interrupt received. ... This continues forever, I've let it go as far as 2000% done. While the machine is rock stable, fsck finds nothing wrong, I'm completely puzzled by this strange behavior of dump. I've brought the machine down to single user mode, unmounted /usr, fscked it and found NOTHING wrong. du and recursive finds behave normally, so I have no clue what might be wrong, if it's the disk or a problem with dump. This machine has a 6 Gig "Bigfood" type IDE disk, 256Mb ram, and K6-2/300 CPU, not that I think that hardware might have anything to do with this particular problem. Searching the dump binary with strings /sbin/dump |egrep '^\$.+\$$' gives: $FreeBSD: src/lib/libc/i386/sys/fork.S,v 1.7.2.1 1999/08/29 14:46:59 peter Exp $ $FreeBSD: src/lib/libc/i386/gen/setjmp.S,v 1.8.2.1 1999/08/29 14:46:38 peter Exp $ $FreeBSD: src/lib/libc/i386/string/strrchr.S,v 1.4.2.1 1999/08/29 14:46:54 peter Exp $ $FreeBSD: src/lib/libc/i386/string/index.S,v 1.4.2.1 1999/08/29 14:46:48 peter Exp $ $FreeBSD: src/lib/libc/i386/string/strcat.S,v 1.4.2.1 1999/08/29 14:46:51 peter Exp $ $FreeBSD: src/lib/libc/i386/string/bcmp.S,v 1.4.2.1 1999/08/29 14:46:47 peter Exp $ $FreeBSD: src/lib/libc/i386/string/strncmp.S,v 1.5.2.1 1999/08/29 14:46:54 peter Exp $ $FreeBSD: src/lib/libc/i386/string/strchr.S,v 1.4.2.1 1999/08/29 14:46:52 peter Exp $ $FreeBSD: src/lib/libc/i386/string/strcpy.S,v 1.4.2.1 1999/08/29 14:46:52 peter Exp $ $FreeBSD: src/lib/libc/i386/string/strcmp.S,v 1.4.2.1 1999/08/29 14:46:52 peter Exp $ $NetBSD: bcopy.S,v 1.6 1996/11/12 00:50:06 jtc Exp $ $FreeBSD: src/lib/libc/i386/string/bzero.S,v 1.4.2.1 1999/08/29 14:46:48 peter Exp $ $FreeBSD: src/lib/libc/i386/string/memchr.S,v 1.7.2.1 1999/08/29 14:46:49 peter Exp $ $NetBSD: bcopy.S,v 1.6 1996/11/12 00:50:06 jtc Exp $ $FreeBSD: src/lib/libc/i386/string/memset.S,v 1.4.2.1 1999/08/29 14:46:51 peter Exp $ $NetBSD: bcopy.S,v 1.6 1996/11/12 00:50:06 jtc Exp $ $FreeBSD: src/lib/libc/i386/sys/sigprocmask.S,v 1.6.2.1 1999/08/29 14:47:08 peter Exp $ $FreeBSD: src/lib/libc/i386/sys/brk.S,v 1.6.2.1 1999/08/29 14:46:58 peter Exp $ $FreeBSD: src/lib/libc/i386/sys/sbrk.S,v 1.6.2.1 1999/08/29 14:47:06 peter Exp $ $FreeBSD: src/lib/libc/i386/sys/cerror.S,v 1.9.2.1 1999/08/29 14:46:59 peter Exp $ $FreeBSD: src/lib/libc/i386/sys/sigsuspend.S,v 1.7.2.1 1999/08/29 14:47:08 peter Exp $ $FreeBSD: src/sbin/dump/itime.c,v 1.2.2.1 1999/08/29 15:12:53 peter Exp $ $FreeBSD: src/sbin/dump/main.c,v 1.18.2.2 1999/08/29 15:12:53 peter Exp $ $FreeBSD: src/sbin/dump/optr.c,v 1.5.2.2 1999/09/03 08:48:51 jkh Exp $ $FreeBSD: src/sbin/dump/dumprmt.c,v 1.13.2.1 1999/08/29 15:12:52 peter Exp $ $FreeBSD: src/sbin/dump/tape.c,v 1.10.2.1 1999/08/29 15:12:54 peter Exp $ $FreeBSD: src/sbin/dump/traverse.c,v 1.8.2.1 1999/08/29 15:12:55 peter Exp $ $FreeBSD: src/sbin/dump/unctime.c,v 1.2.2.1 1999/08/29 15:12:56 peter Exp $ $FreeBSD: src/lib/libc/gen/err.c,v 1.5.2.1 1999/08/29 14:46:06 peter Exp $ $FreeBSD: src/lib/libc/yp/yplib.c,v 1.30.2.1 1999/08/29 14:49:43 peter Exp $ $FreeBSD: src/lib/libc/yp/xdryp.c,v 1.8.2.1 1999/08/29 14:49:42 peter Exp $ $FreeBSD: src/include/rpcsvc/yp.x,v 1.11.2.1 1999/08/29 14:39:19 peter Exp $ $FreeBSD: src/lib/libc/i386/gen/isinf.c,v 1.5.2.1 1999/08/29 14:46:36 peter Exp $ $FreeBSD: src/lib/libc/net/ns_netint.c,v 1.1.2.1 1999/08/29 14:47:28 peter Exp $ $FreeBSD: src/lib/libc/net/ns_name.c,v 1.1.2.1 1999/08/29 14:47:28 peter Exp $ $FreeBSD: src/lib/libc/net/ns_print.c,v 1.1.2.1 1999/08/29 14:47:29 peter Exp $ $FreeBSD: src/lib/libc/net/ns_parse.c,v 1.1.2.1 1999/08/29 14:47:28 peter Exp $ $FreeBSD: src/lib/libc/net/base64.c,v 1.2.2.1 1999/08/29 14:47:16 peter Exp $ $FreeBSD: src/lib/libc/net/ns_ttl.c,v 1.1.2.1 1999/08/29 14:47:29 peter Exp $ I'm extremely paranoid about this... anybody have any ideas? Has anybody else seen this kind of behavior? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002180003.TAA25966>