Suse 9.1: Not all entries in fstab are mounted at boot. why?

BrianK · 06-29-2004, 02:51 PM

I don't know if this is distro-specific (there's no Suse distro forum anyway) so it goes here.

I've got this line in my fstab:

uranium:/job /job nfs bg,noac,rw,hard,rsize=16384,wsize=16384 0 0

but it doesn't get mounted when I boot up unless I su & mount -a.

Why is that?

Tinkster · 06-29-2004, 03:00 PM

man fstab

Just add auto to the rw, bit

Cheers,
Tink

BrianK · 06-29-2004, 03:11 PM

Quote:

Originally posted by Tinkster
man fstab

Just add auto to the rw, bit

no such luck.

auto should be on by default, the way I understand it, but just to make sure, I gave it a try & still have to do mount -a.

If auto wasn't on, I wouldn't be able to mount it with mount -a.

J.W. · 06-29-2004, 03:39 PM

Quote:

Originally posted by BrianK
/job /job nfs bg,noac,rw,hard,rsize=16384,wsize=16384 0 0

I think the problem is that you are specifying the mountpoint twice, rather than to specify the partition and the mount point. In other words, the first "/job" reference needs to be replaced with /dev/hdxy where x is the device and y is the partition, eg, /dev/hdd2 or whatever. -- J.W.

BrianK · 06-29-2004, 04:22 PM

Quote:

Originally posted by J.W.
I think the problem is that you are specifying the mountpoint twice, rather than to specify the partition and the mount point. In other words, the first "/job" reference needs to be replaced with /dev/hdxy where x is the device and y is the partition, eg, /dev/hdd2 or whatever. -- J.W.

well, the first "/job" is actually part of "uranium:/job" which is the way you tell nfs what it's mounting to - the /job directory on uranium.. The second job is the local mount point. Specifying the device path in either place would be incorrect becuase you're not mounting a device, you're mounting a directory.

btw: having this line in my Redhat boxes mounts everything at boot time. Maybe this has soemthing to do with automount or autofs?

J.W. · 06-30-2004, 01:44 AM

Sorry, missed the NFS bit. On both my Suse and Slack boxes, my fstab looks like this

Code:

/dev/hda9        /tmp             ext3        defaults         1   2
/dev/hda10       /var             ext3        defaults         1   2
/dev/hda11       /root            ext3        defaults         1   2
/dev/hda12       /home            ext3        defaults         1   2

hence my confusion -- J.W.

ggreen · 07-25-2004, 02:41 PM

it looks like it's been awhile since this thread started but i think that i might have an answer for you. i ran into a similar problem and it ended up that the fstab file was being read before the rpc services were started. so the nfs mouts in the fstab would fail but once everything got started i could manually mount things fine. i had to write a little script with the mount commands in it had it run after the rpc stuff started.

hope this helps

g

BrianK · 07-26-2004, 12:47 PM

Quote:

Originally posted by ggreen
it looks like it's been awhile since this thread started but i think that i might have an answer for you. i ran into a similar problem and it ended up that the fstab file was being read before the rpc services were started. so the nfs mouts in the fstab would fail but once everything got started i could manually mount things fine. i had to write a little script with the mount commands in it had it run after the rpc stuff started.

hope this helps

g

Hmm.. does that sound like a bug to you? It does to me.

I prefer to not have to write work-arounds when things don't work the way they should.

Thanks for the tip though, sounds like I'll go the script route as well unless someone knows of a better solution.

struthers · 08-19-2004, 06:22 PM

I have the same problem. I can mount the server manually or with mount -a, however it will not mount correctly on boot. I was just wondering if this problem was ever solved or if I should just write a script fix. It just seems to me that this would be a pretty common problem (affecting everyone running nfs) and that suse would make the proper corrections.

BrianK · 08-23-2004, 01:45 PM

I never managed to get it working & didn't look into scripting anything. My uber-lazy fix was to allow all users to mount that nfs share so if they rebooted the machine, they would be able to remount without root priviledges.