Messages in this thread | | | Date | Thu, 01 Apr 1999 08:15:06 +0200 | From | Olivier Chapuis <> | Subject | Re: just installed 2.2.5 (upgraded from 2.0.0) |
| |
> I just compiled and installed kernel 2.2.5 on my Slackware box. Everytime I > shutdown now, it gives me the frightening sequence of messages: (I'm > paraphrasing, I didn't think to write them down last time, and I'm not at my > computer now.) > > Unmounting local file systems. > > umount: /dev/hda could not be unmounted or / is busy > > mount: / is busy, could not mount fs > > mount: (something else I can't recall) > > On next boot, fsck will be FORCED > > then, upon reboot, after checking hardware (and autodetecting all my PCI > devices - I love 2.2.x!) > > >fsck: deleted inode (5-digit number, always [so far] starting with 40xxx) has > zero dtime. Fix dtime? (system automatically answers yes, and it takes about 2 > minutes to recover from each inode found with this problem - one time, it > found 5 inodes with bad dtimes, adding a full 10 minutes to my boot!)
Hi, The Documentation/changes suggests that this is a problem with ld.so and a glibc bug. I have got a similar problem with ld.so-1.9.5 (1.9.9 is recommended) and the glibc-2.0.7 from the update of RH5.1 (ldconfig cause the bad shutdown for me). I upgrade my ld.so but this change nothing. So I take the src of the glibc-2.0.7 from the RH5.2 and compile-install it. After this no more problem ... Hope this help for your situation, Olivier
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |