fstab in Tiger Server

[skaffen]

OK, quick question, does fstab still work in Tiger Server for stopping a drive from mounting? I’m trying to stop an Xserve RAID from mounting on the secondary server out of a failover pair. I’ve created the /etc/fstab file and added:

[code]LABEL=XserveRAID none hfs xx[/code]

I’ve tried it using the UUID of the drive as well. I’ve then also done the:

[code]sudo niload -d -v / < /etc/fstab[/code] but that just returns the error: [code]0 items read from input[/code] I've had something similar working under Panther server before but I just can't get this up and running and I'm not sure if I've forgotten something, there's a bug going on, or this simply doesn't work under 10.4 server. Any help greatly appreciated.

[skaffen]

Thanks for the reply, the niload bit was a bit of a “try and hope” attempt really because the fstab entry didn’t seem to be working at all and I saw the niload command mentioned by a few people. I’d already seen your article on IP Failover and I’m pretty sure that I’ve got the fstab OK, it just doesn’t appear to do anything (and there’s no obvious errors in the logs). Will have to try rebuilding the server from scratch and see if it’s just not happy with something at the moment.

[pingu]

I’ve done a bit of digging into this and it looks like using ‘xx’ actually means that diskarbitrationd and others should completely ignore the record in fstab rather than not mount it.

man fstab states: –
[quote]
If fs_type is specified as “xx” the entry is ignored. This is useful to show disk partitions which are currently unused.
[/quote]

Have you tried
[code]LABEL=XserveRAID none hfs rw,noauto[/code]

This worked for us.

Dan

[skaffen]

[QUOTE][u]Quote by: pingu[/u]

[code]LABEL=XserveRAID none hfs rw,noauto[/code][/QUOTE]

Thanks! That sorted it, all the examples I had seen all used xx so I presumed that that bit was right! Just changed it to …none hfs ro,noauto and that worked straight away.

Cheers.

Skaff.

[pingu]

Just as a quick update BTW…

Even if a volume is formatted as HFS+, you must still list it in fstab as ‘hfs’. Listing it as ‘hfs+’ seems to cause diskarbitrationd and possibly others (mount etc) to ignore the line (I suspect they see it as an syntax error).

D

[Author]

Posts