- Code: Select all
[root@localhost system]#cd /mnt/NAS/back/backup0/etc/systemd/system
[root@localhost system]# cp -l dbus-org.bluez.service /mnt/NAS/back/backup1/etc/systemd/system/
cp: cannot create hard link â/mnt/NAS/back/backup1/etc/systemd/system/dbus-org.bluez.serviceâ to âdbus-org.bluez.serviceâ: Unknown error 524
For reference, when this same command is executed on a locally mounted drive or on an iscsi share, it works properly.
The workstation executing the copy and the NAS with the share are separated by a Netgear router running DD-WRT with packets forwarded to/from the two subnets using iptables rules (no NAT). The workstation is on the WAN side of the router; the NAS is on the LAN side. I doubt this is relevant but provide the information in the interests of completeness.
The settings for the NFS share in fstab are these:
- Code: Select all
# Entry for NAS backup directory
192.168.0.27:/mnt/VD01/Sharon /mnt/NAS nfs rsize=32768,wsize=32768,soft,nosuid,noacl,auto,nofail 0 0
I gave some thought to removing the NFS mount and replacing it with an iscsi share for this purpose, but decided not to because of who the user of the workstation is. She's clueless, and is prone to punching the reset button when something goes wrong. Iscsi binds the workstation and the NAS very tightly, and my experience is that often my NAS will get a corrupted filesystem when reset on the workstation is punched; dismounting cleanly is very important. And, in fact, one of the virtual machines on that workstation IS causing some trouble, locking up the Mageia 4 host from time to time. Until I figure that out, the reset button will be getting punched occcasionally; no avoiding it.
So iscsi is out.
Anyone know how to get this to behave correctly?