User unable to umount samba share

Here is the lines in my /etc/fstab related to samba shares.
# Some Windows/SAMBA shares
//BAO-QNAP500GB/USB\040Disk\0401 /mnt/eBooks smbfs workgroup=BAO-HOME,username=xxxxxx,ip=192.168.2.4,password=xxxxxx,noauto,noatime,user,rw 0 0
I am able to mount samba share as a user (not root) after
chmod u+s /usr/bin/smbmnt
chmod u+s /usr/bin/smbumount
by
mount /mnt/eBooks
However, I am unable to umount as a user:
[ning@HP-m8100y ~]$ umount /mnt/eBooks
umount: /mnt/eBooks mount disagrees with the fstab
On the other hand, this could work:
smbumount /mnt/eBooks
Can somone tell me what I did wrong?

Looks like its something to do with fstab though I don't know what never having mounted shares though fstab myself. I would try removing the fstab entry and just using smbmount to mount shares, thats the way I've always done it and never have problems with mounting/unmounting.
smbmount //IP Address/source folder /destination folder

Similar Messages

How to allow users to mount a Samba shares on a WXP

Through lots of reading I've managed to get an understanding of how to mount SMB shares at bootup by placing the proper edits in /etc/fstab. While having the shares of the server, running Contribs.org SME Server 6.01 (recently known as Mitel SME Server) and acting as a samba server, being mounted at startup is perfect since the server is always on. This is not the best idea for the XP workstation since it isn't always on. Here is a copy of my present fstab file with x's replacing the passwords.
fstab [B---] 0 L:[ 1+19 20/ 21] *(1085/1086b)= . 10 0x0A
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /proc proc defaults 0 0
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
tmpfs /tmp tmpfs defaults 0 0
sysfs /sys sysfs defaults 0 0
usbdevfs /proc/bus/usb usbdevfs defaults 0 0
/dev/cdroms/cdrom0 /mnt/cd iso9660 ro,user,noauto,unhide 0 0
/dev/cdroms/cdrom0 /mnt/dvd udf ro,user,noauto,unhide 0 0
/dev/floppy/0 /mnt/fl vfat user,noauto,unhide 0 0
//192.168.2.2/stuff /mnt/silicon2 smbfs username=kingnubian,password=xxxxxxx,user
//192.168.2.105/e-smith /mnt/silicon1 smbfs username=kingnubian,password=xxxxxxx,users,noauto
/dev/discs/disc0/part5 swap swap defaults 0 0
/dev/discs/disc0/part1 / xfs defaults 0 1
I would like users with an account on the Linux box to mount the remote share on the XP box without needing to SU and consequently need the root password. When trying now to mount "e-smith" (The share on the XP box) as a user using "mount /mnt/silicon1" I get a message about needing to be SU.

To allow users to mount smb shares you need to make smbmnt suid:
# chmod +s /usr/bin/smbmnt
Note however that the user needs to own the directory used as mountpoint. So I don't know how to make 'mount /mnt/silicon1' in your setup work for all users.
For the users to be able to unmount the smb shares as well you need:
# chmod +s /usr/bin/smbumount
Now users can do 'smbmount //server/share mountpoint -o username=whatever' or simply 'mount mountpoint' if the details are specified in fstab. To unmount root can do 'umount mountpoint' or users can do 'smbumount mountpoint'.
Don't confuse smbmount with smbmnt - the first is the command you use to mount shares manually, the second is the one that should be suid and is used both by smbmount and by mount -t smb.
Hope this helps.
-bogomipz

Unable to access samba share.

I'm setting up a ubuntu file server with samba shares and security = user.
These shares are able to be accessed and work correctly for both linux and windows clients. When I attempt to connect to the shares in OSX I get the usual username/password dialog box, however it doesn't accept the correct credentials.
I've googled for help for a few hours now, but cannot find anything that helps. I'm guessing its a security setting somewhere in OSX, but I'm not able to find out what.
Any ideas?

turns out that I was connecting to it incorrectly.
correct method is smb:\\workgroup;user@server\share

Unable to mount samba share file for xbox 360

I want to be able to stream music from a directory in my arch linux computer (xfce4) to my xbox using samba on a local network using ethernet cables and a router not connected to the internet. I've been able to get samba to startup and I see the folder "share" in my network tab in thunar, but I am currentlly unable to mount that folder. I haven't been able to get the xbox to recognize my arch computer or visa versa.
Here is the configuration I am running as of now:
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = XBOX
# server string is the equivalent of the NT Description field
server string = "Samba Server"
# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = user
[share]
comment = music for xbox
path = /home/ricky/Music
browsable = yes
guest ok = yes
read only = yes
create mask = 0777
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
I did a chmod -r 777 on the ~/Music directory already and I still haven't been able to mount it. I have read in the wiki that creating a /mnt/xboxshare directory, for example, would actually mount the share directory and allow the xbox to share. However, I would rather just use the directory I specified instead of creating another directory. Has anyone else experienced this problem or have any advice for me?
Here is some additional information:
I do have to input a password when I issue this command
$ smbclient -L \\RG_ARCH
Enter password:
Domain=[XBOX] OS=[Unix] Server=[Samba 3.6.8]
Sharename Type Comment
share Disk music for xbox
IPC$ IPC IPC Service ("Samba Server")
rg Disk Home Directories
Domain=[XBOX] OS=[Unix] Server=[Samba 3.6.8]
Server Comment
RG_ARCH Samba Server
Workgroup Master
XBOX RG_ARCH

