Package: linux-image-2.6-686 Version: 2.6.25+14 Severity: normal
Thanks for maintaining debian's kernel packages. They're a remarkable technology in more ways than one. Here's how I duplicate the bug. 1.) $ shutdown -r now 2.) ctl-alt-F7 3.) look quickly for something like "mount: / is busy" 4.) After the system has rebooted, if the root filesystem is EXT3, look for EXT3-fs: INFO: recovery required on readonly filesystem. in /var/log/messages. If the root filesystem is EXT2, I get a long, slow fsck recovery. It seems to me that this can be partially explained by the shutdown command running a script named /etc/init.d/umountroot which calls the "mount" command to remount the root file system as read only. It fails, and complains that "/ is busy" Since the root file system wasn't cleanly unmounted, it'll be recovered during the next boot. I investigated other processes interfering with the root file system, without result. However, it seems that inserting "cat /proc/mounts" just before the (re)mount command in /etc/init.d/umountroot usually allows mount to complete. As an aside, the words "mount" and "remount" occur hundreds of times in the changelog for 2.6.26. Frankly, I'm a little worried about data corrutpion. Thanks, Kingsley -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.25-2-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages linux-image-2.6-686 depends on: ii linux-image-2.6.25-2-686 2.6.25-6 Linux 2.6.25 image on PPro/Celeron linux-image-2.6-686 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]