Large-size NFS mounts

Hello,
I'm having a problem mounting an NFS-shared volume. The problem could be one of two things, but I am unable to find any documentation for either concerning leopard server. To explain:
Our xserve is a "head" for a network of sub-servers running amd64 Debian Etch, each managing two ~13 terra blocks (raid 5) of storage space using an xfs filesystem.
I had orginally formatted the Linux-server disks using cfdisk, but this only allows partitions of less than two terra. Nonetheless, I was able to NFS-export the two-terra configurations and mount them successfully in Leopard.
The problem arose when I reformatted the drives using another method (13t partitions made with "parted", with a gpt partition table, 512k blocks): Leopard was able to recognize and "mount" the NFS drives, and the alias appears in the finder where I imported them (/Volumes/), but when I try to explore the mounted partition (by clicking the alias) I get an error message "the volume for "(diskname)" cannot be found."
My questions are these: Does Leopard have limits as to the size of an NFS it can mount? Or does Leopard not recognize a gpt partition table?
Thank you very much for any advice.

Cancel the above - my error was elsewhere, and a rather stupid one. When mounting Linux-driven NFS exports in Leopard, one must give the "special Port" directive - -P - ; I forgot to add this on my latest auto-mount configurations.
Thanks to all who read, and sorry for the waste of space.
Cheers.

Similar Messages

NFS4: Problem mounting NFS mount onto a Solaris 10 Client

Hi,
I am having problems mounting NFS mount point from a Linux-Server onto a Solaris 10 Client.
In the following
=My server IP ..*.120
=Client IP ..*.100
Commands run on Client:
==================
# mount -o vers=3 -F nfs 172.25.30.120:/scratch/pvfs2 /scratch/pvfs2
nfs mount: 172.25.30.120: : RPC: Rpcbind failure - RPC: Unable to receive
nfs mount: retrying: /scratch/pvfs2
nfs mount: 172.25.30.120: : RPC: Rpcbind failure - RPC: Unable to receive
nfs mount: 172.25.30.120: : RPC: Rpcbind failure - RPC: Unable to receive
# mount -o vers=4 -F nfs 172.25.30.120:/scratch/pvfs2 /scratch/pvfs2
nfs mount: 172.25.30.120:/scratch/pvfs2: No such file or directory
# rpcinfo -p
program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
1073741824 1 tcp 36084
100024 1 udp 42835 status
100024 1 tcp 36086 status
100133 1 udp 42835
100133 1 tcp 36086
100001 2 udp 42836 rstatd
100001 3 udp 42836 rstatd
100001 4 udp 42836 rstatd
100002 2 tcp 36087 rusersd
100002 3 tcp 36087 rusersd
100002 2 udp 42838 rusersd
100002 3 udp 42838 rusersd
100011 1 udp 42840 rquotad
100021 1 udp 4045 nlockmgr
100021 2 udp 4045 nlockmgr
100021 3 udp 4045 nlockmgr
100021 4 udp 4045 nlockmgr
100021 1 tcp 4045 nlockmgr
100021 2 tcp 4045 nlockmgr
100021 3 tcp 4045 nlockmgr
100021 4 tcp 4045 nlockmgr
# showmount -e 172.25.30.120 (Server)
showmount: 172.25.30.120: RPC: Rpcbind failure - RPC: Unable to receive
Commands OnServer:
================
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100021 1 tcp 49927 nlockmgr
100021 3 tcp 49927 nlockmgr
100021 4 tcp 49927 nlockmgr
100021 1 udp 32772 nlockmgr
100021 3 udp 32772 nlockmgr
100021 4 udp 32772 nlockmgr
100011 1 udp 796 rquotad
100011 2 udp 796 rquotad
100011 1 tcp 799 rquotad
100011 2 tcp 799 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 809 mountd
100005 1 tcp 812 mountd
100005 2 udp 809 mountd
100005 2 tcp 812 mountd
100005 3 udp 809 mountd
100005 3 tcp 812 mountd
100024 1 udp 854 status
100024 1 tcp 857 status
# showmount -e 172.25.30.120
Export list for 172.25.30.120:
/scratch/nfs 172.25.30.100,172.25.24.0/4
/scratch/pvfs2 172.25.30.100,172.25.24.0/4
Thank you, ~al

