Can anyone confirm whether this bug is still present in 12.10? I think
this may be addressed by the reworking or asynchronous mounting that was
done in mountal 2.42. If so, the mountall part of this bug should be
resolved once that change is backported (to 12.04).
I think the 'nolock' side of things is not yet resolved. The statd job
is still 'start on local-filesystems'. Can someone using NFS root
confirm that changing this to 'virtual-filesystems' does the right thing
on boot?
** Also affects: portmap (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: mountall (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: portmap (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: mountall (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: portmap (Ubuntu Raring)
Importance: Medium
Assignee: Steve Langasek (vorlon)
Status: Fix Released
** Also affects: mountall (Ubuntu Raring)
Importance: Medium
Status: In Progress
** Changed in: mountall (Ubuntu Precise)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/537133
Title:
mountall issues with NFS root filesystem
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/537133/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
