I have a Solaris 10 LDOM installed with UFS and another Solaris 11 LDOM with ZFS. I want to mount a folder on Solaris 10 to Solaris 11. I used the following:
sudo mount -F ufs 10.1.1.44:/export/home/amandeep/workspace /home/amandeep/workspace/mounts/ldom5
and it errors out with:
mount: 10.1.1.44:/export/home/amandeep/workspace or /home/amandeep/workspace/mounts/ldom5, no such file or directory
What am I missing?
Because 10.1.1.44:/export/home/amandeep/workspace is a NFS location.
You must mount this with "-F nfs" (without this option "mount" will automatically see it is NFS).
Hello @MadeInGermay,
How would one know that this is a NFS location. I am very new to solaris and still learning. Following is the output of mount command on 10.1.1.44:
bash-3.2$ /usr/sbin/mount -v
/dev/dsk/c0d1s0 on / type ufs read/write/setuid/devices/rstchown/intr/largefiles/logging/xattr/onerror=panic/dev=2080008 on Tue Sep 25 17:29:06 2018
/devices on /devices type devfs read/write/setuid/devices/rstchown/dev=5bc0000 on Tue Sep 25 17:29:05 2018
ctfs on /system/contract type ctfs read/write/setuid/devices/rstchown/dev=5c00001 on Tue Sep 25 17:29:05 2018
proc on /proc type proc read/write/setuid/devices/rstchown/dev=5c40000 on Tue Sep 25 17:29:05 2018
mnttab on /etc/mnttab type mntfs read/write/setuid/devices/rstchown/dev=5c80001 on Tue Sep 25 17:29:05 2018
swap on /etc/svc/volatile type tmpfs read/write/setuid/devices/rstchown/xattr/dev=5cc0001 on Tue Sep 25 17:29:05 2018
objfs on /system/object type objfs read/write/setuid/devices/rstchown/dev=5d00001 on Tue Sep 25 17:29:05 2018
sharefs on /etc/dfs/sharetab type sharefs read/write/setuid/devices/rstchown/dev=5d40001 on Tue Sep 25 17:29:05 2018
/dev/dsk/c0d1s6 on /usr type ufs read/write/setuid/devices/rstchown/intr/largefiles/logging/xattr/onerror=panic/dev=208000e on Tue Sep 25 17:29:07 2018
/platform/sun4v/lib/libc_psr/libc_psr_hwcap3.so.1 on /platform/sun4v/lib/libc_psr.so.1 type lofs read/write/setuid/devices/rstchown/dev=2080008 on Tue Sep 25 17:29:06 2018
/platform/sun4v/lib/sparcv9/libc_psr/libc_psr_hwcap3.so.1 on /platform/sun4v/lib/sparcv9/libc_psr.so.1 type lofs read/write/setuid/devices/rstchown/dev=2080008 on Tue Sep 25 17:29:06 2018
fd on /dev/fd type fd read/write/setuid/devices/rstchown/dev=5ec0001 on Tue Sep 25 17:29:07 2018
/dev/dsk/c0d1s3 on /var type ufs read/write/setuid/devices/rstchown/intr/largefiles/logging/xattr/onerror=panic/dev=208000b on Tue Sep 25 17:29:10 2018
swap on /tmp type tmpfs read/write/setuid/devices/rstchown/xattr/dev=5cc0002 on Tue Sep 25 17:29:10 2018
swap on /var/run type tmpfs read/write/setuid/devices/rstchown/xattr/dev=5cc0003 on Tue Sep 25 17:29:10 2018
/dev/dsk/c0d1s5 on /opt type ufs read/write/setuid/devices/rstchown/intr/largefiles/logging/xattr/onerror=panic/dev=208000d on Tue Sep 25 17:29:41 2018
/dev/dsk/c0d1s1 on /usr/openwin type ufs read/write/setuid/devices/rstchown/intr/largefiles/logging/xattr/onerror=panic/dev=2080009 on Tue Sep 25 17:29:42 2018
/dev/dsk/c0d1s7 on /export/home type ufs read/write/setuid/devices/rstchown/intr/largefiles/logging/xattr/onerror=panic/dev=208000f on Tue Sep 25 17:29:42 2018
Regards,
Aman
The server:/pathname is a remote filesystem, by default NFS.
A /dev/pathname is a local filesystem, by default UFS (in Solaris <= 10, not sure with Solaris 11).
Well Because of your request above : Solaris 10 to Solaris 11 means from a system to another, and that, can only be achieve across network thus NFS ( Network FileSystem) then in your same request and statement you give the IP of the system (NFS server) exporting: 10.1.1.44 .
So now did you try mount without options?
It should work ( but cannot be sure beeing at home without boxes to try... used with HP-UX and some AIX, not quite sure about Solaris)
the advantages of arguments are to give more mount options like some NFS options letting you able to dismount when server is not responding etc... I dont see any reason to give UFS only to create errors since its not...
That said and MadeInGermany gave you a syntax to try, if your mount directory on the client side is absent you will get error too...( not mentioning the same server side...) and since its network you should check you can reach the NFS server by using ping or anything else to see if it responds
Yes, I was able to mount it as NFS. But was curious about if we could use UFS. Thanks for the help.
On the NFS server the exported(=shared) file system is mounted locally, from /dev/pathname or from ZFS that is rpool/pathname (the ZFS developers decided to not implement its access via a /dev/pathname device driver; instead ZFS has its own kernel API and its own commands).
BTW besides NFS there is another remote file system RFS - but Solaris and all other Unixes prefer NFS. BSD Unix and Linux have NFS only.
A good reason for not implementing them that way is that there is no one to one relationship between a file system and a device with ZFS. Multiple file systems can and often share the same ZFS pool, and a ZFS pool can use one or more backends which are not necessarily disk devices but can be simple files.