I was wondering whether it had anything to do with the network I was using. The router I am using can't access the internet and I am using the basic 192.168.1.X setup with 255.255.255.0 as the mask.
My computer has an ip of 192.168.1.2 and the xbox has an ip of 192.168.1.3. However, I am still unable to ping the xbox or even see it show up in the network. I did notice that whenever I am using another router that is connected to the internet, I can see other windows based computers in the network tab in thunar under "windows network"
Also, I do have a username and password associated with the samba setup.. so I assume maybe that has something do with it. I checked the permissions of the share folder and it was root:root with read and write permissions. I know samba is working fairly well.. but for whatever reason I can't get the xbox to connect even while it is on the same local network.

[SOLVED] Suddenly unable to mount samba share using cifs

I have a home server running ArchLinux, hosting an SMB share. My client box is also ArchLinux, both are up to date, running Linux-ck 3.9.2-2-ck. Prior to rebooting both machines around twenty minutes ago, the share mounted fine for months.
Here is the extent of the "verbosity" I receive from mount:
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Here is my fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
# UUID=71066ae2-40ec-4125-9db7-d04b6a04f712
UUID=71066ae2-40ec-4125-9db7-d04b6a04f712 / ext4 rw,relatime,data=ordered 0 2
# UUID=172faa6a-9cca-4d9e-a0b9-a5da3ea81922
UUID=172faa6a-9cca-4d9e-a0b9-a5da3ea81922 /boot ext2 rw,relatime 0 2
# UUID=65023815-33fc-4ebd-b245-65683201fbcf
UUID=65023815-33fc-4ebd-b245-65683201fbcf /home ext4 rw,relatime,data=ordered 0 2
UUID=1a23d461-fa2b-4ea4-8e58-e7efba3f3bed /media/Storage ext3 rw 0 2
//ARRAY/Array /media/Array cifs credentials=/home/xaero/.smbpasswd,iocharset=utf8,uid=1000,gid=1000,nounix,sec=ntlm 0 0
I have tried any number of different options on that final line defining this share now:
I have tried //array/array (which is what it was originally) and //ARRAY/Array (which is case-sensitive) as well as any combination of using my credentials file (which used to work) or user=,pass= as well changing my credentials file to use quotation marks around my password as it has special characters. I've also read of using sec=ntlm fixing mount issues, but in my case it did not. I'm kind of scratching my head here as passing --verbose to mount yields zero additional information... the uid and gid entries were necessary in the past to mount this share, however I have tried both with and without them, to no avail.
I rely on SMB in lieu of sshfs as there isn't a stable sshfs implementation for Windows users, which there are some on my network; I also find for whatever reason SMB happens to be faster.
Last edited by Xaero252 (2013-05-19 21:45:30)

