[2010-11-24 22:05:35] Version [1.6.3.8] ArchiveRecording: fsync() returned 1
[2010-11-24 22:05:49] Version [1.6.3.8]Error mounting NFS archive drive
(172.25.133.53:/arc): Broken pipe OR Unknown device
---------------------- CRITICAL ERRORS END HERE ----------------------
Solution
- "fsync" errors usually indicate file system corruption or damaged hard drives.
The "write" function succeeds, and we then use "fsync" to force the file to
be written to disk, and that's when the NFS server discovers it can't actually
write the data to disk, and we get an error.
If it's a Windows-based NFS server:
You will probably find errors in the Windows Event Viewer, under System.
Do a filesystem check and disk check (chkdsk /f /r) on the NFS system.
If it's a Unix-based NFS server:
You will probably find errors in the system logs (/var/log/syslog or /var/log/messages).
You should do a filesystem check (fsck) and also a disk check (badblocks).
You may want to back up the NFS before doing the checks.