| 2010-08-07 05:48:00 |
Gerald Villemure |
bug |
|
|
added bug |
| 2010-08-07 05:48:00 |
Gerald Villemure |
attachment added |
|
A working work-around http://launchpadlibrarian.net/53212583/mountall2.tar.gz |
|
| 2010-08-10 16:47:03 |
Gerald Villemure |
description |
Binary package hint: mountall
The current implementation of mountall in Lucid is rather dangerous if you don't have console access.
It will effectively hang your boot process if anything goes wrong. (MD did not get assembled, data drive is offline, etc.) If you don’t have console access to press "s", your out of luck.
For those like me that administer their server remotely the historic solution was to ensure serial console access. But even then, you don’t see anything when connecting, so you can press "s" and HOPE for the best.
There is another issue here, the fundamental idea that a system is an all or nothing solution. Why is it that the data drive needs to be online and mounted BEFORE I can get SSH access? I have systems that run both Asterisk and Samba and I find it inappropriate that Asterisk needs to WAIT for Samba’s Data drive to get online before Asterisk can start. We need a SMARTER start process that is NOT all or nothing, it is OKAY to mount some filesystems later when they are ready, and not hold up the whole system.
I wrote a small script called "mountall2" which mounts the non-root filesystems later in the boot process (last actually) and does so in a way that make diagnostics and recovery POSSIBLE.
Every filesystem is FSCK and MOUNTED just like mountall but it is done in parallel and inside a "screen" session. If you have console you can check the FSCK progress on TTY13+ by pressing <RIGHTALT>+<F1> etc. But if you don’t have physical access to the machine you can SSH into the box and use "screen –x .." to see the FSCK progress.
The script will also call postmount scripts if present since there are times where you will need to notify NFS or some other app that the filesystem is now online. Ideally upstart scripts could be predicated on a filesystem being available and auto start the task when the FS come online.
To use, untar the script somewhere like /usr/local and add this line to /etc/rc.local:
/usr/local/mountall2/mountall2 &
Then edit your /etc/fstab to add the noauto options and set the FSCK field to a 3
Original setup:
UUID=b97af687-8a45-4197-89d4-fb62b4feb0d1 /boot ext4 defaults 0 2
New setup:
UUID=b97af687-8a45-4197-89d4-fb62b4feb0d1 /boot ext4 defaults,noauto 0 3
The "noauto" option will prevent the native "mountall" from touching the entry. Make SURE there is no space between the 3 and the end of the line.
The postmount scripts need to have the same name as the mount point so if your mount point is "/mnt/test" then create a file "postmount/mnt/test" script with your commands. There is a sample "postmount/Media" in the tar file.
Hopefully something of similar functionality will become integrated into the distro.
Gérald |
Binary package hint: mountall
The current implementation of mountall in Lucid is rather dangerous if you don't have console access.
It will effectively hang your boot process if anything goes wrong. (MD did not get assembled, data drive is offline, etc.) If you don’t have console access to press "s", your out of luck.
For those like me that administer their server remotely the historic solution was to ensure serial console access. But even then, you don’t see anything when connecting, so you can press "s" and HOPE for the best.
There is another issue here, the fundamental idea that a system is an all or nothing solution. Why is it that the data drive needs to be online and mounted BEFORE I can get SSH access? I have systems that run both Asterisk and Samba and I find it inappropriate that Asterisk needs to WAIT for Samba’s Data drive to get online before Asterisk can start. We need a SMARTER start process that is NOT all or nothing, it is OKAY to mount some filesystems later when they are ready, and not hold up the whole system.
I wrote a small script called "mountall2" which mounts the non-root filesystems later in the boot process (last actually) and does so in a way that make diagnostics and recovery POSSIBLE.
Every filesystem is FSCK and MOUNTED just like mountall but it is done in parallel and inside a "screen" session. If you have console you can check the FSCK progress on TTY13+ by pressing <RIGHTALT>+<F1> etc. But if you don’t have physical access to the machine you can SSH into the box and use "screen –x .." to see the FSCK progress.
The script will also call postmount scripts if present since there are times where you will need to notify NFS or some other app that the filesystem is now online. Ideally upstart scripts could be predicated on a filesystem being available and auto start the task when the FS come online.
To use, untar the script somewhere like /usr/local and add this line to /etc/rc.local:
/usr/local/mountall2/mountall2 &
Then edit your /etc/fstab to add the noauto options and set the FSCK field to a 3
Original setup:
UUID=b97af687-8a45-4197-89d4-fb62b4feb0d1 /boot ext4 defaults 0 2
New setup:
UUID=b97af687-8a45-4197-89d4-fb62b4feb0d1 /boot ext4 defaults,noauto 0 3
The "noauto" option will prevent the native "mountall" from touching the entry. The FSCK check of 3 is a simple way of saying it should be check at the end of the system boot sequence.
The postmount scripts need to have the same name as the mount point with the / converted to underscores _, so if your mount point is "/mnt/test" then create a file "postmount/_mnt_test" script with your commands. There is a sample "postmount/_Media" in the tar file.
Hopefully something of similar functionality will become integrated into the distro.
Gérald
|
|
| 2010-08-10 16:50:10 |
Gerald Villemure |
attachment added |
|
mountall2.tar.gz http://launchpadlibrarian.net/53434401/mountall2.tar.gz |
|
| 2010-08-18 22:33:18 |
Erik Reuter |
bug |
|
|
added subscriber Erik Reuter |
| 2010-09-03 00:44:47 |
scm |
bug |
|
|
added subscriber scm |
| 2010-09-03 00:48:24 |
scm |
bug |
|
|
added subscriber Goobuntu Team |
| 2010-09-10 19:24:00 |
Gerald Villemure |
nominated for series |
|
Ubuntu Maverick |
|
| 2010-09-11 18:29:15 |
Aleks |
bug |
|
|
added subscriber ALIAKSANDR KALYBENKA |
| 2010-10-29 14:26:31 |
Gerald Villemure |
attachment removed |
A working work-around https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/614662/+attachment/1480113/+files/mountall2.tar.gz |
|
|
| 2010-11-23 20:28:29 |
Matej Kenda |
bug |
|
|
added subscriber Matej Kenda |
| 2011-03-29 12:39:18 |
gdowle |
bug |
|
|
added subscriber gdowle |
| 2011-08-20 10:40:13 |
Launchpad Janitor |
mountall (Ubuntu): status |
New |
Confirmed |
|
| 2011-08-25 07:01:48 |
Nicolas Jungers |
bug |
|
|
added subscriber Nicolas Jungers |
| 2012-01-05 16:13:51 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2012-01-05 16:13:59 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Review Team |
| 2012-02-23 20:41:26 |
Jostein Martinsen |
bug |
|
|
added subscriber Jostein Martinsen |
| 2012-05-19 06:30:35 |
Steve Langasek |
mountall (Ubuntu): status |
Confirmed |
Invalid |
|
