after fsck on startup, no network filesystems are shown in mtab

[disabled.user]

Whenever a file system check (possibly only affects the root file system) happens on system boot (due to maximum mount count or check interval reached on ext3), after system startup is complete, no network shares from fstab show up in mtab, but the shares have been mounted. I've noticed this behaviour since Dapper, Gutsy is still affected, don't know for Hardy.

It may seem more like a cosmetical bug, but imagine this:
Multiple NFS- and CIFS shares are mounted via fstab from servers which are connected via remote VPN connections. Now, after a "normal" (without fsck) startup, network mounts show up in mtab an therefore won't be scanned when slocate runs, because the default behaviour of slocate won't scan on network file systems. But if the network mounts don't show up in mtab, slocate won't notice that network mounts actually are network mounts, and therefore scans them like normal, local subdirectories.

A possible solution for this would be changing /etc/updatedb.conf, but this would only be a workaround and wouldn't solve the original problem.

[Saivann Carignan (oxmosys)]

Thanks for your bug report. Since this issue affect CIFS / fsck, shouldn't that be a linux of fsck bug rather than a usplash bug? Is there something related to usplash in that bug?

[Dereck Wonnacott (dereck)]

I'm sorry, being fairly new to Launchpad, I was misinformed that bugs that occur at boot-time should be moved to usplash. I have since learned much about bug management.

I'll try not to make the same mistake again, there are plenty of new ones to be made after all. :)

[disabled.user (disabled.user-deactivatedaccount)]

My guess would be something related to busybox-initramfs or initramfs-tools. fsck on the root file system on system boot happens while the system is still running from initrd.

[Leann Ogasawara (leannogasawara)]

I don't suppose you would be willing to test the Hardy Alpha release as that is currently under development: http://www.ubuntu.com/testing . Thanks.

[disabled.user (disabled.user-deactivatedaccount)]

I've tested the current Kubuntu Hardy Alpha within VMware Server running on Kubuntu Gutsy. It seems Hardy is NOT affected by this bug report, but Dapper up to Gutsy are. But since this is not a security related bug, my hopes for a fix for the stable releases aren't that high...

[Leann Ogasawara (leannogasawara)]

I'm glad to hear this is working in Hardy. Unfortunately you are correct that this does not qualify for a stable release update for earlier releases. I'm going to go ahead and close this as "Fix Released" against Hardy. Thanks.