I'm not exactly sure what fixed this... I looked at the configuration file to make sure I hadn't missed it being updated, and it was in the new format; everything setup correctly (I remember having to edit it not long ago to fix something, probably for the update which you mentioned) I reverted my fstab back to the way it was before (making backups is good) and restarted the smbd on the server numerous times... at some point it just started working again. I wish I had a more concrete answer for documentation sake, but I was literally just rebooting/restarting services in desperation with little to no config hacking between and suddenly things clicked. I'm also no longer running the sec=ntlm option..
Thanks for reminding me to check my config though, when I updated I had forgotten to enable user restriction (guest was enabled, and certain directories weren't user-specific)

Leopard 10.5.5 and Linux Samba shares not connecting

I have seen this talked about many times, but I have not found the answer. And my situation is always slightly different from others...so here it is!
when I try to connect to our samba share, here are my steps...
Go
Connect to Server
smb://10.xx.xx.xx
Connect
here's where the problem is: the enter username and password pops up, and asks me to put them in...there is no user/password on our samba shares, and I cannot connect via guest either.
in Tiger, there was a work around through terminal to connect, but that doesn't apply to Leopard. We only have 2 Leopard machines here, all the rest are still Tiger, but we are eyeing upgrades, and would be forced to go up to Leopard since we can't buy new Macs with Tiger anymore.

best answer...get rid of Linux share, replaced it with an OS X server, no problems at all...

Non-root user cannot umount a SAMBA share if there is "SPACE" with the

I already post this to the bugs report http://bugs.archlinux.org/task/9672, but I would like to see if someone in the forum can help.
Description:
If there are "SPACE" in the SAMBA share name. Then, a non-root user can mount that share, but cannot umount it with "umount" command. It gives "mount desagrees with the fstab" error. root can mount/umount without any problem.
Also, user can umount the share by "smbumount" without any problem.
Additional info:
* package version(s)
samba 3.0.28A-1
util-linux-ng 2.13.0.1-2
* config and/or log files etc.
/etc/fstab
Steps to reproduce:
1. Add a line in /etc/fstab as the following
//QNAP-500GB/USB\040Disk\0401 /mnt/eBooks smbfs workgroup=GROUPNAME,username=xxxxxx,ip=xxxxxxxx,password=xxxxxx,noauto,noatime,users,rw 0 0
as you can see that SAMBA share name "USB Disk 1" was replace by "USB\040Disk\0401".
2. Change UID of/usr/bin/smbmnt and /usr/bin/smbumount by
chmod u+s /usr/bin/smbmnt
chmod u+s /usr/bin/smbumount
3. Change the ownership of the mount path for this SAMBA share to a non-root user by
chown username:users /mnt/eBooks
4. mount as a non-root user (username)
mount /mnt/eBooks
5. ERROR! if umount as a non-root user; NO ERROR if umount as root.
[ning@HP-m8100y ~]$ umount /mnt/eBooks/
umount: /mnt/eBooks mount disagrees with the fstab
6. This SAMBA share can be umounted by
smbumount /mnt/eBooks

Did you try using %20 instead of a space? I know it works for URLs...worth a shot.

Not able to Start Hyper-V(2012 R2) VM when placing the VM config file on Samba Share,Its giving error:Unable to initialize the saveset

---We are trying to setup Hyper-V on Samba shares samba version 3.6 exported from Ubuntu M/c. Basically runnig the Public(share) from the Ubuntu and able to access it from Windows 2012 (create/modify everything). I used Hyper-V and placed the disks
".vhd" on this , VM succesfull created and started. However when I placed the VM config files on this (samba) shares VM created successfully but its not starting, Its giving error like Unable to initialize the saveset -- Any idea how to place the
Hyper-V VM config files samba share?

Hi Rakesh KK,
Please confirm your share meet the Serve 2012r2 Hyper-V requirement, you can refer the following KB to get more detail require conditions.
Deploy Hyper-V over SMB
http://technet.microsoft.com/en-us/library/jj134187.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Leopard unable to send folders to a samba share

We are currently experiencing a problem trying to copy a pro tools project onto one of our servers via a samba share on the server. When we try to copy/move a directory finder reports that it does not have sufficiant privalages to do so.
But when we selected individual files inside the directory tree and copied them, they all went over fine and where able to create directories on the server from the client.
I then used terminal and ls -la to view the contents of the directories and discovered there were a fair few hidden temporary files. All belong to the correct user as far as samba is concerned, but some had the "@", Extended attributes flag attatched. I am able to interrogate them using xattr which shows com.apple.<this part varies> I'm unsure completely what com. files represent, as I am generally a linux user (sorry apple! but hey we're both unixy..)
Does anyone know of a fix, or if this is a common problem? or any way I can stop osx from spuriously creating these hidden files? or am I going to havto script something.. umm.. somewhere.
Oh, the server is running Fedora Linux, and the client is an Imac running OSX Leopard.
Any information would be greatly appreciated!
Stewart
I am having difficulty finding a sollution to this problem.

do you get error -36 or error -50? there are several bugs related to that in snow leopard finder. not sure which one is affecting you. try this link first
http://support.apple.com/kb/HT4017
next, see this post. It could be a problem with split resource forks for hidden .DS_Store files if it only affects folders
http://discussions.apple.com/thread.jspa?messageID=11122044&#11122044
also see this link for yet another bug
http://db.tidbits.com/article/10772

App freeze on accessing Samba shares

