Date: Sat, 09 Nov 2002 18:00:07 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Larry Sica <lomifeh@earthlink.net> Cc: Nick Rogness <nick@rogness.net>, freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem corruption Message-ID: <45812.1036861207@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 09 Nov 2002 11:55:06 EST." <FFCEB30D-F403-11D6-BCF2-000393A335A2@earthlink.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <FFCEB30D-F403-11D6-BCF2-000393A335A2@earthlink.net>, Larry Sica wri tes: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Not sure if hackers is the correct place to ask about this but... > >On Friday, November 8, 2002, at 06:28 PM, Nick Rogness wrote: > >> >> We have a server that is doing some wierd things. /var/mail filesystem >> (/dev/idad2s1e) is reporting errors during certain tasks (like dump). >> It does fsck clean umounted. I have yet to see this type of error and >> can't tell whether this is a bug or a hardware problem: >> >> Nov 8 15:41:20 pop1 /kernel: dscheck(#idad/0x20014): negative b_blkno >> -791620152 >> Nov 8 15:41:20 pop1 /kernel: dscheck(#idad/0x20014): negative b_blkno > >I've seen mention of this before, not sure what the fix was. I heard >about this a few years ago on some quantam drives, the guy updated his >firmware and it went away iirc. Does it do this only when you dump or >under other circumstances? If other circumstances, which ones? The fix is to not run dump(8) on a live filesystem. You should either use a snapshot or umount the device. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45812.1036861207>