Date: Mon, 19 Aug 1996 01:25:20 -0400 (EDT) From: "Marc G. Fournier" <scrappy@ki.net> To: ccd@stampede.cs.berkeley.edu Cc: stable@freebsd.org Subject: ccd and/or fsck bug in "current" stable Message-ID: <Pine.NEB.3.95.960819011027.15508B-100000@quagmire.ki.net>
next in thread | raw e-mail | index | archive | help
Hi... Last week, I decided to play around with the CCD support that exists in 2.1.5R and above, so upgraded my kernel and ccd'd my news parititions into one big drive...works beautiful... Except, last nihgt, I started seeing my machine reboot every 20min, like clockwork. Night, I got down to the office and watched it reboot, with the following error: /news/spool: bad dir ino 614809 at offset 8192: mangled entry panic: bad dir Watching it reboot, fsck just reported that the clean flag wasn't set in the super block, set it, and the system back back up again...so fsck didn't find the mangled entry... Using 'find /news/spool -inum 614809 -print', I found the offending inode to belong to /news/spool/alt/books/review, which, after removing all the contents from the directory, gives me: news> ls -litd reviews 614809 drwxrwxr-x 2 news news 14848 Aug 19 00:41 reviews news> rmdir reviews rmdir: reviews: Directory not empty news> ls -lta reviews total 10 drwxrwxr-x 2 news news 14848 Aug 19 00:41 . drwxrwxr-x 45 news news 1536 Aug 18 17:21 .. news> And, running an fsck against the unmounted spool comes back with: ki# fsck -y /dev/ccd0c ** /dev/rccd0c ** Last Mounted on /news/spool ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 223864 files, 637541 used, 621322 free (46786 frags, 71817 blocks, 3.7% fragmentation) Shouldn't fsck find that mangled directory? How did it get mangled in the first place? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.95.960819011027.15508B-100000>