On Sat, 9 Nov 2002, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, 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.
I've been running dump for years on live filesystems with FreeBSD
and never had a problem. I was not aware of any snapshot feature
available for 4.X-STABLE (only 5.0)?
umounting a live filesystem to back it up is not a solution. What
should I be using to backup a live filesystem?
Nick Rogness <[EMAIL PROTECTED]>
-
"Wouldn't it be great if we could answer people with a
kick to the crotch?" [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
