Date: Fri, 10 Nov 2000 07:30:02 -0800 (PST) From: Bruce Evans <bde@zeta.org.au> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/22726: mkfifo can cause ext2fs to break sync at shutdown Message-ID: <200011101530.HAA47388@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/22726; it has been noted by GNATS.
From: Bruce Evans <bde@zeta.org.au>
To: Jimmy <olgeni@uli.it>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/22726: mkfifo can cause ext2fs to break sync at shutdown
Date: Sat, 11 Nov 2000 02:21:22 +1100 (EST)
On Thu, 9 Nov 2000, Jimmy wrote:
> >Synopsis: mkfifo can cause ext2fs to break sync at shutdown
Syncing at unmount time was actually broken for all types of files.
This is now fixed in -current. The commit message was:
---
Quick fix for not writing group descriptor group, inode bitmaps or
^^^^^ oops, should be "blocks"
block bitmaps before unmount() completes. They were written using
bdwrite(), so they were normally written less than 32 seconds after
unmount(), but this is too late if the media is removed or the system
is rebooted soon after unmount(). sync()ing before unmount() didn't
help, because ext2fs uses buggy private caching for these blocks --
it doesn't even bdwrite() them until they are uncached or the filesystem
is unmounted. sync()ing after unmount() didn't help, because sync()
only applies to (vnodes for) mounted filesystems.
---
> >How-To-Repeat:
Thanks for the detailed instructions.
> >Fix:
>
> Running shutdown with the media still in the drive helps, but I didn't
> try to insert a different disk and see what gets written.
FreeBSD now retries until shutdown after write errors, so inserting the
same disk is a safe workaround, but inserting a different disk will
clobber that disk.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011101530.HAA47388>