Hi,
I really didn't want to have to make a topic on this, as I've searched all over the place and I'm beginning to wonder if I'm the only one with this problem (unless I've somehow missed something).
Basically I have some Samba shares set up like this in my fstab:
# Share Mounts
//<address>/share1 /home/eldersnake/Shares/share1 cifs noauto,x-systemd.automount,users,uid=eldersnake,gid=users,password= 0 0
//<address>/share2 /home/eldersnake/Shares/share2 cifs noauto,x-systemd.automount,users,uid=eldersnake,gid=users,credentials=<credentials location> 0 0
The problem is periodically, trying to access/mount these shares through let's say, Dolphin (but it happens in any file manager I try) causes the program to simply hang. It will stay there, hung and cannot be killed, even with the "kill -9" command. Only rebooting gets rid of the process.
And looking at the process list with KDE's system monitor lists the affected program status as "disk sleep". Again, it cannot be killed. I've seen this happen with my file manager, Clementine (when I tried to open up a file, therefore it opened up the file dialog and I clicked on a share mount) and even in my terminal...
Even running
sudo mount /home/eldersnake/Shares/share1
for example, nothing happens. The terminal is simply hung and never completes.
I say this happens periodically because sometimes it seems to work just fine. Then some days, it does the above consistently. I'm really unable to pin it down.
Anyway I removed the x-systemd.automount option from fstab and so far I have not been able to reproduce this problem. I'd file a bug report but I can't help but wonder if I've missed something obvious and I'm unsure how to provide evidence that it's systemd specifically causing the problem. Thanks for any help.
EDIT: I should add this occasionally also happens on a separate machine, my netbook. Again, only after adding the systemd automount line to the fstab file.
Also manually mounting the share with
sudo mount -t cifs <share> <directory>
always works fine. It's simply when using the fstab entry combined with systemd automount.
EDIT: Took systemd-automount out of the title as I am not sure its the cause anymore.
Last edited by ElderSnake (2012-11-24 00:02:24)

Okay, still happening. Often I reboot and everything works fine but sometime later, can be 10 mins...could be 10 hours, this problem re-emerges.
I did however manage to catch this in dmesg
[ 4448.046038] kernel BUG at fs/dcache.c:2138!
[ 4448.046041] invalid opcode: 0000 [#1] PREEMPT SMP
[ 4448.046046] Modules linked in: fuse msr des_generic ecb md4 md5 hmac nls_utf8 cifs fscache usb_storage uas joydev hid_generic snd_usb_audio snd_usbmidi_lib snd_rawmidi usbhid snd_seq_device hid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer nvidia(PO) snd r8169 soundcore iTCO_wdt psmouse serio_raw acpi_cpufreq mperf coretemp mii evdev microcode firewire_ohci firewire_core crc_itu_t gpio_ich intel_agp i2c_i801 iTCO_vendor_support intel_gtt i2c_core lpc_ich processor pcspkr button vboxdrv(O) ext4 crc16 jbd2 mbcache sd_mod sr_mod cdrom ata_generic uhci_hcd pata_acpi pata_jmicron ata_piix libata scsi_mod ehci_hcd usbcore usb_common
[ 4448.046115] CPU 1
[ 4448.046120] Pid: 3062, comm: pool Tainted: P O 3.6.6-1-ARCH #1 Gigabyte Technology Co., Ltd. EP45-DS3/EP45-DS3
[ 4448.046123] RIP: 0010:[<ffffffff81195843>] [<ffffffff81195843>] __d_rehash+0x83/0xf0
[ 4448.046133] RSP: 0018:ffff88009c627b88 EFLAGS: 00010286
[ 4448.046136] RAX: 00000000000176bd RBX: ffff880040ff7ddc RCX: 0000000000000013
[ 4448.046138] RDX: ffffc90000002000 RSI: ffffc900000bd5e8 RDI: ffff880040ff7d80
[ 4448.046141] RBP: ffff88009c627ba8 R08: 0000000000010000 R09: ffff88009c627fd8
[ 4448.046143] R10: ffff8800a751a4a0 R11: 0000000000000000 R12: ffff880040ff7d80
[ 4448.046146] R13: 0000000000000000 R14: 00000000fffffffe R15: 000000000000010f
[ 4448.046149] FS: 00007fb76933c700(0000) GS:ffff8800bfc80000(0000) knlGS:0000000000000000
[ 4448.046152] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 4448.046154] CR2: 00007fb74c0010b8 CR3: 000000003cb77000 CR4: 00000000000007e0
[ 4448.046157] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 4448.046160] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 4448.046163] Process pool (pid: 3062, threadinfo ffff88009c626000, task ffff8800638fa850)
[ 4448.046164] Stack:
[ 4448.046166] ffff8800a4af7e00 0000000000000000 ffff880040ff7ddc ffff880040ff7d80
[ 4448.046172] ffff88009c627bb8 ffffffff811958e6 ffff88009c627bd8 ffffffff8119591c
[ 4448.046176] 0000000000000000 ffff8800a4914480 ffff88009c627c38 ffffffffa0e6c973
[ 4448.046181] Call Trace:
[ 4448.046187] [<ffffffff811958e6>] _d_rehash+0x36/0x40
[ 4448.046191] [<ffffffff8119591c>] d_rehash+0x2c/0x40
[ 4448.046201] [<ffffffffa0e6c973>] cifs_lookup+0x263/0x360 [cifs]
[ 4448.046210] [<ffffffffa0e6cab2>] cifs_atomic_open+0x42/0x230 [cifs]
[ 4448.046214] [<ffffffff81197fa5>] ? d_lookup+0x35/0x60
[ 4448.046218] [<ffffffff8118eadf>] do_last+0x56f/0xea0
[ 4448.046223] [<ffffffff8118f4ca>] path_openat+0xba/0x520
[ 4448.046227] [<ffffffff8118fc91>] do_filp_open+0x41/0xa0
[ 4448.046232] [<ffffffff8119c766>] ? alloc_fd+0xd6/0x120
[ 4448.046237] [<ffffffff8117e9d6>] do_sys_open+0xf6/0x1e0
[ 4448.046241] [<ffffffff8117eae1>] sys_open+0x21/0x30
[ 4448.046246] [<ffffffff81499f2d>] system_call_fastpath+0x1a/0x1f
[ 4448.046248] Code: 48 89 16 0f ba 36 00 65 48 8b 04 25 f0 c6 00 00 83 a8 44 e0 ff ff 01 48 8b 80 38 e0 ff ff a8 08 75 0b 48 83 c4 10 5b 41 5c 5d c3 <0f> 0b e8 96 c2 2f 00 eb ee 49 89 c4 48 89 c3 41 83 ac 24 44 e0
[ 4448.046295] RIP [<ffffffff81195843>] __d_rehash+0x83/0xf0
[ 4448.046300] RSP <ffff88009c627b88>
[ 4448.046322] ---[ end trace 822cd52e99a52b51 ]---
[ 4448.046327] note: pool[3062] exited with preempt_count 1
[ 4448.055386] ------------[ cut here ]------------
[ 4448.055393] kernel BUG at fs/dcache.c:2138!
[ 4448.055396] invalid opcode: 0000 [#2] PREEMPT SMP
[ 4448.055401] Modules linked in: fuse msr des_generic ecb md4 md5 hmac nls_utf8 cifs fscache usb_storage uas joydev hid_generic snd_usb_audio snd_usbmidi_lib snd_rawmidi usbhid snd_seq_device hid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer nvidia(PO) snd r8169 soundcore iTCO_wdt psmouse serio_raw acpi_cpufreq mperf coretemp mii evdev microcode firewire_ohci firewire_core crc_itu_t gpio_ich intel_agp i2c_i801 iTCO_vendor_support intel_gtt i2c_core lpc_ich processor pcspkr button vboxdrv(O) ext4 crc16 jbd2 mbcache sd_mod sr_mod cdrom ata_generic uhci_hcd pata_acpi pata_jmicron ata_piix libata scsi_mod ehci_hcd usbcore usb_common
[ 4448.055471] CPU 1
[ 4448.055476] Pid: 3063, comm: pool Tainted: P D O 3.6.6-1-ARCH #1 Gigabyte Technology Co., Ltd. EP45-DS3/EP45-DS3
[ 4448.055479] RIP: 0010:[<ffffffff81195843>] [<ffffffff81195843>] __d_rehash+0x83/0xf0
[ 4448.055488] RSP: 0000:ffff88003a059b88 EFLAGS: 00010286
[ 4448.055491] RAX: 000000000004ad5b RBX: ffff880040ff7a1c RCX: 0000000000000013
[ 4448.055494] RDX: ffffc90000002000 RSI: ffffc90000258ad8 RDI: ffff880040ff79c0
[ 4448.055496] RBP: ffff88003a059ba8 R08: 000000000001b2c0 R09: ffff8800bfc9b2c0
[ 4448.055499] R10: ffff8800a751ae60 R11: 0000000000000000 R12: ffff880040ff79c0
[ 4448.055501] R13: 0000000000000000 R14: 00000000fffffffe R15: 0000000000000110
[ 4448.055505] FS: 00007fb768b3b700(0000) GS:ffff8800bfc80000(0000) knlGS:0000000000000000
[ 4448.055507] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 4448.055510] CR2: 00007f8507000000 CR3: 000000003cb77000 CR4: 00000000000007e0
[ 4448.055513] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 4448.055515] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 4448.055518] Process pool (pid: 3063, threadinfo ffff88003a058000, task ffff8800638fc890)
[ 4448.055520] Stack:
[ 4448.055522] ffff8800ae280200 0000000000000000 ffff880040ff7a1c ffff880040ff79c0
[ 4448.055527] ffff88003a059bb8 ffffffff811958e6 ffff88003a059bd8 ffffffff8119591c
[ 4448.055531] 0000000000000000 ffff8800956d5cc0 ffff88003a059c38 ffffffffa0e6c973
[ 4448.055536] Call Trace:
[ 4448.055542] [<ffffffff811958e6>] _d_rehash+0x36/0x40
[ 4448.055546] [<ffffffff8119591c>] d_rehash+0x2c/0x40
[ 4448.055556] [<ffffffffa0e6c973>] cifs_lookup+0x263/0x360 [cifs]
[ 4448.055564] [<ffffffffa0e6cab2>] cifs_atomic_open+0x42/0x230 [cifs]
[ 4448.055568] [<ffffffff81197fa5>] ? d_lookup+0x35/0x60
[ 4448.055572] [<ffffffff8118eadf>] do_last+0x56f/0xea0
[ 4448.055577] [<ffffffff8118f4ca>] path_openat+0xba/0x520
[ 4448.055582] [<ffffffff8118fc91>] do_filp_open+0x41/0xa0
[ 4448.055586] [<ffffffff8119c766>] ? alloc_fd+0xd6/0x120
[ 4448.055591] [<ffffffff8117e9d6>] do_sys_open+0xf6/0x1e0
[ 4448.055595] [<ffffffff8117eae1>] sys_open+0x21/0x30
[ 4448.055600] [<ffffffff81499f2d>] system_call_fastpath+0x1a/0x1f
[ 4448.055602] Code: 48 89 16 0f ba 36 00 65 48 8b 04 25 f0 c6 00 00 83 a8 44 e0 ff ff 01 48 8b 80 38 e0 ff ff a8 08 75 0b 48 83 c4 10 5b 41 5c 5d c3 <0f> 0b e8 96 c2 2f 00 eb ee 49 89 c4 48 89 c3 41 83 ac 24 44 e0
[ 4448.055649] RIP [<ffffffff81195843>] __d_rehash+0x83/0xf0
[ 4448.055653] RSP <ffff88003a059b88>
[ 4448.055666] ---[ end trace 822cd52e99a52b52 ]---
[ 4448.055670] note: pool[3063] exited with preempt_count 1
Not sure what to make of it though other than it's something CIFS related, but whether CIFS itself is the problem I'm unsure. I just installed the samba daemon as suggested above though and will see how we go.
EDIT: The pid it's referring to in the stacktrace is a process which I noticed appears as a zombie after the problem occurs. The process is "gvfs-udisks2-vo".
Last edited by ElderSnake (2012-11-23 23:41:44)

