Can't mount NFS exports on Arch laptop

I've browsed the forums, double checked the wiki, but for some reason I'm not able to mount my NFS exports. There must be some small issue not letting me do this, but I can't find it. This is my /etc/exports file on the server (desktop):
/glados 192.168.0.99(rw,fsid=0,no_subtree_check)
/glados/movies 192.168.0.99(rw,no_subtree_check)
And the order of the rc.conf daemons on the server:
DAEMONS=(syslog-ng dbus network @netfs crond rpcbind nfs-common nfs-server !hwclock ntpd)
On the client (laptop):
DAEMONS=(syslog-ng dbus network crond @bumblebeed @networkmanager @postgresql rpcbind nfs-common nfs-server sshd)
$ showmount -e 192.168.1.101
Export list for 192.168.1.101:
/glados/movies 192.168.0.99
/glados 192.168.0.99
Now try mount:
$ sudo mount -t nfs4 192.168.1.101:/movies server/
Here it just freezes and nothing happens. I also did the configuration both on server and client side of /etc/idmapd.conf, adding a domain.
Nothing happens on the client side when I try to mount. It just freezes there. Both machines running up to date ArchLinux.
Any help is appreciated!
Last edited by fbt (2012-09-18 03:47:46)

I just thought that server/ was a typo
He's able to use showmount -e 192.168.1.101 from the machine with the ip 192.168.0.99 so assumed his network's functioning ok ... but you know what they say about 'assume', which machine did you actually run the showmount command on? This might be stating the obvious, but if you ran it on 192.168.0.101 make sure 192.168.0.99 and 192.168.1.101 are communicating with each other
Also I think you're not mounting the path correctly, you have movies exported as:
/glados/movies 192.168.0.99(rw,no_subtree_check)
But you're trying to mount it as:
sudo mount -t nfs4 192.168.1.101:/movies server/
Try mounting it something like this:
sudo mount -t nfs4 192.168.1.101:/glados/movies /server/movies
That command is assuming you're wanting to put your nfs shares inside a folder called /server, also be aware that the directory you're trying to mount your shares inside of has to already exist
Incidentally, why are you mounting /glados and then also mounting directories unger /glados such as /glados/movies, by mounting /glados as an nfs share you already have access to /glados/movies. Once /glados is mounted then you can symlink to or bind mount any directories under it to any location you want

Similar Messages

Can't mount NFS from my Arch laptop, am I missing something obvious?

Hello,
I have been trying to solve this issue for over a week and tried everything that I can imagine with no luck...
Set up:
- Qnap SS-839 Pro with several NFS shares on
/share/to_sort
/share/movies
/share/music
etc.
- MythTV frontend/backend running Mythbuntu.
I can mount my NFS shares without problem. I use this fstab.
192.168.1.100:/share/Music /var/lib/mythtv/music nfs nolock,async,proto=tcp,rw,ac 0 0
192.168.1.100:/share/Videos /var/lib/mythtv/videos nfs nolock,async,proto=tcp,rw,ac 0 0
- Arch laptop
I can't get to mount any of the NFS share:
[18:59:14][[email protected]]
/mnt/aether Arch64# /etc/rc.d/rpcbind restart
:: Stopping rpcbind [DONE]
:: Starting rpcbind [DONE]
[18:59:32][[email protected]]
/mnt/aether Arch64# mount 192.168.1.100:/share/to_sort/ to_sort/
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
[19:00:03][[email protected]]
/mnt/aether Arch64# mount 192.168.1.100:/share/to_sort/ to_sort/ -o no-lock
mount.nfs: an incorrect mount option was specified
I tried using the 2 following lines in my fstab on my laptop but nothing works:
1) 192.168.1.100:/share/to_sort /mnt/aether/to_sort nfs nolock,async,proto=tcp,rw,ac 0 0 (same option than under mythbuntu)
2) 192.168.1.100:/share/to_sort /mnt/aether/to_sort nfs defaults 0 0
I'm no guru when it comes to nfs sharing etc, but I really can't see what I am missing here, nor whatelse can I try!
Any idea will be more than welcome!
Thanks in advance
Ludo

