| 2010-04-20 23:08:01 |
Aurélien Begel |
bug |
|
|
added bug |
| 2010-04-20 23:08:01 |
Aurélien Begel |
attachment added |
|
Dependencies.txt http://launchpadlibrarian.net/44927866/Dependencies.txt |
|
| 2010-04-20 23:10:01 |
Aurélien Begel |
description |
On my desktop computer, (which has separate volumes for /, /usr, /var, /tmp,etc.) statd fail to start, and then autofs later fails to mount NFS volumes.
This problem does not appear on my laptop computer that only has one volume for the whole filesystem, so I think that is a race condition between statd starting and /usr mounting. Indeed, reading /etc/init/statd.conf I can see that statd is ran after portmap. Portmap can start only with / mounted, because it is located in /sbin, however statd is located in /usr and so we have to wait for /usr to be mounted.
I suggest the following fix:
in /etc/init/statd.conf, replace "start on" clause (line 6) with:
start on ((started portmap and local-filesystems) or mounting TYPE=nfs)
(was: start on (started portmap or mounting TYPE=nfs)
On my computer this fixes the issue, nevertheless I am not sure whether this will suit all cases.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nfs-common 1:1.2.0-4ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Wed Apr 21 00:52:06 2010
ProcEnviron:
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: nfs-utils |
On my desktop computer, (which has separate volumes for /, /usr, /var, /tmp,etc.) statd fail to start, and then autofs later fails to mount NFS volumes.
This problem does not appear on my laptop computer that only has one volume for the whole filesystem, so I think that is a race condition between statd starting and /usr mounting. Indeed, reading /etc/init/statd.conf I can see that statd is ran after portmap. Portmap can start with only / mounted, because it is located in /sbin, however statd is located in /usr and so we have to wait for /usr to be mounted.
I suggest the following fix:
in /etc/init/statd.conf, replace "start on" clause (line 6) with:
start on ((started portmap and local-filesystems) or mounting TYPE=nfs)
(was: start on (started portmap or mounting TYPE=nfs)
On my computer this fixes the issue, nevertheless I am not sure whether this will suit all cases.
Please tell me if you need more details or logs.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nfs-common 1:1.2.0-4ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Wed Apr 21 00:52:06 2010
ProcEnviron:
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: nfs-utils
|
|
| 2010-04-20 23:10:27 |
Aurélien Begel |
description |
On my desktop computer, (which has separate volumes for /, /usr, /var, /tmp,etc.) statd fail to start, and then autofs later fails to mount NFS volumes.
This problem does not appear on my laptop computer that only has one volume for the whole filesystem, so I think that is a race condition between statd starting and /usr mounting. Indeed, reading /etc/init/statd.conf I can see that statd is ran after portmap. Portmap can start with only / mounted, because it is located in /sbin, however statd is located in /usr and so we have to wait for /usr to be mounted.
I suggest the following fix:
in /etc/init/statd.conf, replace "start on" clause (line 6) with:
start on ((started portmap and local-filesystems) or mounting TYPE=nfs)
(was: start on (started portmap or mounting TYPE=nfs)
On my computer this fixes the issue, nevertheless I am not sure whether this will suit all cases.
Please tell me if you need more details or logs.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nfs-common 1:1.2.0-4ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Wed Apr 21 00:52:06 2010
ProcEnviron:
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: nfs-utils
|
On my desktop computer, (which has separate volumes for /, /usr, /var, /tmp,etc.) statd fail to start, and then autofs later fails to mount NFS v3 volumes.
This problem does not appear on my laptop computer that only has one volume for the whole filesystem, so I think that is a race condition between statd starting and /usr mounting. Indeed, reading /etc/init/statd.conf I can see that statd is ran after portmap. Portmap can start only with / mounted, because it is located in /sbin, however statd is located in /usr and so we have to wait for /usr to be mounted.
I suggest the following fix:
in /etc/init/statd.conf, replace "start on" clause (line 6) with:
start on ((started portmap and local-filesystems) or mounting TYPE=nfs)
(was: start on (started portmap or mounting TYPE=nfs)
On my computer this fixes the issue, nevertheless I am not sure whether this will suit all cases.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nfs-common 1:1.2.0-4ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Wed Apr 21 00:52:06 2010
ProcEnviron:
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: nfs-utils
|
|
| 2010-04-21 10:23:02 |
Steve Langasek |
marked as duplicate |
|
525154 |
|