Samba share shows up only after I restart samba

I've been setting up a laptop with Arch to use at work and home. The problem is I can not see my samba share until I restart the samba service. The server is available though. I can connect with \\IPADDRESS\SHARE. It's just not listed under Network Places or smbtree.
I have samba under DAEMONS in rc.conf and I've tried starting it in rc.local too. But even if I leave it out of those and start samba manually, I have to restart samba before the share will show up on any client.
The clients are Arch, Windows, and Ubuntu and the share is not available any of them. And the problem happens when I'm at work or at home. I've been googling, but I can't find much about a share being available but not being listed.
My /etc/samba/smb.conf:
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = MYWORKGOUP
# server string is the equivalent of the NT Description field
server string = Work Files
# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = user
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
hosts allow = 192.168.0. 192.168.1. 127.
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = yes
# you may wish to override the location of the printcap file
; printcap name = /etc/printcap
# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat
# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
; printing = cups
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# Put a capping on the size of the log files (in Kb).
max log size = 50
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
; realm = MY_REALM
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
; passdb backend = tdbsam
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/local/samba/lib/smb.conf.%m
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
dns proxy = no
# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
# Allow Symlinks (Needed this option after 3.4.6 due to security issues)
unix extensions = no
#============================ Share Definitions ==============================
;[homes]
; comment = Home Directories
; browseable = no
; writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
wins support = no
;[printers]
; comment = All Printers
; path = /var/spool/samba
; browseable = no
# Set public = yes to allow user 'guest account' to print
; guest ok = no
; writable = no
; printable = yes
# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = no
; printable = no
; write list = @staff
# Other examples.
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
[mike]
comment = Work Files
path = /home/MYUSER/.samba_share
valid users = MYUSER
available = yes
browsable = yes
public = yes
writable = yes
# Needed this option after 3.4.6 due to security issues
wide links = yes

