[opensuse] Howto start cifs daemon for automounting shares?
Hi, I've got samba running on an OpenSuse 12.1. I can manually mount external shares. Then I entered apparently suitable lines in /etc/samba/cifstab but the shares aren't automatically mounted on boot time. This is ignored. Nothing gets mounted and there is no error in the smb.log. I found a refernce that I need to start the cifs service in Yast-->Runlevel. I set it to runlevel 3+5 and tried to start it imediatly in yast. When I try this I get the error : /etc/init.d/cifs start returned 6 (program not configured) Can someon point me in the right direction, please? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Feb 10, 2012 at 12:00:22PM +0100, Andreas wrote:
Then I entered apparently suitable lines in /etc/samba/cifstab but the shares aren't automatically mounted on boot time.
How does your /etc/samba/cifstab look like?
6 (program not configured) as defined in /etc/init.d/skeleton we return in the case when /etc/fstab has no cifs mount point configured and if there is no /etc/samba/cifstab file. Please check via bash -x /etc/init.d/cifs Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Am 10.02.2012 12:14, schrieb Lars Müller:
//192.168.0.210/e /mnt/backup_extern cifs username=x,password=y //192.168.0.211/updates /mnt/updates cifs username=x,password=y I tried rccifs status and got "running" though yast shows it as not running. And it listed the 2 shares I mounted manually. rccifs stop unmounts both shares but rccifs start mounts only the first though the lines look the same. Am I missing some detail? Why is the 2nd line ignored?
I did and it dumped some stuff that doesn't give me a clue. Is there a special part to look at? Btw. there are a lot of errors in /var/log/messages coming roughly every minute like: Feb 10 12:25:01 mybox kernel: [104270.254182] CIFS VFS: Received no data, expecting 4 Andreas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Feb 10, 2012 at 12:52:51PM +0100, Andreas wrote:
I have no clue. Please check /var/log/messages (syslog) if you find there any complain. As you're usinf IP addresses and no names it can't be an DNS issue.
This smells more and more like a bug. :/
You are using systemd? If ls -l /sbin/init shows ../bin/systemd, then the answer is yes. Can you please give the following commands a try: systemctl status cifs.service If this reports an active service please call next: systemctl stop cifs.service and then: systemctl start cifs.service If inactive (dead) was reported as on the status request call the latter two commands the other way around. In between follow all the time /var/log/messages via tail -f and please report the lines you get printed on screen via bugzilla. Then quote the bug ID here as cross reference.
This might be caused by your cifs server. Is this a recent recent Linux kernel based system too? Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Am 10.02.2012 17:21, schrieb Lars Müller:
As you're usinf IP addresses and no names it can't be an DNS issue.
and the manual call of mount ... works with those values.
no. I switched to sysinit. systemd of Suse 12.1 has issues with softraids. I've got a raid1 pair and there are errors when booting with systemd. It's not the system partition so the boot process stops and I get to a root console. As long as I don't mount the raid on boot, the system gets up and I can mount the raid manually. So systemd is a no go. That was a known issue at least as V 12.1 was released.
its the latest opensuse 12.1 kernel that came via online-update. I found posts with google that stated this too was a known problem that should go away with a 3.2 kernel. It's a 64bit 3.1.9-1.4-desktop kernel. Andreas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Feb 10, 2012 at 08:03:56PM +0100, Andreas wrote:
Then please do the same with sysvinit. service cifs <command> While command is status, stop, or start as suggested for the systemctl case before. Please attach the output step by step to a bug report.
Please quote the URLs for reference.
It's a 64bit 3.1.9-1.4-desktop kernel.
You might give kernel-default a try. That's the one I'm used while my tests. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Am 10.02.2012 21:49, schrieb Lars Müller:
1) I added 2 lines in /etc/fstab and commented out the 2 i /etc/samba/cifstab After reboot the 2 shares got mounted. service cifs stop Umount CIFS File Systems ... done service cifs start Mount CIFS File Systems from /etc/fstab ... done service cifs status Checking for mounted CIFS File Systems both shares are mounted 2) I commented out the 2 lines in /etc/fstab and activated the 2 in cifstab service cifs stop and service cifs start look the same but service cifs status shows only the 1st share mounted 3) I switched back to /etc/fstab and both shares get mounted again.
You might give kernel-default a try. That's the one I'm used while my tests.
I'm a wee bit reluctant to play with the kernel on that machine as I had a kernel panic when the kernel got updated last sunday, though it was another machine and opensuse 11.4. I just don't like the idea of having to explain why there is another system failiour in such a short time. I'll check on the backup sytem -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Feb 10, 2012 at 12:00:22PM +0100, Andreas wrote:
Then I entered apparently suitable lines in /etc/samba/cifstab but the shares aren't automatically mounted on boot time.
How does your /etc/samba/cifstab look like?
6 (program not configured) as defined in /etc/init.d/skeleton we return in the case when /etc/fstab has no cifs mount point configured and if there is no /etc/samba/cifstab file. Please check via bash -x /etc/init.d/cifs Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Am 10.02.2012 12:14, schrieb Lars Müller:
//192.168.0.210/e /mnt/backup_extern cifs username=x,password=y //192.168.0.211/updates /mnt/updates cifs username=x,password=y I tried rccifs status and got "running" though yast shows it as not running. And it listed the 2 shares I mounted manually. rccifs stop unmounts both shares but rccifs start mounts only the first though the lines look the same. Am I missing some detail? Why is the 2nd line ignored?
I did and it dumped some stuff that doesn't give me a clue. Is there a special part to look at? Btw. there are a lot of errors in /var/log/messages coming roughly every minute like: Feb 10 12:25:01 mybox kernel: [104270.254182] CIFS VFS: Received no data, expecting 4 Andreas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Feb 10, 2012 at 12:52:51PM +0100, Andreas wrote:
I have no clue. Please check /var/log/messages (syslog) if you find there any complain. As you're usinf IP addresses and no names it can't be an DNS issue.
This smells more and more like a bug. :/
You are using systemd? If ls -l /sbin/init shows ../bin/systemd, then the answer is yes. Can you please give the following commands a try: systemctl status cifs.service If this reports an active service please call next: systemctl stop cifs.service and then: systemctl start cifs.service If inactive (dead) was reported as on the status request call the latter two commands the other way around. In between follow all the time /var/log/messages via tail -f and please report the lines you get printed on screen via bugzilla. Then quote the bug ID here as cross reference.
This might be caused by your cifs server. Is this a recent recent Linux kernel based system too? Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Am 10.02.2012 17:21, schrieb Lars Müller:
As you're usinf IP addresses and no names it can't be an DNS issue.
and the manual call of mount ... works with those values.
no. I switched to sysinit. systemd of Suse 12.1 has issues with softraids. I've got a raid1 pair and there are errors when booting with systemd. It's not the system partition so the boot process stops and I get to a root console. As long as I don't mount the raid on boot, the system gets up and I can mount the raid manually. So systemd is a no go. That was a known issue at least as V 12.1 was released.
its the latest opensuse 12.1 kernel that came via online-update. I found posts with google that stated this too was a known problem that should go away with a 3.2 kernel. It's a 64bit 3.1.9-1.4-desktop kernel. Andreas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Feb 10, 2012 at 08:03:56PM +0100, Andreas wrote:
Then please do the same with sysvinit. service cifs <command> While command is status, stop, or start as suggested for the systemctl case before. Please attach the output step by step to a bug report.
Please quote the URLs for reference.
It's a 64bit 3.1.9-1.4-desktop kernel.
You might give kernel-default a try. That's the one I'm used while my tests. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Am 10.02.2012 21:49, schrieb Lars Müller:
1) I added 2 lines in /etc/fstab and commented out the 2 i /etc/samba/cifstab After reboot the 2 shares got mounted. service cifs stop Umount CIFS File Systems ... done service cifs start Mount CIFS File Systems from /etc/fstab ... done service cifs status Checking for mounted CIFS File Systems both shares are mounted 2) I commented out the 2 lines in /etc/fstab and activated the 2 in cifstab service cifs stop and service cifs start look the same but service cifs status shows only the 1st share mounted 3) I switched back to /etc/fstab and both shares get mounted again.
You might give kernel-default a try. That's the one I'm used while my tests.
I'm a wee bit reluctant to play with the kernel on that machine as I had a kernel panic when the kernel got updated last sunday, though it was another machine and opensuse 11.4. I just don't like the idea of having to explain why there is another system failiour in such a short time. I'll check on the backup sytem -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Andreas -
Lars Müller