On Fri, 2010-05-14 at 13:20 +0000, Steve Langasek wrote: > There is no nfs-utils maintainer in Ubuntu, but as a frequent uploader > of the package, I don't agree that it's a problem at all to try to mount > NFS filesystems before statd starts. The only problem is if mountall > fails to *retry* the mount once statd *does* start.
This sounds *very* race prone to me. Discarding proper ordering, hoping that a "mop up" later will fix things is just bad design, IMHO. There really is no need for it. ISTM that mountall is simply trying to do too much work all at once and too hastily. It is interesting that there is already mountall-net.conf which tells mountall (via SIGUSR1) when a network interface has become available. Perhaps mountall needs to be told when NFS (or any number of filesystems that have prerequisites) is fully available and wait for that before mounting NFS filesystems. Or mountall needs to be split into multiple tools and/or have multiple personalities which can be called to mount different filesystem (types) when the prerequisites for such filesystems have been met. > Since you say the NFS filesystem does eventually get mounted, So far. But I will not be holding my breath on that. > I regard > the extra messages about failed mount attempts to be a 'wontfix' issue. That's a pity. "Cleanliness" should be every developer's goal. i.e. it should not be simply accepted that "yeah, well there will be error messages on boot, but you can ignore them" because it creates an environment of complacency where all errors are ignored. "but you told me i could ignore errors on boot -- oh, not these error messages, just those other ones? how am i to know which errors i can ignore and which ones i can't?" -- mountall tries to mount NFS filesystem before statd starts https://bugs.launchpad.net/bugs/547139 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
