Skip to contentSkip to conversation

2.6.23.9 NFS Invalid argument in fopen("something","w")

DISCUSSION Gianluca Alberici 1 participant 1 message Dec 14, 2007

lore
Share & tools
lore
#0 lore raw

Hi,

I've run into this problem on a 'localhost:' NFS mount on a 2.6.23.9: The fopen syscall will return "Invalid argument" trying to fopen in "w" mode an existing file. The same file can be opened for append or removed.

The evidence is for example:

mars:~# mount localhost:/opt/nfs/ /mnt/tmp
mars:~# echo "Hello" > /mnt/tmp/test-file
mars:~# echo "Hello" > /mnt/tmp/test-file
bash: /mnt/tmp/test-file: Invalid argument
mars:~# echo "Hello" > /mnt/tmp/test-file
bash: /mnt/tmp/test-file: Invalid argument
mars:~# echo "Hello" > /mnt/tmp/test-file
bash: /mnt/tmp/test-file: Invalid argument
mars:~# rm /mnt/tmp/test-file
mars:~# echo "Hello" > /mnt/tmp/test-file
mars:~# echo "Hello" > /mnt/tmp/test-file
bash: /mnt/tmp/test-file: Invalid argument

I've also noticed that the stat() syscall too returns bad values after the first readdir().

This is really ugly...anybody ?

TIA

Gianluca