You are not logged in.
My NFS server started to behave strangely today. It's been a long time since I used it last time, so I don't know what doesn't work anymore; but it used to work. I set the server up following the wiki guidelines. The server startup procedure gives me this warning:
:: Starting rpcbind [DONE]
:: Starting rpc.statd daemon [DONE]
:: Mounting pipefs filesystem [BUSY]
:: Starting rpc.idmapd daemon [DONE]
:: Mounting nfsd filesystem [DONE]
:: Exporting all directories [BUSY]
exportfs: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export "192.168.0.2/4:/media/disks/sATA-a".
Assuming default behaviour ('no_subtree_check').
NOTE: this default has changed since nfs-utils version 1.0.x
exportfs: Warning: /media/disks/sATA-a does not support NFS export.
[DONE]
:: Starting rpc.nfsd daemon [BUSY]
rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused)
rpc.nfsd: unable to set any sockets for nfsd
[FAIL] The nfs partition I'm trying to share is /media/disks/sATA-a, which seems to not support NFS export. Googling around for this issue, I found this thread on the Ubuntu forum:
http://ubuntuforums.org/showthread.php?t=597298
It's a bit outdated, but there the problem is linked to FUSE filesystems. I don't know how it translates to Arch kernel, nor if it is the actual issue. I'm only sure that it worked before with stock packages (kernel, rpcbind, nfs-utils, ntfs-3g) from Arch repo and no particular tweak.
Thanks everybody.
Last edited by snack (2010-12-28 16:51:31)
Offline