Date: Fri, 18 May 2001 09:54:20 +0100 From: Brian Somers <brian@Awfulhak.org> To: John Baldwin <jhb@FreeBSD.ORG> Cc: current@FreeBSD.ORG, mckusick@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: background fsck Message-ID: <200105180854.f4I8sKb92664@hak.lan.Awfulhak.org> In-Reply-To: Message from John Baldwin <jhb@FreeBSD.ORG> of "Thu, 17 May 2001 14:31:55 PDT." <XFMail.010517143155.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This happens to me ``almost all the time'' on my dev box: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 254063 82600 151138 35% / devfs 1 1 0 100% /dev procfs 4 4 0 100% /proc /dev/ad0s1e 254063 7 233731 0% /tmp /dev/ad1s2a 496239 26424 430116 6% /var /dev/ad1s2e 4466254 1448160 2660794 35% /usr /dev/ad0s1f 775487 392540 320909 55% /usr/obj /dev/ad1s1a 10145116 5631076 3702432 60% /usr/ports/distfiles /dev/ad1s1e 10145116 4957632 4375876 53% /usr/audio /dev/ad1s1g 4963030 3621790 944198 79% /usr/packages /dev/ad1s1f 10145116 4790396 4543112 51% /cvs /dev/ad1s2f 33059676 1 30414901 0% /spare1 The interesting thing is that it always happens on /usr and /cvs and no other partitions. Both of these partitions have large directory hierarchies.... Also, FWIW it now takes nearly 30 minutes to fsck my laptop's disk (20Gb 5400rpm). That's not good.... > Has anyone else been trying out the background fsck? Last night I was working > on the ithread code some and managed to panic my laptop while ejecting a pccard. > Anyways, the kernel ate itself while trying to flush its buffers and I ended up > with a dirty filesystem. I rebooted and let fsck -p do its usual thing, except > that it freaked out. The actual fsck of / proceeded fine (actual fs activity > when I panic'd my machine was very low, so the filesystems weren't corrupted, > just marked dirty). When it got to /usr and /var, however, fsck freaked out > and claimed that the primary superblock didn't match the first alternate. At > this point I first had a heart attack. Once I recovered from that, I attempted > read-only mounts of /usr and /var which did succeed, except that each mount > spewed out a message to the kernel console about losing x files and y blocks. > Confident that my fs wasn't totally hosed after doing some ls's, I unmounted > /usr and /var and ran a non-preen fsck on them, which insisted on using an > alternate superblock, but otherwise proceeded fine (except that it seemed to > take longer than usual). Once the fscks's finished, it seemed to be all ok. > Is anyone else seeing any weird stuff like this? I've never had fsck complain > about the superblocks after a crash before. > > > df -t ufs > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/ad0s2a 148823 84717 52201 62% / > /dev/ad0s2f 10191770 7052563 2323866 75% /usr > /dev/ad0s2e 99183 14254 76995 16% /var > > mount -t ufs > /dev/ad0s2a on / (ufs, local) > /dev/ad0s2f on /usr (ufs, local) > /dev/ad0s2e on /var (ufs, local) > > grep ufs /etc/fstab > /dev/ad0s2a / ufs rw 1 1 > /dev/ad0s2f /usr ufs rw 2 2 > /dev/ad0s2e /var ufs rw 2 2 > > Hmm, that's odd, I did have soft updates on on /usr and /var before the crash. > It seems to be off now. :( > > -- > > John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ -- Brian <brian@Awfulhak.org> <brian@[uk.]FreeBSD.org> <http://www.Awfulhak.org>; <brian@[uk.]OpenBSD.org> Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105180854.f4I8sKb92664>