I finally solved this problem after 4 months after someone posted a similar issue with Arch few days ago...
He said to install the iana-etc package... I already had the package but still gave it a go:
[08:15:33][[email protected]]
~ Arch64$ showmount -e 192.168.0.100
clnt_create: RPC: Unknown host
[08:15:41][[email protected]]
~ Arch64$ sudo pacman -Syu iana-etc
Password:
:: Synchronising package databases...
core is up to date
extra is up to date
community is up to date
archlinuxfr is up to date
warning: iana-etc-2.30-1 is up to date -- reinstalling
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
Targets (1): iana-etc-2.30-1
Total Download Size: 0.00 MB
Total Installed Size: 0.88 MB
Proceed with installation? [Y/n]
(1/1) checking package integrity [########################################################################################################################] 100%
(1/1) checking for file conflicts [########################################################################################################################] 100%
(1/1) upgrading iana-etc [########################################################################################################################] 100%
[08:20:13][[email protected]]
~ Arch64$ showmount -e 192.168.0.100
Export list for 192.168.0.100:
/to_sort
/mythbox
/Qweb
/Qusb
/Documents
[08:20:18][[email protected]]
~ Arch64$
As you can see, it is now working and I am now completely puzzled...
How come reinstalling this package solved the issue?
Any idea on what the problem was would be more than welcome
Thanks

Can not mount nfs shares

I have a centos server which tries to mount a nfs share from an osx server tiger.
on the osx server showmount -e shows me the mountpoint perfectly.
on the linux server i try to mount the mountpoint and after some time it gives me the error:
mount.nfs: Input/output error
does this sound familiar to anyone? please help me :P

more information:
nidump -r /exports .
"name" = ( "exports" );
CHILDREN = (
"clients" = ( "192.168.0.10" );
"name" = ( "/backup" );
"opts" = ( "" );
showmount -a returns:
Exports list on localhost:
/backup 192.168.0.10

[SOLVED]Can´t mount nfs shares!

Hello,
I am trying to get up a fileserver. I installed an old PC with Arch and configerd it over SSH. I followed the wiki over NFS and NFSv4. But everytime I want to mount a share that is in the physical map /home/jozef/shares/downloads, I get the following error:
mount.nfs4: timeout set for Mon Aug 24 14:36:57 2009
mount.nfs4: text-based options: 'clientaddr=192.168.0.100,addr=192.168.0.111'
mount.nfs4: mount(2): Permission denied mount.nfs4: access denied by server while mounting 192.168.0.111:/shares/downloads
I tried to mount it with the following command:
mount -v -t nfs4 192.168.0.111:/shares/downloads /media/Downloads-Server
Lets call the fileserver fileserver and my workstation Gamepc. Here I will give you some files that I think are needed, from fileserver and Gamepc are there other files you need, I will post them.
/etc/exports on fileserver
# /etc/exports
# List of directories exported to NFS clients. See exports(5).
# Use exportfs -arv to reread.
# Example for NFSv2 and NFSv3:
# /srv/home hostname1(rw,sync) hostname2(ro,sync)
# Example for NFSv4:
# /srv/nfs4 hostname1(rw,sync,fsid=0)
# /srv/nfs4/home hostname1(rw,sync,nohide)
# Using Kerberos and integrity checking:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/home gss/krb5i(rw,sync,nohide)
/shares 192.168.0.12(rw,fsid=0,no_subtree_check,async,no_root_squash)
/shares/downloads 192.168.0.12(rw,no_subtree_check,async,no_root_squash,nohide)
/etc/hosts.allow on fileserver
# /etc/hosts.allow
sshd: 192.168.0.0/255.255.255.0
#nfsd: 192.168.0.0/255.255.255.255
#portmap: 192.168.0.0/255.255.255.255
#mountd: 192.168.0.0/255.255.255.255
nfsd: ALL
portmap: ALL
mountd: ALL
# End of file
/etc/hosts.deny on fileserver
# /etc/hosts.deny
ALL: ALL: DENY
# End of file
/etc/conf.d/nfs-common on fileserver
STATD_OPTS="--no-notify"
/etc/conf.d/nfs-server on fileserver
STATD_OPTS="--no-notify"
/etc/rc.conf on fileserver
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK=""
USEDIRECTISA="no"
TIMEZONE=""
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="myhost"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="dhcp"
eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !network rpcbind nfs-common nfs-server netfs crond !xinetd !samba sshd transmissiond)
/etc/rc.conf on Gamepc
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Europe/Amsterdam"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="GAMEPC"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="dhcp"
eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !network rpcbind nfs-common @netfs crond @hal @fam @samba @alsa @cups)
/etc/hosts.allow on Gamepc
# /etc/hosts.allow
sshd:ALL
# End of file
/etc/hosts.deny on Gamepc
# /etc/hosts.deny
ALL: ALL: DENY
# End of file
If someone could help me, I would be pleased.
With kind regards,
Jozef00
Last edited by jozef00 (2009-09-01 15:28:07)

Are you sure that the nfs module is loaded? Do
lsmod | grep nfs
to check. If "nfs" doesn't appear then that's your problem. Do:
sudo modprobe nfs
and continue.
EDIT: Also, I'll assume both your server and your client machine are connected to the network. You have the network DAEMON "!"-disabled in each machine's /etc/rc.conf. So I'm assuming you're connecting them to the network in some other way, and have verified that you can, for example, ssh from one machine to the other.
Third, you're sure that /share exists on your server machine, that a (presumably empty) directory /share/downloads exists inside it, that another folder is mounted on top of that empty directory? When you type "mount" on the server machine there should be a line containing "on /share/downloads".
Fourth, if your client's ip address is 192.168.0.100 (this will be displayed when you do "ifconfig") then the /etc/exports on your server has been changed to read:
/shares 192.168.0.100(rw,fsid=0,no_subtree_check,async,no_root_squash)
/shares/downloads 192.168.0.100(rw,no_subtree_check,async,no_root_squash,nohide)
Then you either typed "exportfs -rf" on the server, or stopped and restarted nfs-server. (I'd stop nfs-server, nfs-common, and rpcbind, then start them up again in reverse order, to be sure.)
STATD_OPTS has no effect in /etc/conf.d/nfs-server. Also, you don't need to use statd if you're using nfs4. So you could change /etc/conf.d/nfs-common to read:
NEED_STATD=no
NEED_IDMAPD=yes
and /etc/conf.d/server and can be blank.
(Then restart everything, as described above.)
If you're using the latest arch packages then portmap has been replaced by rpcbind (which you do have in your DAEMONS line on the server). So you need to change the "portmap:" line in your server's /etc/hosts.allow to "rpcbind:". I also have a "lockd:" line in my /etc/hosts.allow, in addition to what you have. It's probably not the source of your present troubles, and I'm not sure it's necessary. But you could try adding it.
Finally, did you add/change a "Domain = ..." line in the /etc/idmapd.conf on your server, and a corrsponding line in the /etc/idmapd.conf on your client?
Last edited by Profjim (2009-08-25 12:51:48)

Can't mount NFS share via GUI

Mac OS X 10.8.2
MacBookPro5,3
Hello,
I've recently upgraded to OS X 10.8.2 and am having great difficulty in mounting my NFS shares via the OSX GUI. This worked fine at OS X 10.6.
My aim is to provide an automount type of setup so that less experienced users don't have to worry about the command line.
Can someone please point me in the right direction here?
This is what I've tried to date.
My NFS service is hosted on my Debian server. It supports NFS v4. The service is working and stable and is used routinely with Ubuntu clients. It has also worked with OS X 10.6 clients in the past, but not with OS X 10.7 clients.
To date I have tried the following options:
Mount via finder: Connect to server option using syntax: nfs://<user>@<server>/<share>
setting up autofs using the instructions from pmbuko
using the command line to mount the share.
The first option failed repeatedly. I did find that it would eventually work, though only after I'd manually mounted the share at the command line.
I have not been able to get the second option to work.
I initiate autofs using the command 'automount -vc' and see that the connection is recognised
when I attempt to cd into a directory below the mount point, I eventually get the message 'Connection Refused'.
when I check my Debian logs, I find that the NFS service had actually received an authenticated mount request from the Mac.
when I check my Mac Console logs, I see an error:kernel: nfs_connect: socket error 61 for <server>/<share>
I was able to get the third option working, but only after using the '-o resvport' option.
'Something' does appear to be broken with OS X 10.8.2 as an NFS client.
Any thoughts?

I have found a work around that meets my imediate needs, though it doesn't allow me to use autofs functionality.
The work around uses the traditional Unix/Linux approach of automatically mounting a file system or NFS share via fstab at boot time. OS X 10.8 still supports fstab, even though the file is not included in the default installation.
Once mounted, the NFS share appears as if it is part of the normal file system.
The following is only intended for people confident in Unix or Linux systems administration and in using a shell environment via the command line. Do not attempt this if you do not have these skills.
To set up for fstab, do the following within a terminal session:
create an empty directory in your file system that you can use as your mount point for your NFS share:
sudo mkdir /data/share
sudo chown root:wheel /data/share
using your favourite editor, create the fstab file (in a terminal type 'man fstab' for details)
sudo vi /etc/fstab
add similar to the following to /etc/fstab and then save and exit, substituting your own values where appropriate
# My NFS share
<your-server>:/<your-share> /data/share nfs resvport,rw,hard,intr 0 0
sudo chown root:wheel /etc/fstab
Please note: you may not need the resvport option in the fstab line above. It will depend on your NFS server's requirements.
Once you have done this, reboot your Mac and your NFS share should be mounted at the mount point that you defined.
If not, check your logs to see what went wrong.

How can a mount a NFS share exported from OpenBSD?

Hello Apple Discussions:
I've been experimenting with NFS in a mixed OS environment, and have been successful exporting nfs share with tigerserver, and mounting it on both a powerpc linux system, and on a powerpc openBSD system.
Likewise, I can export a NFS share from the linux powerpc box, and mount it on the openBSD box and on the tigerserver, although, the latter required using the options (ro,sync,insecure) in my exports file.
However, when I export a share on the OpenBSD box, I can mount it on the linux box, but not on tigerserver.
I would like for the OpenBSD box to export a NFS share securely, with read-write permissions, to the tigerserver.
After reading so many tutorials, that it would be a page of links, just to list them all, I am pulling my hair out. However, I have found one thread that suggests, that perhaps what I'm trying to do is impossible:
http://www.bsdforums.org/forums/showthread.php?t=54308
Here it is suggested that the NFS won't work because tigerserver is not using UTF-8?
I will have to say, that I was somewhat alarmed, that the only times I succeeded in mounting an nfs share exported from linux onto tigerserver, it was when the "insecure" option is used in the /etc/exports file. There doesn't seem to be an equivalent for the linux style exports option "insecure", in the bsd style options of --maproot=user:group1:group2.
But I don't like using any options that say "insecure" anyways, so rather than trying to find out how to make openbsd "insecure", I would rather like to find out if there is a way to get tigerserver using UTF-8, at least when mounting NFS shares, if this is indeed the issue.
Here are the more technical details. I've created a user on all sytems named "fives" with the userid of 5555 and the groupid of 5555. I made the user local user in the local net info domain, but I've tried it with an LDAP user as well. The folders I wish to export and the folders into which to mount them are all owned by user fives and group fives, and have permissions set to 0775. The ip addresses are OpenBSD=192.168.222.111 TigerServer=192.168.222.233 LinuxPPC=192.168.222.253. I've included the relevant NFS setup files and running processes below:
ON THE OPENBSD BOX:
#/etc/exports
/fives -alldirs -network=192.168.222.0 -mask=255.255.255.0
/exports/fives -mapall=fives:fives 192.168.222.233 192.168.222.253
#/etc/hosts.deny
ALL: ALL
#/etc/hosts.allow
ALL: 192.168.222.233 192.168.222.253
#/etc/rc.conf.local
portmap=YES
lockd=YES
nfs_server=YES
#here's proof that the daemons are running on the OpenBSD box;
rpcinfo -p localhost
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100005 1 udp 863 mountd
100005 3 udp 863 mountd
100005 1 tcp 613 mountd
100005 3 tcp 613 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100021 1 udp 895 nlockmgr
100021 3 udp 895 nlockmgr
100021 1 tcp 706 nlockmgr
100021 3 tcp 706 nlockmgr
# actually, I don't see statd, but haven't found the equivalent in openbsd. There's rpc.rstatd, and maybe it should be listed here, but there doesn't seem to be a way to launch it directly. This is a competitor with the UTF-8 theory about why it's not working.
ON THE TIGER SERVER:
# here's proof that tiger server sees the mounts:
showmount -e 192.168.222.111
Exports list on 192.168.222.111:
/fives 192.168.222.0
/exports/fives 192.168.222.233 192.168.222.253
# here's the result of user fives' attempt at mounting a share:
sudo mount -t nfs 192.168.222.111:/exports/fives /imports/fives
mount_nfs: /imports/fives: Permission denied
# yet user fives has no problem mounting same share on linuxppc box.
What is different about OSX server? I thought it was supposed to speak NFS?
---argh... I'm steppin out for a pint.. Hopefully when I'm back it'll just work.

One thing not mentioned is that if you decide on the multiple user approach, you can have your music folder in Shared Documents so you only store the tracks once.
Each user is free to choose which of those tracks they want in their library.
There is an Apple help article on multiple users.
http://docs.info.apple.com/article.html?artnum=300432

Can't mount Archlinux NFS-Server via Win 7

Dear Forum,
first of all: I'm neither a native english speaker nor do i have any experience in the field of linux etc.
Therefore please excuse typing errors and unclear sentences. I read a lot of manpages and webforums but can't get the solution to my problem.
I bought a pogoplug classic (Version E-02) to use it as a linux-based webserver. I installed Arch Linux, updated all the packages and tried to get NFS to work (i followed these steps: https://wiki.archlinux.org/index.php/NFS )
My desktop machine runs a win 7 x64 and i connect to my pogoplug via putty/ssh.
Shortcut to my problem:
I can't connect to my NFS server, everytime i try do so, i just get a page that looks like kind of a small manpage for the syntax of the "mount" command. Is my syntax wrong or did i miss something essential?
What i did in particular:
- Installed nfs-utils via pacman
- idmapd.conf:
[General]
Verbosity = 1
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
Domain = localdomain
[Mapping]
Nobody-User = nobody
Nobody-Group = nobody
- /etc/exports
/srv/nfs4/ *(rw,fsid=0,no_subtree_check)
/srv/nfs4/tausch *(rw,no_subtree_check,async,insecure,nohide)
I also created /mnt/tausch/
- /etc/fstab/
/mnt/tausch /srv/nfs4/tausch none bind 0 0
- "showmount -e alarm" gives me this:
/srv/nfs4/tausch *
/srv/nfs4 *
I can get this message via cmd.exe from my windows machine - does this mean, my nfs server is running correctly?
- Activated NFS client in win 7
- After the succesfull "showmount" i did this:
mount -t nfs4 -o alarm:/mnt/tausch /srv/nfs4/tausch
Thats where i am right now. Any hint would be appreciated!
Merry christmas to all of you,
greetings,
nick

As far as I know you have to have a NFS connector on the Win7 machine for it to use NFS. It is not a native function of Windows to have NFS.
I think you are mounting /mnt/tausch from host alarm and mounting it to your /srv/nfs4/tausch on another machine (win7?).
It otherwise looks like you are mounting /mnt/tausch to /srv/nfs4/tausch on your ArchLinux machine, and then trying to export it from double mounting to the win7 machine. I don't know why you wouldn't just use the export from alarm and mount it to your win7 machine. Mounting an export from another machine and then exporting that to another machine, unless you transpose it will not show the other export.

[solved] mounted NFS shows nobody:nobody

I followed the wiki and found a thread that mentioned using the fsid=0 option in exports file but its not working for me.
I enabled rpc-idmapd on the client (Arch), its running I checked with systemctl status rpc-idmapd. The server is running Debian Wheezy with ZFS volumes mounted and exported as legacy, I placed 'NEED_IDMAPD=YES' in /etc/default/nfs-common and, when that didn't work, in /etc/default/nfs-kernel-server too. I restart nfs-kernel-server after changes and remount the shares on the client.
When that didn't work I exported the shares with 'fsid=0', but then I can't even enter the share, I get 'device does not exist' (IIRC, that was yesterday and can't find the literal message in the logs anymore).
Anyway, this worked fine when my client was running Wheezy and it still works fine for other clients so my guess is I got something wrong on my Arch system.
I'd appreciate some help getting this to work properly.
Thanks in advance!
Last edited by mouseman (2014-04-26 09:03:28)

I know that, it doesn't negate the fact that Debian has that comment that made me believe it wasn't necessary if the domain is the same on all hosts. It worked when I was running Debian on both the client and server, but with Arch apparently I need to specifically set it.
I edited the wiki to reflect this (my first edit ), hope I did oke there.

Netboot with NFS - export what/where?

Hello, Arch noob and first post here. Let me first express appreciation for the wiki, whose articles have helped me several times already outside of Arch. Great job!
Now then - I'm trying to add Arch's live netboot into my current setup (based on Fog's menu system) and after reading through several wiki articles, I'm at the point where I load the relevant parts of arch.cfg syslinux config (contained on the iso, so cannot modify), which download kernel image and initrd, and start booting the system. I haven't configured the nfs export yet as it's not clear to me where arch expects it to be:
The Diskless System article suggests /srv/arch, but doesn't mention WHAT should be in it.
The PXE article suggests /mnt/archiso - this shouild work on my system without further configuration, as I export entire /mnt with crossmnt option to satisfy all the ubuntu netboots.
When I actually boot the system, it appears to want to mount $SERVER/run/archiso/bootmnt. Searching for this path yields some patches on a mailing list, but no documentation.
If the /run/... path is the right one, can anyone tell me what should be there, and preferably, how to automatically prepare that path on bootup, since /run is a tmpfs mount?

myxal wrote:
Right - by live netboot, I mean a network-based equivalent of a LiveCD - a means to test-drive/install a new release on a clean-slate, and as a recovery tool when GRUB on the disk dies for whatever reason.
I've actually seen that article too, and have 2 issues with it:
It's implied that servers on the internet are used to download the live system during boot. I'd rather avoid this and just use locally-shared files, which would obviously download much faster.
It doesn't work, at least not without further prerequisites, which are missing from the article - the boot fails after a short while with "Could not find kernel image: menu.c32" - which is ridiculous, as that is definitely available over TFTP. Looking through the tftp logs, there appears no "file not found" error
Arch Diskless expert here.
I would just go with the Diskless - NFS article. The path doesn't exactly matter, but /srv/tftp/archxx is a good start in case you have some other PXE installations. Install a PXE installation on your already installed Arch system. If the architecture is the same as the host for the client, you can just point your pacman to your PXE installation directory.
In /etc/fstab export your /srv/tftp/archxx directory, but when tftp serves the file it will come from /srv/tftp. You may want a separate partition for your PXE installation.
Diskless doesn't care whether you are trying to install a live diskless client or an install system. I prefer to have a live diskless system, since you basically use a live running system and the same steps to install PXE as you do a new client. Just point pacman to your installation directory and away you go.
menu.c32 comes from your syslinux directory under /usr/lib/syslinux/ and copy it into your /boot/grub /boot/syslinux directory. You will need pxelinux.0 in /srv/tftp and a directory pxelinux.cfg will syslinux style configuration files will default for any clients, or MAC address specific.
You will need a PXE ROM or iPXE to boot from the PXE server.
Last edited by nomorewindows (2013-08-08 16:48:20)

NFS exports and the mandatory no_root_squash

We are running a SUSE11/OES11 cluster serving NSS volumes as NCP, NFS and AFP. Is the only feasible workaround for the NFS no_root_squash requirement to firewall the mountd port?
If so will having a list of 1,000+ IP numbers in the allow list for mountd have a significant impact on the cluster nodes? Unfortunately on our University class B IPv4 site the allocated IP addresses are scattered and the subset of PCs controlled by technicians (and therefore 'trusted') are not contiguous and neatly arranged.

There is another workaround to the "no_root_squash" requirement. The below is taken from TID: Support | OES: Compatibility issues between NSS and NFS
2. no_root_squash: Officially, this is mandatory, so care should be taken to limit what hosts can mount the export (as the root user of the NFS client host will be able to act as the root user on the NSS exported path).
However, due to potential security concerns with allowing root access, some administrators chose to set this up in another way. This alternative way is thus far considered experimental, and not thoroughly tested: It seems that the key requirement here is that the user who is requesting the mount (typically root) have at least Filescan rights to the NSS volume. If root is "squashed" he is treated like "nobody." Typically, "nobody" does not have access, neither through its own merits nor by being associated with any LUM-enabled user in eDir. However, an eDir user can be created and LUM-enabled, given Filescan right to the NSS volume(s), and then the UID assigned to that user can be used as the "anonuid" for that particular export. So, for example, if the user in question was given UID 1011, then instead of "no_root_squash" the combination of "root_squash,anonuid=1011" could be used.
In that case, be sure to remember that even after mount, "squashed root user" will be treated as having whatever rights the anonuid user has been given. Also remember that if you use the "all_squash" parameter as well, all NFS client users (not just eDir users and not just root) will be treated as the anonuid user, and will be able to access the NSS volume.
On the other subject: I do not know the potential impact of 1000+ IP numbers in an allow list for mountd.
Darcy

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!!!

KDE's Dolphin can't mount NTFS partitions after upgrade to systemd

Hi, I just finished to migrate my system to a pure systemd setup. Everithing seems to work fine, except that Dolphin can't mount NTFS partitions anymore, as it was able to do before. I'm not 100% sure that systemd is the culprit, but nevertheless it is a big change in my system so I assume that it may be the problem.
Trying to mount with Dolphin I get this error message:
An error occurred while accessing 'sATA-a', the system responded: The requested operation has failed.: Error mounting: mount exited with exit code 1: helper failed with:
Error opening '/dev/sdb1': Permesso negato
Failed to mount '/dev/sdb1': Permesso negato
Please check '/dev/sdb1' and the ntfs-3g binary permissions,
and the mounting user ID. More explanation is provided at
http://tuxera.com/community/ntfs-3g-faq/#unprivileged
I used to get this kind of error aeons ago when trying to mount from CL; puzzling enough, mounting from CL now works:
$ mount /media/disks/sATA-a
$ ls /media/disks/sATA-a
Documenti Download $RECYCLE.BIN RECYCLER sATA-b System Volume Information Temp Video
This is the relevant entry in my fstab (I don't know if Dolphin cares about it...):
#sATA-a
UUID=D6789B21789B0003 /media/disks/sATA-a ntfs-3g noauto,users 0 0
And finally:
$ ll `which ntfs-3g`
-rwsr-xr-x 1 root root 125K 21 apr 12.13 /bin/ntfs-3g
Can anybody give me a hint? Thanks.

OK, the mess is growing up. Today I switched my laptop to systemd, and the mount problem has appeared on this system as well. So I am confident that this is a systemd-related issue, and maybe some stock Arch config file is broken. I have this entry on my /etc/fstab for the ntfs-3g drive:
UUID=88705BA9705B9D2E /media/vista ntfs-3g noauto,users,exec 0 0
I compiled ntfs-3g with internal fuse support and did the setuid trick:
$ ls -l `which ntfs-3g`
-rwsr-xr-x 1 root root 125K 16 apr 2012 /bin/ntfs-3g
I can mount the disk using the command:
$ mount /media/vista/
$
It works flawlessly, so ntfs-3g works. If I try to mount it with udisks I get:
$ /usr/bin/udisks --mount /dev/sda2 --mount-options users,exec
Mount failed: Error mounting: mount exited with exit code 1: helper failed with:
Error opening '/dev/sda2': Permesso negato
Failed to mount '/dev/sda2': Permesso negato
Please check '/dev/sda2' and the ntfs-3g binary permissions,
and the mounting user ID. More explanation is provided at
http://tuxera.com/community/ntfs-3g-faq/#unprivileged
It sounds to me that udisks is trying to mount the disk as a different user, but I'm not an expert so I might be wrong. If I remove the entry in /etc/fstab then udisks will ask for the password. Repeating the same steps but for an ext3 partition, I am able to mount with udisks when there is a proper fstab entry, and I'm asked for a password when that entry is commented out.
Based on these findings, I strongly suspect that there is some problem with logind configuration in my system. I have been going round and round for hours, serching the web and the wiki (which BTW is in a very bad shape, containing outdated or no informations about mount policies in the polkit and udev sections), and now I feel I need some help to go through it... thanks.

SUN NAS 5310 NFS exporting problem

Dear Experts ,
I'me facing a strange problem with SUN NAS 5310 , a volume from this NAS is exported as NFS share with the options ( R/W Access , map root user to root user of a Unix machine and the hosts to be in a trusted group ) what is happening is when i mount this exported volume at a Unix machine it is mounded with permission 700 and the owner is root no other users can access it . i tried to change the permissions from the Unix machine but i couldn't and it gives me the message " chmod :WARNING: can't change ...." there is no way on the NAS to change this as i can see . i tried to export the folders under this volume and mounted it on Unix and it went fine , i tried with other volumes used for windows and they mounted normally !!!!, except for the mentioned volume refuse to change and mount normally ,
Any ideas will be appreciated
Thanks for you all
Regards, Amr.

Hi,
I've blogged some time ago about this: http://vnull.pcnet.com.pl/blog/?p=87 but in inter-VM communication scenario. This could be adapted to have physical ethernet in dom0 running also with 1GigE with MTU=9000.
Be sure to have NFS mounted as something like this: nointr,tcp,nfsvers=3,timeo=300,rsize=32768,wsize=32768
Another trick is to tune drivers setting, but this only works for high packet-per-seconds scenario (works great for e1000); Also you could try enabling all offload settings for driver (for both cases consult: man ethtool). If even that doesn't help to fully exploit storage performance, you could try dividing /OVS NFS mountpoint to several ones, based on performance charcteristics. If have 2 VMs that would mean for example three NFS mountpoints:
1) /OVS
2) /OVS/running_pool/01_vm1
3) /OVS/running_pool/02_vm2
This would exploit three TCP streams, but I'm not sure if it's supported. Also be sure to tune server NFS kernel threads (man nfsd -> rc.nfsd -> /etc/sysconfig/nfs -> RPCNFSDCOUNT="some_big_number").

Urgent: Oracle VM server reboot everytime write data to an NFS export

This is a weird thing:
simply describe the problem. I have created a server pool for holding just one server, not enabling cluster.
this server has 2 NIC. one is used for public connection, let's say port 1 for management network, heartbeat, etc...
the other is used to connect to a EMC NAS directly, let's say port2.
what I did is created a network which type is Virtualmachine and add the port2 to the network.
when I create virtual machine on the server, I added one VNIC for public network(10.*.*.*), and one VNIC for connecting to the NAS(192.168.4.*).
then I installed Oracle ENterprise Linux 5.x/6.x (I've tried both) and started up the two VNIC inside the guest successfully. mount NFS filesystem successfully.the fstab like below:
192.168.4.60:/datafs /u02 nfs rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,actimeo=0,vers=3,timeo=600 0 0
I can touch a empty file or delete file from the NFS mount point. BUT, when I open an empty file and modified a few lines, then tried to save it, the whole OVM server just reboot itself. NOT the VM, but the OVM server. I tried to copy files or dd files to the mount pont, always get the same result.
I really don't understand what's happening. the NFS exports should be fine. because when I tried to mount it to a VMware guest VM, read/write operations to the NFS mount point was just fine!
anyone has any advice on this or any comments are highly appreciated...

today I've got the culprit from the output screen of the server.
kernel BUG at drivers/net/bna/bnad.c:2102!
invalid opcode: 0000 [#1] SMP
kernel panic - not syncing: fatal exception interrupt
pid: 8160, comm: netback/1 Tainted: G D 2.6.32.21-45xen #1
any idea on this? should I go to Oracle Support directly? when I tried to log a SR, I cannot find the OVM in the product category list... does it mean that we don't have Oracle VM support?

I installed firefox on a new Win 8 laptop, and my account can not sync with my Win 7 laptop.

I recently purchased a new Win 8 laptop. When I installed firefox and go to sync in option, it doesn't give me the old 4x3 box with code. When I entered my email, it couldn't find my account either.
I am not sure where is the problem, because my old Win 7 laptop and HTC One X are both synced, when I could use the 4x3 box. The Win 7 firefox and Win 8 firefox are both ver 29.0.1, but the sync tab in option looks different.
In summary, I have two problems
1) My old laptop has a sync account set up long ago, but not firefox is not recognizing my account by my email.
2) My new laptop doesn't give me the 4x3 sync code.
3) Just for safety, is there a way to export all of my firefox setting and bookmark from my win 7 laptop? This way I can have the files for backup, in case my sync account is corruptedd or something, and maybe I can import the files to the new laptop this way.
Please let me know if there are solutions to these problem. Thanks!

Hi joey0352,
Yes check out the article about Firefox profiles:[[Back up and restore information in Firefox profiles]]
The profile folder will have all of the information stored in it on your Windows 7 computer. If you have any questions about moving the file we are happy to post back.

Can't mount NFS exports on Arch laptop

Similar Messages

Maybe you are looking for