On Sat, Dec 06, 2003 at 10:47:46AM +0100, Arjan van Leeuwen wrote: Content-Description: signed data > On Saturday 06 December 2003 05:33, Bruce Evans wrote: > > On Fri, 5 Dec 2003, Arjan van Leeuwen wrote: > > > > On Thursday 27 November 2003 10:43, Stefan Ehmann wrote: > > > > > This is a known problem for nearly three months now (See PR 56675). > > > > > It happens to me every time I shut down the system if i don't unmount > > > > > my (read-only) ext2 file systems manually. > > > > > > FYI, I'm still seeing this problem on a -CURRENT system from today. Is > > > there any way I can help to diagnose the cause of this problem? Is there > > > already a fix available somewhere? > > > > No need. It was diagnosed over 3 months ago (see PR 56675). I don't know > > of any publicly available fix. My version of ext2fs avoids the bug by > > doing buffering differently. > > > > As a workaround, unmount ext2fs file systems before rebooting. > > Unmounting most file systems before rebooting should be the default > > anyway (handled by shutdown(8) and reboot(8)), since unmounting may > > fail and vfs_unmountall() in the kernel has no good way to log errors. > > Thanks. It won't help though, as I don't have any ext2fs file systems, only > UFS. Also, my problem isn't 3 months old - I'm only seeing it since a few > weeks. > I've been seeing this problem for a good few months now - if I boot into single-user mode (using boot -s), fsck the (UFS2 only) disks and then type 'reboot', the system will always give up on at least 1 buffer, sometimes even 4 or 5. Of course, since / was mounted ro the filesystem is still clean when the system is rebooted, but it seems something thinks there's data to be written to a read-only filesystem! The root filesystem is UFS2 without softupdates. -- Bruce CranReceived on Sat Dec 06 2003 - 07:49:04 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:32 UTC