You are not logged in.
Since upgrading my linux kernel from 3.3.8 to 3.4.2 I've noticed that my cifs mounts fail at boot time.
The relevant portion of my fstab file is as follows:
//192.168.1.100/share /mnt/share/ cifs noatime,_netdev,password=foo,uid=USER,gid=GROUP,file_mode=0644,dir_mode=0755 0 0
//192.168.1.54/MP3z /mnt/MP3z/ cifs noatime,_netdev,password=foo,uid=USER,gid=GROUP,file_mode=0644,dir_mode=0755 0 0
//192.168.1.100/other_stuff /mnt/other_stuff/ cifs noatime,_netdev,password=foo,uid=USER,gid=GROUP,file_mode=0644,dir_mode=0755 0 0
Looking at the error log I see the following lines:
Jun 15 09:34:11 localhost kernel: [ 13.204578] CIFS: Unknown mount option "noatime"
Jun 15 09:34:11 localhost kernel: [ 13.207548] CIFS: Unknown mount option "noatime"
Jun 15 09:34:11 localhost kernel: [ 13.210119] CIFS: Unknown mount option "noatime"
Jun 15 09:34:11 localhost kernel: [ 13.214924] CIFS: Unknown mount option "noatime"
Jun 15 09:34:11 localhost kernel: [ 13.217581] CIFS: Unknown mount option "noatime"
Jun 15 09:34:11 localhost kernel: [ 13.223864] CIFS: Unknown mount option "noatime"
While my fstab config seemed to work in 3.3.8 it now breaks my network shares. Removing the noatime option fixes things but I don't know why. Is the noatime option invalid? The current revision of the Samba wiki page advises using the noatime option. Is this incorrect?
Offline
Man pages beat wiki pages every time, and the mount.cifs man page makes no reference to noatime.
Offline
Found out this same thing this morning. Was getting constant invalid argument errors and indeed removing "noatime" from the fstab entries fixes it. Looking at mount.cifs man page there is not only no reference to noatime but neither to relatime or anything like that.
Guess that functionality has been removed in cifs-utils? Not sure but the Wiki will need updating regardless.
Last edited by ElderSnake (2012-06-16 02:59:36)
Arch Linux - Intel E5200 Desktop (MATE GTK3) | Fedora 25 - ASUS Core-i7 Optimus Laptop
Offline
Removing noatime from some lines in /etc/fstab soved it for me.
There is a difference between knowing the path and walking the path.
Offline
I added a short note about this problem on the arch wiki for samba.
Offline