7:47 p.m.
Hi All,
I am using nfs-ganesha 2.6.3. I am dumping Netezza to a Linux machine running nfs-ganesha.
Netezza writes data in 1MB chunks. After each write it checks size of file. After dumping
some data it failed saying that expected size is 106MB. But the file size is 104MB.
Nfs-Ganesha debug logs indicated that one of the workers processed a getattr RPC (supposed
to have been sent after writing 104MB) after receiving write RPC for 106MB but before it
was written to disk.
Is this valid behavior from nfs-ganesha? Are there any settings (on nfs-client or on
nfs-ganesha) to make sure operations on a given file are processed in the order they are
received?
I have seen another weird problem. I have not got a chance to check logs for it yet. My
application creates a temp file, writes small data (10K) to it, closes the file and then
renames it. This rename failed with ENOEXIST. I see that temp file is indeed present.
Based on my observation with Netezza I am suspecting that that rename was processed before
the temp file create RPC was processed. Could that be possible?
--Satish
--Satish