I also tried to run Snoop on the client and wireshark on Server and following is what I see:
One Server: Upon issuing mount command on client:
# tshark -i eth1
Running as user "root" and group "root". This could be dangerous.
Capturing on eth1
0.000000 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
0.205570 172.25.30.100 -> 172.25.30.120 Portmap V2 GETPORT Call MOUNT(100005) V:3 UDP
0.205586 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
0.207863 172.25.30.100 -> 172.25.30.120 Portmap V2 GETPORT Call MOUNT(100005) V:3 UDP
0.207869 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
2.005314 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
4.011005 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
5.206109 Dell_70:ad:29 -> SunMicro_70:ff:17 ARP Who has 172.25.30.100? Tell 172.25.30.120
5.206277 SunMicro_70:ff:17 -> Dell_70:ad:29 ARP 172.25.30.100 is at 00:14:4f:70:ff:17
5.216157 172.25.30.100 -> 172.25.30.120 Portmap V2 GETPORT Call MOUNT(100005) V:3 UDP
5.216170 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
On Clinet Upon issuing mount command on client:
# snoop -d bge1
Using device /dev/bge1 (promiscuous mode)
? -> * ETHER Type=9000 (Loopback), size = 60 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
atlas-pvfs2 -> pvfs2-io-0-3 PORTMAP C GETPORT prog=100005 (MOUNT) vers=3 proto=UDP
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (UDP port 111 unreachable)
atlas-pvfs2 -> pvfs2-io-0-3 PORTMAP C GETPORT prog=100005 (MOUNT) vers=3 proto=UDP
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (UDP port 111 unreachable)
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> * ETHER Type=9000 (Loopback), size = 60 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
pvfs2-io-0-3 -> * ARP C Who is 172.25.30.100, atlas-pvfs2 ?
atlas-pvfs2 -> pvfs2-io-0-3 ARP R 172.25.30.100, atlas-pvfs2 is 0:14:4f:70:ff:17
atlas-pvfs2 -> pvfs2-io-0-3 PORTMAP C GETPORT prog=100005 (MOUNT) vers=3 proto=UDP
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (UDP port 111 unreachable)
Also I see the following on Client:
# rpcinfo -p pvfs2-io-0-3
rpcinfo: can't contact portmapper: RPC: Rpcbind failure - RPC: Failed (unspecified error)
When I try the above rpcinfo command on Client and Server Snoop And wireshark(ethereal) outputs are as follows:
Client # snoop -d bge1
Using device /dev/bge1 (promiscuous mode)
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
atlas-pvfs2 -> pvfs2-io-0-3 TCP D=111 S=872 Syn Seq=2065245538 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK>
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (TCP port 111 unreachable)
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=2004 (Unknown), size = 48 bytes
? -> (multicast) ETHER Type=0003 (LLC/802.3), size = 90 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> * ETHER Type=9000 (Loopback), size = 60 bytes
pvfs2-io-0-3 -> * ARP C Who is 172.25.30.100, atlas-pvfs2 ?
atlas-pvfs2 -> pvfs2-io-0-3 ARP R 172.25.30.100, atlas-pvfs2 is 0:14:4f:70:ff:17
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
atlas-pvfs2 -> pvfs2-io-0-3 TCP D=111 S=874 Syn Seq=2068043912 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK>
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (TCP port 111 unreachable)
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> * ETHER Type=9000 (Loopback), size = 60 bytes
Server # tshark -i eth1
Running as user "root" and group "root". This could be dangerous.
Capturing on eth1
0.000000 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
0.313739 Cisco_3d:68:10 -> CDP/VTP/DTP/PAgP/UDLD CDP Device ID: MILEVA Port ID: GigabitEthernet1/0/16
2.006422 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
3.483733 172.25.30.100 -> 172.25.30.120 TCP 865 > sunrpc [SYN] Seq=0 Win=49640 Len=0 MSS=1460 WS=0
3.483752 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
4.009741 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
6.014524 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
6.551356 Cisco_3d:68:10 -> Cisco_3d:68:10 LOOP Reply
8.019386 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
8.484344 Dell_70:ad:29 -> SunMicro_70:ff:17 ARP Who has 172.25.30.100? Tell 172.25.30.120
8.484569 SunMicro_70:ff:17 -> Dell_70:ad:29 ARP 172.25.30.100 is at 00:14:4f:70:ff:17
10.024411 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
12.030956 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
12.901333 Cisco_3d:68:10 -> CDP/VTP/DTP/PAgP/UDLD DTP Dynamic Trunking Protocol
12.901421 Cisco_3d:68:10 -> CDP/VTP/DTP/PAgP/UDLD DTP Dynamic Trunking Protocol
^[[A 14.034193 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
15.691119 172.25.30.100 -> 172.25.30.120 TCP 866 > sunrpc [SYN] Seq=0 Win=49640 Len=0 MSS=1460 WS=0
15.691138 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
16.038944 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
16.550760 Cisco_3d:68:10 -> Cisco_3d:68:10 LOOP Reply
18.043886 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
20.050243 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
21.487689 172.25.30.100 -> 172.25.30.120 TCP 867 > sunrpc [SYN] Seq=0 Win=49640 Len=0 MSS=1460 WS=0
21.487700 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
22.053784 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
24.058680 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
26.063406 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
26.558307 Cisco_3d:68:10 -> Cisco_3d:68:10 LOOP Reply
~thank you for any help you can provide!!!

Cannot write to NFS mount with finder

hi folks
i have moved from a G4 cube running 10.4.9 to a new iMac running os x 10.5.7 (including upgrading from the old machine)
the NFS mounts i used to have with my G4 cube are not working properly; new mounts i've created aren't working properly either.
i can read/open file OK, but when i try to drag & drop files onto the NFS mount using the finder i get errors:
"You may need to enter the name and password for an administrator on this computer to change the item named test.jpg" [ stop ] [ continue ]
clicking "continue" i get:
"The item test.jpg contains one or more items you do not have permission to read. Do you want to copy the items you are allowed to read? [ stop ] [ continue ]
Choosing continue again results in the file appearing in the NFS directory, but with 0 size, and a time stamp of 1970.
if i try to copy the same file using the Terminal, it works fine - so it is not a simple NFS permissions problem - it is something particular to the Finder.
i am able to create a folder inside the NFS director by using the Finder.
i thought at first it might be related to the .DS_Store and similar files being written, so i tried turning off that behaviour:
defaults write com.apple.desktopservices DSDontWriteNetworkStores true
but that hasn't fixed the problem
there are no obvious messages in any of the logs
any suggestions or pointers on how to fix this?

thanks for the reply
these articles appear to relate to sharing a mac filesystem via NFS: exporting the data.
i am referring to mounting a NFS filesystem from another server onto the mac (leopard) client
the mounting works fine: it's just the finder which isn't behaving. the finder worked in tiger; isn't in leopard.

Autofs timeout while accessing to remote NFS mount

Following Apple recommendations, I switched to "Directory Utility" to configure NFS mounts. As far as I understand, if you do so, the mounts are handled by automount which is itself called by autofs. The good thing of this is that autofs is unmounting unused mounts (after a timeout of 3600 seconds as defined in /etc/autofs.conf). Any time you need the remote drive (Finder call, ls in Terminal..., opening file), autofs is remounting ressource. This is a nice behaviour... in theory.
I'm using some codes (written in IDL) that are reading and writing on that remote NFS server once every 5 minutes. Theoretically, autofs should be detecting these accesses and should keep the drive mounted. This is unfortunately not the case. The drive is unmounted 3600 seconds after I last accessed the mount through the Finder or with any other Application.
There is apparently no way to remove this "automated unmounting" feature. I tried to set the timeout delay to a very large number (1 day) but it still disconnects me after this delay, if I don't do anything else than running my IDL code. If I mount the NFS share with the "mount_nfs" command, it works perfectly, as it is not handled by autofs.
I wonder then if there is any recommandation on Apple's side in such a case, other than going back to traditional mount_nfs.

As you have discovered, automount/autofs is also an "auto-unmounter" and there is no way to remove that feature. Contrary to what one might think, the auto unmounting does NOT happen after a period of "inactivity" of the mount. This is because autofs has no way of knowing when an automounted file system was last accessed. So, instead it periodically attempts to unmount it - if it is busy it won't get unmounted - if it isn't busy it will get unmounted.
You can't disable this - but you can make the periodic unmounting so infrequent as to effectively disable the feature. Try setting the AUTOMOUNT_TIMEOUT interval to something really large - like 315360000 (which would be 10 years).
However, in theory, this auto-unmounting should not be a problem because if it does get unmounted then the next access to that file system should cause it to get mounted again. And all this should happen without the code that is accessing the automount knowing that it isn't always mounted. It should always be there when it is accessed. So, the usual response to someone asking how to disable the auto-unmounting is to ask why they think it is a problem.
(Oh, and you don't have to use "mount_nfs" - just "mount" should work to manually mount an NFS file system (that saves a little typing).)
HTH
--macko

NFS mount error messages on Solaris 8; is there a patch?

We recently purchased an EMC Celerra NS80 to serve as a front end to our Centerra archive solution. On a Solaris 8 box I've been seeing a large number of NFS errors in the /var/adm/messages file relating directly to the datamover on the NS80. I've tried everything I can think of from the array side of the house to no avail. EMC states there is fix for this problem, patch 113318-12, but according to the patch notes this is for an NFS problem with Solaris 9.
The error is causing sporadic performance issues when our end users attempt to pull up the data that resides on the Celerra NFS mount, so I would really like to get it resolved. The specific error message is:
NFS server DATAMOVER1 not responding still trying
NFS server DATAMOVER1 ok
The messages of not responding and ok tend to relate every few seconds to 3-5 minutes delay. Our database vendor insists something on the NS80 is introducing this error, but I cannot find anything to change to clear this up.
Any input would be greatly appreciated.
Thanks.

SunOS www02.unix 5.10 Generic_127128-11 i86pc i386 i86pc
10:58am up 22:51, 4 users, load average: 2.16, 2.26, 2.26
/export/www
cache hit rate: 99% (111069900 hits, 6674 misses)
consistency checks: 459000 (458945 pass, 55 fail)
modifies: 0
garbage collection: 0
/export/zero
cache hit rate: 94% (2089349 hits, 110629 misses)
consistency checks: 1497690 (1497075 pass, 615 fail)
modifies: 0
garbage collection: 0
/export/saba
cache hit rate: 97% (7677577 hits, 174056 misses)
consistency checks: 10809059 (10801491 pass, 7568 fail)
modifies: 0
garbage collection: 0
So 1 day uptime, that is much better. We rebooted it for mirroring setup, and found that cachefs needs to fsck before it comes up. Can I not simply have it start afresh rather than attempt to keep cache directory? (Obviously I can, but I mean in a boot-friendly manner)

NFS mount unmounting automatically

Hi There,
I have an issue where I have a NFS mount on my client. Here, NFS server and client are configured on the same server. After a period of time for some reason this mount point disappears or unmounts. Could anyone enlighten me on why this occurs?
Thanks for any help in advance.

Hi Cindy,
Here, the NFS server and client is the same.
root@GTRFO005 #df -kh /smb
Filesystem             size   used avail capacity Mounted on
localhost:/smb         1.0G   512M   512M    50%    /smb
root@GTRFO005 #share
-               /smb   rw   ""
root@GTRFO005 #mount
/ on /dev/md/dsk/d0 read/write/setuid/devices/rstchown/intr/largefiles/logging/xattr/onerror=panic/dev=1540000 on Sun Apr 19 01:54:40 2015
/devices on /devices read/write/setuid/devices/rstchown/dev=5940000 on Sun Apr 19 01:53:47 2015
/system/contract on ctfs read/write/setuid/devices/rstchown/dev=5980001 on Sun Apr 19 01:53:47 2015
/proc on proc read/write/setuid/devices/rstchown/dev=59c0000 on Sun Apr 19 01:53:47 2015
/etc/mnttab on mnttab read/write/setuid/devices/rstchown/dev=5a00001 on Sun Apr 19 01:53:47 2015
/etc/svc/volatile on swap read/write/setuid/devices/rstchown/xattr/dev=5a40001 on Sun Apr 19 01:53:47 2015
/system/object on objfs read/write/setuid/devices/rstchown/dev=5a80001 on Sun Apr 19 01:53:47 2015
/etc/dfs/sharetab on sharefs read/write/setuid/devices/rstchown/dev=5ac0001 on Sun Apr 19 01:53:47 2015
/platform/sun4u-us3/lib/libc_psr.so.1 on /platform/sun4u-us3/lib/libc_psr/libc_psr_hwcap1.so.1 read/write/setuid/devices/rstchown/dev=154000
0 on Sun Apr 19 01:54:37 2015
/platform/sun4u-us3/lib/sparcv9/libc_psr.so.1 on /platform/sun4u-us3/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1 read/write/setuid/devices/rst
chown/dev=1540000 on Sun Apr 19 01:54:38 2015
/dev/fd on fd read/write/setuid/devices/rstchown/dev=5c40001 on Sun Apr 19 01:54:40 2015
/var on /dev/md/dsk/d2 read/write/setuid/devices/rstchown/intr/largefiles/logging/xattr/onerror=panic/dev=1540002 on Sun Apr 19 01:54:46 201
5
/tmp on swap read/write/setuid/devices/rstchown/xattr/dev=5a40002 on Sun Apr 19 01:54:46 2015
/var/run on swap read/write/setuid/devices/rstchown/xattr/dev=5a40003 on Sun Apr 19 01:54:46 2015
/auditlog5 on /dev/md/dsk/d154 read/write/setuid/devices/rstchown/intr/largefiles/logging/xattr/onerror=panic/dev=154009a on Sun Apr 19 01:5
5:04 2015
/opt on /dev/md/dsk/d3 read/write/setuid/devices/rstchown/intr/largefiles/logging/xattr/onerror=panic/dev=1540003 on Sun Apr 19 01:55:04 201
5
/global/.devices/node@1 on /dev/md/dsk/d80 read/write/setuid/devices/rstchown/intr/largefiles/logging/noquota/global/xattr/nodfratime/onerro
r=panic/dev=1540050 on Sun Apr 19 01:56:17 2015
/global/.devices/node@3 on /dev/md/dsk/d83 read/write/setuid/devices/rstchown/intr/largefiles/logging/noquota/global/xattr/nodfratime/onerro
r=panic/dev=1540053 on Sun Apr 19 01:56:17 2015
/global/.devices/node@4 on /dev/md/dsk/d92 read/write/setuid/devices/rstchown/intr/largefiles/logging/noquota/global/xattr/nodfratime/onerro
r=panic/dev=154005c on Sun Apr 19 01:56:17 2015
/apps_cl on /dev/md/sgd-mset/dsk/d120 read/write/setuid/devices/rstchown/intr/largefiles/logging/xattr/onerror=panic/dev=1546078 on Sun Apr
19 02:01:13 2015
/smb on localhost:/smb remote/read/write/setuid/devices/rstchown/proto=udp/vers=2/port=4242/xattr/dev=5cc0001 on Sun Apr 19 02:03:51 2015
/global/.devices/node@2 on /dev/md/dsk/d89 read/write/setuid/devices/rstchown/intr/largefiles/logging/noquota/global/xattr/nodfratime/onerro
r=panic/dev=1540059 on Sun Apr 19 05:05:41 2015
/net/gtrfo005 on / read/write/nosetuid/nodevices/rstchown/dev=1540000 on Sun Apr 19 09:29:54 2015
root@GTRFO005 #

Vi error on nfs mount; E212: Can't open file for writing

Hi all,
I've setup a umask of 0 for testing on both NFS client (Centos 5.2) and NFS server (OSX 10.5.5 server).
I can create files as one user and edit/save out as another user w/o issue when directly logged into the server via ARD.
However, when I attempt the same from an NFS mount on a client machine, even as root I get the following error using vi;
"file" E212: Can't open file for writing
Looking at the system.log file on the server, I see;
kernel[0]: add_fsevent: no name hard-link! dropping the event. (event 2 vp == 0xa5db510 (-UNKNOWN-FILE)).
This baffles me. My umask is 0 meaning files I create and attempt to edit as other users are 777, but I cannot save out edits unless I do a wq! in vi. At that point, the owner of the file changes to whomever did the vi.
This isn't just a vi issue as it happens using any editor, but I like to use vi.
Any help is greatly appreciated. Hey, beer is on me!

Hi all,
Thanks for the replies
I've narrowed it down to a Centos client issue.
Everything works fine using other Linux based OS's as clients.
Since we have such a huge investment in Centos, I must figure out a workaround. Apple support wasn't much help as usual however they were very nice.
There usual response is "its unsupported".
If Apple really wants to play in the enterprise of business space, they really need to change there philosophy. I mean telling me that I shouldn't mount home directories via NFS is completely rediculus.
What am I supposed to use then, Samba of AFP? No, I don't think so. No offense to Microsoft but why would I use a Windows based file sharing protocol to mount network shares in a Nix env???

When I download pictures from my camera, they turn out a nice big size in iPhoto; other pictures that have been e-mailed to me or imported from older libraries/other computers show up small. Why is this, and how can I make them all the larger size?

When I download pictures from my digital camera into iPhoto, they turn out a nice large size (usually almost the full screen), but when somebody e-mails me pictures and I import them into iPhoto, or when I transfer old photos from an old library into my new iPhoto library, they turn out very small--not exactly thumbnail-size, but too small to use for calendars or photo books. I don't know much about computers, so I don't know how this happened. Also, I can't find any discernible pattern to why this happens with some pictures and not others--ie: what I described above is usually true, but I have had e-mailed photos or old photos turn out the way I want them, which is in the larger size in iPhoto. Why is this happening, and how can I make all the pictures the larger size?

Some mail programs, including Apple Mail, can reduce the size of images that are attached to a message. It's happening at the sender's end, and all you can do is ask the sender for a larger image.

Accessing NFS mounted share in Finder no longer works in 10.5.3+

I have setup an automounted NFS share previously with Leopard against a RHEL 5 server at the office. I had to go through a few loops to punch a hole through the appfirewall to get the share accessible in the Finder.
A few months later when I returned to the office after a consultancy stint and upgrades to 10.5.3 and 10.5.4 the NFS mount no longer works. I have investigated it today and I can't get it to run even with the appfirewall disabled.
I've been doing some troubleshooting, and the interaction between the statd, lockd and perhaps the portmap seem a bit fishy, even with the appfirewall disabled. Both the statd and lockd complains that they can not register; lockd once and statd indefinitely.
Jul 2 15:17:10 ySubmarine com.apple.statd[521]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
Jul 2 15:17:10 ySubmarine com.apple.launchd[1] (com.apple.statd[521]): Exited with exit code: 1
Jul 2 15:17:10 ySubmarine com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
... and rpcinfo -p gets connection refused unless I start portmap using the launchctl utility.
This may be a bit obscure, and I'm not exactly an expert of NFS, so I wonder if someone else stumbled across this, and can point me in the right direction?
Johan

Sorry for my late response, but I have finally got around to some trial and error. I can mount the share using mount_nfs (but need to use sudo), and it shows up as a mounted disk in the Finder. However, when I start to browse a directory on the share that I can write to, I end up with the lockd and statd failures.
$ mount_nfs -o resvport xxxx:/home /Users/yyyy/xxxx-home
mount_nfs: /Users/yyyy/xxxx-home: Permission denied
$ sudo mount_nfs -o resvport xxxx:/home /Users/yyyy/xxxx-home
Jul 7 10:37:34 zzzz com.apple.statd[253]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
Jul 7 10:37:34 zzzz com.apple.launchd[1] (com.apple.statd[253]): Exited with exit code: 1
Jul 7 10:37:34 zzzz com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
Jul 7 10:37:44 zzzz com.apple.statd[254]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
Jul 7 10:37:44 zzzz com.apple.launchd[1] (com.apple.statd[254]): Exited with exit code: 1
Jul 7 10:37:44 zzzz com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
Jul 7 10:37:54 zzzz com.apple.statd[255]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
Jul 7 10:37:54 zzzz com.apple.launchd[1] (com.apple.statd[255]): Exited with exit code: 1
Jul 7 10:37:54 zzzz com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
Jul 7 10:37:58 zzzz loginwindow[25]: 1 server now unresponsive
Jul 7 10:37:59 zzzz KernelEventAgent[26]: tid 00000000 unmounting 1 filesystems
Jul 7 10:38:02 zzzz com.apple.autofsd[40]: automount: /net updated
Jul 7 10:38:02 zzzz com.apple.autofsd[40]: automount: /home updated
Jul 7 10:38:02 zzzz com.apple.autofsd[40]: automount: no unmounts
Jul 7 10:38:02 zzzz loginwindow[25]: No servers unresponsive
... and firewall wide open.
I guess that the Finder somehow triggers file locking over NFS.

Cannot access external NFS mounts under Snow Leopard

I was previously running Leopard (10.5.x) and automounted an Ubuntu (9.04 Jaunty) Linux NFS mount from my iMac. I had set this up with Directory Utility and it was instantly functional and I never had any issues. After upgrading to Snow Leopard, I set up the same mount point on the same machine (using Disk Utility now), without changing any of the export settings, and Disk Utility stated that the external server had responded and appeared to be working correctly. However, when attempting to access the share, I get a 'Operation not permitted' error. I also cannot manually create the NFS mount using mount or mount_nfs. I get a similar error if I try to cd into /net/<remote-machine>/<share>. I can see the shared folder in /net/<remote-machine>, but I cannot access it (cd, ls, etc). I can see on the Linux machine that the iMac has mounted the share (showmount -a), so the problem appears to be solely in the permissions. But I have not changed any of the permissions on the remote machine, and even then, they are blown wide open (777) so I'm not sure what is causing the issue. I have tried everything as both a regular user, and as root. Any thoughts?
On the Linux NFS server:
% cat /etc/exports
/share 192.168.1.0/24(rw,sync,nosubtree_check,no_rootsquash)
% showmount -a
All mount points on <server>:
192.168.1.100:/share <-- <server> address
192.168.1.101:/share <-- iMac address
On the iMac:
% rpcinfo -t 192.168.1.100 nfs
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
program 100003 version 4 ready and waiting
% mount
trigger on /net/<server>/share (autofs, automounted, nobrowse)
% mount -t nfs 192.168.1.100:/share /Volumes/share1
mount_nfs: /Volumes/share1: Operation not permitted

My guess is that the Linux server is refusing NFS requests coming from a non-reserved (<1024) source port. If that's the case, adding "insecure" to the Linux export options should get it working. (Note: requiring the use of reserved ports doesn't actually make things any more secure on most networks, so the name of the option is a bit misleading.)
If you were previously able to mount that same export from a Mac, you must have been specifying the "-o resvport" option and doing the mounts as root (via sudo or automount which happens to run as root). So that may be another fix.
HTH
--macko

Expdp fails to create .dmp files in NFS mount point in solaris 10,Oracle10g

Dear folks,
I am facing a wierd issue while doing expdp with NFS mount point. Kindly help me on this.
===============
expdp system/manager directory=exp_dumps dumpfile=u2dw.dmp schemas=u2dw
Export: Release 10.2.0.4.0 - 64bit Production on Wednesday, 31 October, 2012 17:06:04
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31641: unable to create dump file "/backup_db/dumps/u2dw.dmp"
ORA-27040: file create error, unable to create file
SVR4 Error: 122: Operation not supported on transport endpoint
I have mounted like this:
mount -o hard,rw,noac,rsize=32768,wsize=32768,suid,proto=tcp,vers=3 -F nfs 172.20.2.204:/exthdd /backup_db
NFS=172.20.2.204:/exthdd
given read,write grants to public as well as specific user

782011 wrote:
Hi sb92075,
Thanks for ur reply. pls find the below. I am able to touch the files while exporting log files also creating having the error msg as i showed in previous post.
# su - oracle
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
You have new mail.
oracle 201> touch /backup_db/dumps/u2dw.dmp.test
oracle 202>I contend that Oracle is too dumb to lie & does not mis-report reality
27040, 00000, "file create error, unable to create file"
// *Cause: create system call returned an error, unable to create file
// *Action: verify filename, and permissions

How do you open an image in a new window at a larger size?

Yes I am new at this.
Basically all I'd like to do is have a thumbnail on a page as a button, click it so it opens in a new window at a zoomed larger size.
I know this is probably simple but I can't figure out how to do this.
Anybody have a second to point me in the right direction?
I would appreciate it.

It sounds like you want to create a button hot spot. See this article:
https://blogs.adobe.com/indesigndocs/2010/12/hot-spot-button-workaround-for-indesign-dig-p ubs.html
You might also want to download the free DPS Tips app for an example of this and other DPS effects.

How can I make this desktop dialogue box default on a larger size?

When I do a "save as" with a document, the dialogue box is so small I have to scroll to reach the folder I want it in. Then I have to drag the corner to make it larger.
Is there a way to make this box default on a larger size so I can see more file choices? see pic

Hold down option as you resize the window.

Anyone else having problems with NFS mounts not showing up?

Since Lion, cannot see NFS shares anymore. Folder that had them is still threre but the share will not mount. Worked fine in 10.6.
nfs://192.168.1.234/volume1/video
/Volumes/DiskStation/video
resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=3276
Any ideas?
Thanks

Since the NFS points show up in the terminal app, go to the local mount directory (i.e. the mount location in the NFS Mounts using Disk Utility) and do the following:
First Create a Link file
sudo ln -s full_local_path link_path_name
sudo ln -s /Volumes/linux/projects/ linuxProjects
Next Create a new directory say in the Root of the Host Drive (i.e. Macintosh HDD)
sudo mkdir new_link_storage_directory
sudo mkdir /Volumes/Macintosh\ HDD/Links
Copy the Above Link file to the new directory
sudo mv link_path_name new_link_storage_directory
sudo mv linuxProjects /Volumes/Macintosh\ HDD/Links/
Then in Finder locate the NEW_LINK_STORAGE_DIRECTORY and then the link file should allow opening of these NFS point points.
Finally, after all links have been created and placed into the NEW..DIRECTORY, Place it into the left sidebar. Now it works just like before.

Is there a way to make the view window on mail display messages with a larger size ?

I would like to set it up as a default, and not have to zoom in or make larger (cmd +) each individual message.
I have tried the font setup, but it does not work. It works for my own messages only.
I guess what I'm asking is if the font-setup of the sender of the mail can be overidden.

~Bee: I think you meant to say Mail's preferences.
I tried to do the same myself with the Fonts in Mail. Problem is it only enlarges part of messages for the most part. I could not get a good balance that way with some text enlarging while some stays small.
Using the cmd+ keys to zoom brings everything in the message to a larger size which is much better. Yes it's a pain, but I haven't found a better alternative yet.
Also, ctrl-mouse zoom works also, but not as crisp text. Wish the mouse tap zoom would work in mail, but it doesn't.
It would be a nice addition if apple would just include a zoom setting for all screens including Safari.
But as Bee suggested, increasing the font size does help depending on what is sent to you.

Large-size NFS mounts

Similar Messages

Maybe you are looking for