LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (http://www.linuxquestions.org/questions/linux-software-2/)
-   -   problems with smbfs mount-point in /etc/fstab - "mount -a" works, but not at boottime (http://www.linuxquestions.org/questions/linux-software-2/problems-with-smbfs-mount-point-in-etc-fstab-mount-a-works-but-not-at-boottime-376193/)

MarkSide 10-23-2005 08:47 PM

problems with smbfs mount-point in /etc/fstab - "mount -a" works, but not at boottime
 
Hi there...

I'm having problems getting a Windows share to be auto-mounted at boot-time of my Linux system (coLinux 0.6.1/Debian unstable).

The line in my /etc/fstab is as follows:

Code:

//192.168.0.105/MP3 /var/www/webdav/mp3 smbfs credentials=/root/.smbcredentials 0 0
Running "mount -a" as root mounts the share just fine, but when I reboot the machine that mount-point is just an empty dir, and the //192.168.0.105/MP3 share doesn't show up in the list displayed by "mount". I've grepped through the logfiles in /var/log for anything matching the case-insensitive text "mp3" without showing up anything - the only reference I can find to that share is in the /var/log/samba/log.smbmount file, and that's just for the times when I've manually mounted the share.

Anyone have any ideas as to what might be going on, or where I could look for more hints as to what's happening here??

Thanks in advance,

--- Mark ---

xgreen 10-25-2005 06:01 AM

does the network connection established before the mounting?

MarkSide 10-25-2005 08:06 PM

Not sure - how would I check for this? I'm afraid my Linux skills are a bit rusty at the moment...

The (apparently) relevant portion of my boot-time syslog looks like the following:
Code:

...
Oct 25 20:52:50 bobafett kernel: cobd0 size: 2097152 kb
Oct 25 20:52:50 bobafett kernel: cobd1 size: 65536 kb
Oct 25 20:52:50 bobafett kernel: cobd: loaded (max 32 devices)
Oct 25 20:52:50 bobafett kernel: cobd1 size: 65536 kb
Oct 25 20:52:50 bobafett kernel: cobd: loaded (max 32 devices)
Oct 25 20:52:50 bobafett kernel: conet: loaded (max 16 devices)
Oct 25 20:52:50 bobafett kernel: conet0: initialized
Oct 25 20:52:50 bobafett kernel: Initializing Cryptographic API
Oct 25 20:52:50 bobafett kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Oct 25 20:52:50 bobafett kernel: IP Protocols: ICMP, UDP, TCP
Oct 25 20:52:50 bobafett kernel: IP: routing cache hash table of 512 buckets, 4$
Oct 25 20:52:50 bobafett kernel: TCP: Hash tables configured (established 4096 $
Oct 25 20:52:50 bobafett kernel: NET4: Unix domain sockets 1.0/SMP for Linux NE$
Oct 25 20:52:50 bobafett kernel: kjournald starting.  Commit interval 5 seconds
Oct 25 20:52:50 bobafett kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on cobd(117$
Oct 25 20:52:50 bobafett kernel: EXT3-fs: mounted filesystem with ordered data $
Oct 25 20:52:50 bobafett kernel: VFS: Mounted root (ext3 filesystem).
Oct 25 20:52:50 bobafett kernel: Freeing unused kernel memory: 52k freed
Oct 25 20:52:50 bobafett kernel: Adding Swap: 65528k swap-space (priority -1)
Oct 25 20:52:50 bobafett kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on cobd(117$
Oct 25 20:52:50 bobafett mysqld_safe[426]: started
...

From the above, since the "conet" and "NET4" messages are showing up prior to the "EXT3 FS" / "Adding Swap" messages (by some fraction of a second), would it be safe to assume that, yes, my network stuff is coming up prior to the /etc/fstab file being processed? ...or is there any easier way to figure this out?

Now, my understanding is that the /etc/fstab file is being processed by the running of the command "mount -a" during boot. Is there any way to get this command to log any output as to the results of its execution?

Thanks,

--- Mark ---

MarkSide 10-26-2005 09:28 AM

Okay, your post prompted me to figure out how the linux boot-process works. After looking through all the inet.d scripts, I tried manually-invoking all the mount-oriented ones; none of mountall.sh, mountnfs.sh, or mountvirtfs.sh mounted my type=smbfs shares. I started trying to figure out why this was the case, but then got really lazy and since I knew that a post-boot execution of "mount -a" worked just fine, I simply created a new init-script that runs at the end of runlevel-S and just executes the command "mount -a".

May not be the most elegant solution to my problem, but it seems to have done the trick.

--- Mark ---

qzu 11-20-2005 03:30 PM

make sure that the line you have added in /etc/fstab is AFTER the line which mounts /var. Hmm... I mean, put your entry at the end of the fstab file. Hope this helps.


All times are GMT -5. The time now is 07:16 AM.