|
Home > Archive > Red Hat Topics > July 2006 > SANs and run levels -- question on best practices
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SANs and run levels -- question on best practices
|
|
|
| We have some production Red Hat Enterprise servers connected to an EMC
SAN. The SAN driver stuff gets started at run level 3 and the SAN
partitions are in the fstab.
I noticed the other day that things get a little nasty when booting to
single user. The SAN partitions can't be mounted, because the drivers
haven't been started, but the machine tries to fsck them anyway, barfs,
and asks for the single user password so you can repair the condition.
Well, that's where I was trying to get anyway, but I have to wonder if
there isn't a better way to do this. For various reasons we're stuck
with starting the SAN at run level 3. What are best practices? Ignore
SAN related errors on boot? Start the SAN earlier? Suppress fsck at
run level 0? (How?) My solutions so far are (1) ignore the issue, and
(2) put in some weird hack, like swapping around fstabs based on run
level. Hopefully, there's a more elegent answer.
Ron
| |
| Robert Nichols 2006-07-19, 1:21 pm |
| In article <1153252695.184568.192340@p79g2000cwp.googlegroups.com>,
Ron <98sport@gmail.com> wrote:
:We have some production Red Hat Enterprise servers connected to an EMC
:SAN. The SAN driver stuff gets started at run level 3 and the SAN
:partitions are in the fstab.
:
:I noticed the other day that things get a little nasty when booting to
:single user. The SAN partitions can't be mounted, because the drivers
:haven't been started, but the machine tries to fsck them anyway, barfs,
:and asks for the single user password so you can repair the condition.
:
:Well, that's where I was trying to get anyway, but I have to wonder if
:there isn't a better way to do this. For various reasons we're stuck
:with starting the SAN at run level 3. What are best practices? Ignore
:SAN related errors on boot? Start the SAN earlier? Suppress fsck at
:run level 0? (How?) My solutions so far are (1) ignore the issue, and
 2) put in some weird hack, like swapping around fstabs based on run
:level. Hopefully, there's a more elegent answer.
Is there some reason you can't just suppress the automatic fsck by
putting a "0" in field 6 (fs_passno) in the /etc/fstab entry for those
partitions?
--
Bob Nichols AT comcast.net I am "RNichols42"
|
|
|
|
|