I removed the . (and moved the directory to match) but I still have the same issue.
Here's the smbd.log after a rebooting and then restarting samba:
[2010/05/04 07:25:41.262266, 0] smbd/server.c:500(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address already in use
[2010/05/04 07:25:41.266578, 0] smbd/server.c:500(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address already in use
[2010/05/04 07:26:01.041577, 1] smbd/server.c:267(remove_child_pid)
Scheduled cleanup of brl and lock database after unclean shutdown
[2010/05/04 07:26:21.051370, 1] smbd/server.c:240(cleanup_timeout_fn)
Cleaning up brl and lock database after unclean shutdown
[2010/05/04 07:26:45.716653, 1] smbd/server.c:267(remove_child_pid)
Scheduled cleanup of brl and lock database after unclean shutdown
[2010/05/04 07:36:46.016675, 0] smbd/server.c:500(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address already in use
[2010/05/04 07:36:46.017386, 0] smbd/server.c:500(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address already in use
And log.nmbd:
[2010/05/04 07:25:41, 0] nmbd/nmbd.c:857(main)
nmbd version 3.5.2 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2010/05/04 07:26:48.718046, 0] nmbd/nmbd.c:71(terminate)
Got SIGTERM: going down...
[2010/05/04 07:27:26, 0] nmbd/nmbd.c:857(main)
nmbd version 3.5.2 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2010/05/04 07:27:26.544934, 0] nmbd/nmbd.c:696(open_sockets)
[2010/05/04 07:36:46, 0] nmbd/nmbd.c:857(main)
nmbd version 3.5.2 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010

DFS Folder Target to Samba Share not working

Hello folks,
I'm on Server 2012 R2. I'm using a DFS Namespace that is configured as standalone server (i.e. not a domain-based namespace). The Namespace is the IP address of the server. I have also tried this with the hostname of the server and I get the same results.
Here's my problem:
I've created a folder target within DFS that points to a samba share on a linux-based NAS. The samba share is a 'cloud storage' share hosted by my server host, so I'm not entirely sure what specific technology it is. It does not have a public ACL - it requires
authentication and I cannot change that. I can connect to the Namespace fine from other servers. However, when I try to open the folder target, it tells me "Logon failure: unknown user name or bad password". Then, if I right-click the folder, select
Properties then the DFS tab, I see that the path is Active. If I click Check Status, I get Okay, and when I exit, the folder is now navigable and I have no problems browsing the folders. Sometimes when I close Explorer, the share will still be accessible when
I reopen Explorer and browse to it, but most of the time when I close and reopen, the same error is displayed and I have to Check Status again to regain access. If I logout of the session, log back in and try again, it always gives me the error until I Check
Status again.
The idea is to access this share from multiple instances of IIS, so obviously requiring user intervention is not going to be suitable. I have added a local user to the DFS server that matches the valid credentials on the samba share, and I've also added
them to all the servers trying to use this share. I've confirmed that all servers can browse directly to the share. I do notice that when I browse directly to the samba share after having not used it for some time (30 minutes or one hour), it takes longer
than expected to open - maybe 10 seconds. Could this lag be causing the issue? There are no errors or warnings in the logs on the DFS server. Any ideas what this could be? Have I missed something? Massive thanks for any guidance!

Hi,
Thanks for your posting.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How do I add myself to the "staff" group for a samba share?

Hi all,
I've been struggling with this for a few hours now. I searched but could not find the answer (neither here nor google).
I am trying to set up a samba share on my raspberry pi and have it accessible by all other computer on my local network (just a home network). I want it set up so that when I access the share via my linux desktop I have read/write privileges, but when other users (my family, variety of linux and windows machines) access it they have read-only access and do not have to enter a password. I am not sharing any printers. The raspberry pi and my desktop are both running arch.
I am currently able to mount the share, but I only have read-only access. In the smb.conf file it has a pre-configured section for A publicly accessible directory, but read only, except for people in the "staff" group, which is the section I have tried to use. My user name on my desktop is 'gav', and I have created a user with the same name on the pi. On both the pi and the desktop I have added 'gav' to the staff group (using groupadd and usermod -aG).
On Windows machines: a Windows 7 desktop found the share and prompted for a password, I entered my password (as 'gav') and could access files, but read-only. A windows 8 laptop couldn't see it at all.
Here are some outputs of some things:
testparm (on the pi)
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
params.c:Parameter() - Ignoring badly formed line in configuration file: i
Processing section "[sharedfiles]"
Loaded services file OK.
Server role: ROLE_STANDALONE
[global]
workgroup = PISERVER
server string = Shared Media
log file = /var/log/samba/%m.log
max log size = 50
dns proxy = No
idmap config * : backend = tdb
[sharedfiles]
comment = Proper share
path = /mnt/sambashare
write list = @staff
guest ok = Yes
I'm not sure which is the 'badly formed line', any idea how I find out?
smbtree (on desktop)
WORKGROUP
PISERVER
\\PI Shared Media
\\PI\sharedfiles Proper share
\\PI\IPC$ IPC Service (Shared Media)
ASUSROUTER
smbclient -L PI -U% (on desktop)
Domain=[PISERVER] OS=[Unix] Server=[Samba 4.1.0]
Sharename Type Comment
IPC$ IPC IPC Service (Shared Media)
sharedfiles Disk Proper share
Domain=[PISERVER] OS=[Unix] Server=[Samba 4.1.0]
Server Comment
PI Shared Media
Workgroup Master
ASUSROUTER DSL-N55U
PISERVER PI
WORKGROUP SHODAN
command I entered to mount share (as root)
mount -t cifs //PI/sharedfiles /media/pi -o user=gav,password=pass,workgroup=PISERVER,ip=192.168.1.199
Any help would be appreciated, please let me know if there are any more outputs I can provide.
Thank you for reading
Last edited by gav989 (2013-11-10 13:34:46)

Consider using sshfs to mount your Pi from your Linux boxes. It's much easier to configure and manage than samba. It sounds like you already have your Windows machines mounting your Pi so Samba is doing its job in that respect.
More info on sshfs in the Wiki: https://wiki.archlinux.org/index.php/Sshfs
To help get you off the dime, here's a modified line from my fstab that I use to mount my Pi with:
gav@PI:/mnt/backup /mnt/rpi/backup fuse.sshfs rw,relatime,user_id=0,group_id=0,allow_other 0 0
Subsitute my mount points with yours.
For a password-less mount:
ssh-copy-id gav@PI
after you've set up ssh and generated some keys on your client box.
Here are some relevant lines from the smb.conf file on my Pi that I use for my one Windows box in the house that might help you with your write permissions:
security = user
hosts allow = 192.168.1.0/255.255.255.0
guest account = gav
; And my share setup:
[rpi]
comment = Public Stuff
path = /mnt
writable = yes
; printable = no
; write list = @krb
[torrent_dl]
path = /mnt/video/torrent_dl
writable = yes
create mask = 0770
directory mask = 0770
guest ok = Yes
case sensitive = No
read only = No
Hope this helps.

[Solved] Help Setting Samba Share In Qemu With XP Guest

Hello all,
After getting around all the quirks of setting an XP guest inside qemu, the only (though, pretty important) thing I can't solve is setting a samba share between the Arch host and the XP guest.
I tried whatever I could think of that's relevant, with no success:
Qemu is launched with:
qemu-system-x86_64 -machine type=pc,accel=kvm -cpu host -boot d -m 1024 -net user,smb={my home folder} -net nic,model=virtio -rtc base=localtime -drive file=XP.qcow2,if=virtio -spice port=5900,disable-ticketing,image-compression=off,jpeg-wan-compression=never,zlib-glz-wan-compression=never,playback-compression=off -vga qxl -global qxl-vga.vram_size=67108864 -device virtio-serial-pci -device virtserialport,chardev=spicechannel0,name=com.redhat.spice.0 -chardev spicevmc,id=spicechannel0,name=vdagent -balloon virtio
I installed samba, added a user, and started the service according to the wiki.
I allowed the samba ports in UFW (using the CIFS rule).
Whenever I try accessing the share inside my XP guest (\\10.0.2.4\qemu), I usually end up with a target not found error, or at times, a password prompt that will not accept the samba user/password.
Anything else I forgot to do?
Thanks, Adam.
* EDIT *
I somehow missed the section regarding the guest OS able to access the host OS normal samba shares at 10.0.2.2.
Default samba share for home folder works as expected.
Last edited by adam777 (2013-07-15 16:05:44)

Thanks.
I tried toying with the options a bit more, with no success.
I then decided to try Spice+QXL anyway, and am very happy with it.
Aside from the lengthy compilation of the Qemu version that supports Spice from the AUR, once I got it set up, installing the guest was a breeze.
Using the Spice guest tools for windows, everything was set up very conveniently (virtio for network, hdd, qxl driver, mouse integration etc.).
Responsiveness is much better comparing to previous attempts with "vga std", "vga cirrus" and normal adapter.
Bottom line, I'm sticking with Spice+QXL, seems to work best for me.

AutoFS + Samba share problems when share not online (especially in itunes)

I'm trying to look into having some or all of my media on a server for a couple of my macs, the main one of interest right now being a mac mini working as a HTPC under a tv, being operated 99% of the time with just the apple remote and frontrow.
A friend informed me that if you have your itunes library not managed and add files from a remote share then everything works pretty well. Namely if you try to play a file it will seemingly automount the remote file and start it playing. If the remote server is not available it will quickly discover this and after a short pause start giving explanation marks next to the broken tracks. Get the remote destination connected and then try to play a broken track and it will successfully mount the track and play.
Basically perfect.
I quickly tried accessing these files via a symbolic link or alias to them on the remote drive, in doing this i can be somewhat insulated from problems of trying to move the library to other machines/shares in the future. This all works fine but you do lose the ability for itunes to automatically mount the remote drive, which is a bit of a step back, but not a big deal on my normal machine. On my HTPC machine however i'd really like front row to be able to just work, hence automatically mounting the server as required.
The only problem was that when i tried with files directly added to the itunes library from a remote location frontrow would NOT automount the tracks/videos when you attempted to play them like itunes would do.
I've just spent the last few hours following the advice here
http://rajeev.name/blog/2007/11/22/autofs-goodness-in-apples-leopard-105-part-i/
to setup autofs in the hope that this would let me get auto mounting working as it does with itunes and directly added to the library remote files.
I boiled this down to the following settings
as root
vi /etc/auto_master
and add
/smb auto_smb
then create this new config file
vi /etc/auto_smb
and add
<Mount dir under /smb folder> -fstype=smbfs ://<share user>:<share pass>@<ip address>/<share point>
ie.
testMount -fstype=smbfs ://netuser:[email protected]/remoteMount
finally tell automount to throw away its cache
automount -vc
then the mount should be setup
df -h
shows the indirect map waiting
map auto_smb 0Bi 0Bi 0Bi 100% /smb
and by triggering it
ls /smb/testMount
you should connect and get a listing, a subsequent df shows
df -h
//[email protected]/Media 466Gi 325Gi 141Gi 70% /smb/Media
Everything worked well with the share getting mounted nicely when present, frontrow could just start playing the files it needed, perfect!!
The problem came when i wanted to simulate the media server being offline, basically frontrow, a lot of the system including finder, cd commands attempting to access the share, and itunes if you tried that would all freeze for long periods of time as they tried their best to get the files they were looking for.
I tried looking into getting this to gracefully time out and think i got somewhere by trying to setup the samba share to be soft linked.. I wasn't sure in what files i could add this to, first attempts didn't seem to do anything but adding this seemed to make a difference
/etc/nsmb.conf
containing something like
#Configuration file for example.com
[default]
minauth=ntlmv2
streams=yes
soft=yes
to turn soft samba shares on. Things like cd in a terminal seemed to behave quite well with this, when no remote share present you would get empty folders and the like. Finder would also seem to be reasonable with it.
Frustratingly itunes and frontrow both still have quite massive pauses even when finder and cds in the background show that perhaps the soft links are working and failing like they should.
I'm now left wondering what i can do to fix it, and resorting to perhaps having the files added via a symbolic link, using the login items to launch the remote share every boot and then having it so that all i need to do is reboot the HTPC mac mini if the server is on for it to pick it up and let me play the files. Otherwise they'll just be unavailable and will fail gracefully without locking up itunes. The perfect solution would be to either have a crontab running, or some applescript bound somehow to whenever frontrow is ran which manually tries to tell finder to do the equivelant mount the login items setup does.
It's frustrating though as its so close, and the autofs solution if it did work better would seem to be the perfect solution. Has anyone dabbled with this and got any suggestions as to options you can setup to make things not go horribly wrong when a remote share is NOT present, preferrably within the context of itunes or front row not complaining, but to be honest any suggestions i'll be able to try out myself.
Sorry i've written so much, perhaps some of it will be helpful reference as it took me a while to decipher that link at the top into just setting up a samba autofs.
Cheers.

It seems like it's not only the ArchLinux workstation that displays the norwegian letters wrong. The only machine that shows this correc is the machine that created the file/catalogue.
It seems like the windows 2000 displays the cataloge created by windows XP just fine.

User unable to umount samba share

Similar Messages

Maybe you are looking for