"Kevin Oberman" <oberman_at_es.net> writes: >> Date: Wed, 26 Nov 2003 19:37:45 +0100 >> From: Matthias Andree <matthias.andree_at_gmx.de> >> Sender: owner-freebsd-current_at_freebsd.org >> >> Hi, >> >> when I rebooted my 5.2-BETA (kernel about 24 hours old), it gave up on >> flushing 4 dirty blocks. >> >> I had three UFS1 softdep file systems mounted on one ATA drive, one ext2 >> file system on another ATA drive and one ext2 file system on a SCSI >> drive. Both ext2 file systems had been mounted read-only, so they can't >> have had dirty blocks. >> >> At the next reboot, FreeBSD checked all three UFS file systems as they >> hadn't been umounted cleanly before. Makes me wonder if FreeBSD gave up >> on the super blocks... > > This looks like a GEOM related issue, although I am not completely sure > of this. > > I have observed the following: > System dies leaving the file systems dirty. (File systems have > soft-updates enabled.) > I reboot to single user and fsck all partitions including the root. > I halt or reboot. > I get a number of dirty buffers and the syncer eventually gives up. > > If I issue a "mount -u /" before shutting down, the problem does not > occur. Why I should be able to get dirty buffers on a file system that > has never been mounted as RW, I don't understand, but I see it every > time I reboot after a crash. It happened to me many times on various machines. Some running 4.x, so no GEOM. I wonder why all the file systems are marked dirty. The buffers are associated with specific device anyway. /SReceived on Wed Nov 26 2003 - 10:03:28 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:31 UTC