LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices



Reply
 
Search this Thread
Old 06-29-2004, 03:51 PM   #1
BrianK
Senior Member
 
Registered: Mar 2002
Location: Los Angeles, CA
Distribution: Debian, Ubuntu
Posts: 1,334

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


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?

Last edited by BrianK; 06-29-2004 at 03:54 PM.
 
Old 06-29-2004, 04:00 PM   #2
Tinkster
Moderator
 
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 23,005
Blog Entries: 11

Rep: Reputation: 903Reputation: 903Reputation: 903Reputation: 903Reputation: 903Reputation: 903Reputation: 903Reputation: 903
man fstab

Just add auto to the rw, bit




Cheers,
Tink

Last edited by Tinkster; 06-29-2004 at 04:01 PM.
 
Old 06-29-2004, 04:11 PM   #3
BrianK
Senior Member
 
Registered: Mar 2002
Location: Los Angeles, CA
Distribution: Debian, Ubuntu
Posts: 1,334

Original Poster
Rep: Reputation: 51
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.
 
Old 06-29-2004, 04:39 PM   #4
J.W.
LQ Veteran
 
Registered: Mar 2003
Location: Milwaukee, WI
Distribution: Mint
Posts: 6,642

Rep: Reputation: 69
Re: Suse 9.1: Not all entries in fstab are mounted at boot. why?

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.
 
Old 06-29-2004, 05:22 PM   #5
BrianK
Senior Member
 
Registered: Mar 2002
Location: Los Angeles, CA
Distribution: Debian, Ubuntu
Posts: 1,334

Original Poster
Rep: Reputation: 51
Re: Re: Suse 9.1: Not all entries in fstab are mounted at boot. why?

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?
 
Old 06-30-2004, 02:44 AM   #6
J.W.
LQ Veteran
 
Registered: Mar 2003
Location: Milwaukee, WI
Distribution: Mint
Posts: 6,642

Rep: Reputation: 69
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.
 
Old 07-25-2004, 03:41 PM   #7
ggreen
LQ Newbie
 
Registered: Jul 2004
Posts: 1

Rep: Reputation: 0
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
 
Old 07-26-2004, 01:47 PM   #8
BrianK
Senior Member
 
Registered: Mar 2002
Location: Los Angeles, CA
Distribution: Debian, Ubuntu
Posts: 1,334

Original Poster
Rep: Reputation: 51
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.
 
Old 08-19-2004, 07:22 PM   #9
struthers
LQ Newbie
 
Registered: Aug 2004
Posts: 1

Rep: Reputation: 0
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.
 
Old 08-23-2004, 02:45 PM   #10
BrianK
Senior Member
 
Registered: Mar 2002
Location: Los Angeles, CA
Distribution: Debian, Ubuntu
Posts: 1,334

Original Poster
Rep: Reputation: 51
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Remote NFS export (via fstab) isn't mounted at boot tisource Linux - General 3 10-30-2005 05:57 PM
/etc/fstab -- adding entries every boot Kamikazee Linux - Newbie 3 07-14-2005 05:35 AM
Dynamic Entries in fstab? bigoli MEPIS 1 06-02-2005 03:18 PM
Immortal fstab entries tmoorman Mandriva 1 02-05-2005 03:52 AM
Entries in /etc/fstab kamransoomro84 Linux - General 6 05-05-2004 10:32 AM


All times are GMT -5. The time now is 02:33 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration