There is still a race condition in mountall, proabably due to teh integration with plymouth boot screen.
Add/change events from udev are being dropped.
When I get the error, I press 'M', and sulogin. The links are there in /dev/<volume_group>, so I believe that udev is getting its job done, and letting mountall know about it.
two things should be done:
1) add code to try 2 mount attempts before giving up on a file system in /etc/fsta on boot.
2) Find the race and fix it.
1) is the belt and braces - not mounting file systems on boot is a SERIOUS problem.
Condition can be debugged when a machines running by creating a volume group with about 10 logical volumes, deactivating it with 'vgchange -a n /dev/<volume_group>, and then activating it. mountall would have to be running in a separate window, not issuing events to upstart init.
Further to above:
There is still a race condition in mountall, proabably due to teh integration with plymouth boot screen.
Add/change events from udev are being dropped.
When I get the error, I press 'M', and sulogin. The links are there in /dev/<volume_ group>, so I believe that udev is getting its job done, and letting mountall know about it.
two things should be done:
1) add code to try 2 mount attempts before giving up on a file system in /etc/fsta on boot.
2) Find the race and fix it.
1) is the belt and braces - not mounting file systems on boot is a SERIOUS problem.
Condition can be debugged when a machines running by creating a volume group with about 10 logical volumes, deactivating it with 'vgchange -a n /dev/<volume_ group>, and then activating it. mountall would have to be running in a separate window, not issuing events to upstart init.