On 31/10/18 9:32 am, Ed Greshko wrote:
On 10/31/18 5:36 AM, Stephen Morris wrote:
On 30/10/18 1:14 pm, Ed Greshko wrote:
On 10/30/18 6:57 AM, Ed Greshko wrote:
This test may not be valid in your environment. What O/S is running on the server side?
FWIW, I have a Windows 10 VM that I've resurrected. I shared a folder and used the same
format entry in the fstab.
It mounts just fine on reboot. Having a bit of trouble figuring on the Windows side
allowing writing but that is due to my limited knowledge of MS products and
terminology. :-)
To be honest I don't know what operating is on the NAS device, and I can't see any
information in the web interface to tell me, but having said that I haven't really tried
to find out either. I'm assuming its linux, but I can't be sure.
The device seems to show itself as a Windows accessible device by default (which under
Linux I'm using CIFS to mount it) and also provides an NFS server interface that can be
activated if desired (which I have done and I mount it via NFS under Linux as well). In
my fstab entry for the CIFS mount I've added a systemd parameter to serialise the CIFS
mount behind the nfs mount, as some time ago I had issues where the NAS controller
couldn't handle systemd trying to do the automounting of the NFS and CIFS mount points
at the same time. Both mount points are the same physical storage, as I can write data
to the device under linux via the CIFS mount point or under Windows 10 and the NFS mount
point under Linux can see the data, but the same doesn't always apply the other way
around. I have a situation where I wrote a .apk file to the device from linux via the
NFS mount point and that file is not visible on the device from Windows 10 nor from the
CIFS mount point under Linux, but as expected it continues to be visible via the Linux
NFS mount point.
With the NFS mount process failing at boot time because of the Networkmanager Wait
Online process timing out, the CIFS serialisation cause that mount to fail at boot as
well, consequently I've added the x-systemd.automount parameter to both mount
definitions in fstab. Having done this issue the command "ls /mnt/nfs" mounts the nfs
interface as expected, but I can't get the same functionality to mount the CIFS mount
point, which I thought might have something to do with CIFS only being mountable by root
and not by an ordinary user.
Ahhh.... FWIW, I changed my fstab to....
//192.168.1.152/music /music cifs
credentials=/home/egreshko/.cifspw,rw,uid=egreshko,gid=egreshko,x-systemd.automount 0 0
//192.168.1.124/egreshko /home/egreshko/win10 cifs
credentials=/home/egreshko/.cifspw,rw,uid=egreshko,gid=egreshko,x-systemd.automount 0 0
.152 is a Linux based NAS
.124 is a Win10 system
After reboot.....
[egreshko@f29bk ~]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/fedora_f29bk-root 29106188 7648616 19955980 28% /
/dev/sda1 999320 216812 713696 24% /boot
[egreshko@f29bk ~]$ ls /music
ACDC part-1
Adele part-2
'Bruce Springsteen' 'Spyro Gyra - Down The Wire (2009)'
'Lady Gaga' 'The Rolling Stones - GRRR! - Deluxe Edition {mp3 320kbps}'
'Manhattan Transfer'
[egreshko@f29bk ~]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/fedora_f29bk-root 29106188 7648612 19955984 28% /
/dev/sda1 999320 216812 713696 24% /boot
//192.168.1.152/music 2879621632 906374608 1973247024 32% /music
[egreshko@f29bk ~]$ ls win10
'3D Objects'
AppData
<other junk>
[egreshko@f29bk ~]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/fedora_f29bk-root 29106188 7648612 19955984 28% /
/dev/sda1 999320 216812 713696 24% /boot
//192.168.1.152/music 2879621632 906374608 1973247024 32% /music
//192.168.1.124/egreshko 66110996 24305564 41805432 37% /home/egreshko/win10
So, no problems. No root needed.
When I issue df I get :
bash-4.4$ df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 8177492 0 8177492 0% /dev
tmpfs 8190472 484 8189988 1% /dev/shm
tmpfs 8190472 1748 8188724 1% /run
tmpfs 8190472 0 8190472 0% /sys/fs/cgroup
/dev/sdc6 847903444 65097840 739711488 9% /
tmpfs 8190472 56 8190416 1% /tmp
/dev/sda1 358396 51648 306748 15% /mnt/win-sys
/dev/sda6 9946988 170272 9248384 2% /mnt/ubuntu_boot
/dev/sda5 9946988 292968 9125688 4% /boot
/dev/sda2 228758524 114954456 113804068 51% /mnt/windows
/dev/sdc9 847902420 9159932 795648424 2% /mnt/ubuntu_root
/dev/sdc5 103181592 7231276 90685932 8% /home
/dev/sdc8 103181592 2062740 95854468 3% /mnt/ubuntu_home
/dev/sdb1 1953513468 1015969732 937543736 53% /mnt/win_data
tmpfs 1638092 12 1638080 1% /run/user/1000
My fstab CIFS entry is:
//192.168.0.12/Volume_1 /mnt/nas cifs
vers=1.0,username=*,password=*,cache=strict,rw,x-systemd.requires=/mnt/nfs,x-systemd.automount
0 0
If I issue the mount command as myself I get the following:
bash-4.4$ mount /mnt/nas
mount: /mnt/nas: operation permitted for root only.
If I add the users parameter to the fstab entry mount then tells me CIFS
doesn't allow user mounts.
//192.168.0.12/Volume_1 /mnt/nas cifs
vers=1.0,users,username=*,password=*,cache=strict,rw,x-systemd.requires=/mnt/nfs,x-systemd.automount
0 0
bash-4.4$ mount /mnt/nas
This program is not installed setuid root - "user" CIFS mounts not
supported.
Listing the contents of /mnt/nas produces the following:
bash-4.4$ ls /mnt/nas
bash-4.4$ df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 8177492 0 8177492 0% /dev
tmpfs 8190472 532 8189940 1% /dev/shm
tmpfs 8190472 1748 8188724 1% /run
tmpfs 8190472 0 8190472 0% /sys/fs/cgroup
/dev/sdc6 847903444 65097844 739711484 9% /
tmpfs 8190472 56 8190416 1% /tmp
/dev/sda1 358396 51648 306748 15% /mnt/win-sys
/dev/sda6 9946988 170272 9248384 2% /mnt/ubuntu_boot
/dev/sda5 9946988 292968 9125688 4% /boot
/dev/sda2 228758524 114954456 113804068 51% /mnt/windows
/dev/sdc9 847902420 9159932 795648424 2% /mnt/ubuntu_root
/dev/sdc5 103181592 7231708 90685500 8% /home
/dev/sdc8 103181592 2062740 95854468 3% /mnt/ubuntu_home
/dev/sdb1 1953513468 1015969732 937543736 53% /mnt/win_data
tmpfs 1638092 12 1638080 1% /run/user/1000
Have I done something wrong in my setup? I can't remove the
x-systemd.requires parameter unless there is some way of stopped systemd
from trying to mount the nfs and cifs mount points at the same time,
because with my device they interfere with each other and eventually
time out result in them not being mounted anyway.
regards,
Steve
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
