retry remote devices when parent is ready after SIGUSR1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Release Notes for Ubuntu |
Won't Fix
|
Undecided
|
Unassigned | ||
mountall (Ubuntu) |
Fix Released
|
Medium
|
Scott James Remnant (Canonical) | ||
Bug Description
Binary package hint: mountall
Hi,
I have a similar problem like in https:/
I think my problem is more related to https:/
Release: Ubuntu 9.10
This is what happens:
- Grub (still old Grub) line is: /vmlinuz-
- root is mounted readonly due to Grubline
- After Network is up, mountall receives SIGUSR1 (as expected)
- At this time root is not yet remounted RW and NFS-Shares cannot be mounted:
usr1_handler: Received SIGUSR1 (network device up)
try_mount: /Bignfs waiting for /
try_mount: /Backnfs waiting for /
usr1_handler: Received SIGUSR1 (network device up)
try_mount: /Bignfs waiting for /
try_mount: /Backnfs waiting for /
- After root is remounted, NFS-Shares will not be mounted as they are waiting for SIGUSR1
try_mount: /Bignfs waiting for device gigakobold.
try_mount: /Backnfs waiting for device gigakobold.
- mountall will continue running
- Sending SIGUSR1 manually will get everything mounted and mountall exits normally
So the problem is: Mountall doesn't remember having SIGUSR1 (i.e. network up) already received.
So if there is a problem with NFS-mounts while signal from network up is received and the NFS-filesystems cannot be mounted at this time, later retries will not work, too.
Regards
Markus
Changed in mountall (Ubuntu): | |
status: | Triaged → Fix Committed |
milestone: | none → lucid-alpha-2 |
assignee: | nobody → Scott James Remnant (scott) |
tags: | added: verification-needed |
description: | updated |
Your assumption is, I think, correct. When SIGUSR1 is received, it tries to bring up the mount but fails because the parent mount isn't yet ready. When it brings up the parent, it hasn't remembered that it can bring up the network mount, so waits for SIGUSR1 again