On Oct 09 16:18:33, [email protected] wrote:
> I have run into an odd problem. Machine A is running a model that writes
> files periodically to a file system NFS mounted from machine B. Machine B
> backs up this file system periodically to machine C via rsync. If this
> backup runs while machine A is writing a file, the model on A crashes.
Crashes how? What happens?
> The model is written in Go.
>
> I recently updated the disk containing this file system on machine B to an
> 8 TB disk from a 2 TB disk. The problem didn't occur with the 2 TB disk.
> I believe that this disk used FFS-1 while the new disk uses FFS-2.
>
> Any ideas on this? I haven't tried digging into the Go write code yet.
That's what I would suspect first.
You can make a simple test: 'touch /data.gy/path/to/file' on machine A
(thus making a write) while the backup is running on machine B.
Jan
> Here is the fstab entry on machine B:
> 6a99351289f050d4.a /data.gy ffs rw,nodev,nosuid 1 2
>
> Here is the rsync command updating from B to C:
> /usr/local/bin/rsync -avxl --delete /data.gy/ gryphon:/data.gy
>
> Here is the fstab entry on machine A:
> loro:/data.gy /data.gy nfs rw,nodev,nosuid,noatime 0 0
>
> Here is the entry in the exports file on machine B (the problem occurs for
> A equal to all of gy01 to gy08):
> /data.gy me merlin gy01 gy02 gy03 gy04 gy05 gy06 gy07 gy08
>
> Are there any other diagnostics that would be useful?
>
> Dave Raymond
>
>
> David J. Raymond
> [email protected]
> http://kestrel.nmt.edu/~raymond
