Re: Stale NFS file handle - persistent error

["Carlos Jiménez" <cjimenez@eneotecnologia.com>]

Ok, you are right.
Certainly, it is a very old kernel because we had problems with the SCSI 
controller in new distros with 2.6-3 kernel. I think there is another 
computer available, so I think the best choice will be to try to move to 
that one.

Thanks guys for your fast replies and your time.

Carlos.

On 08/30/2012 08:59 PM, J. Bruce Fields wrote:
> On Thu, Aug 30, 2012 at 12:02:04PM -0400, Bryan Schumaker wrote:
>> On 08/30/2012 02:45 AM, Carlos Jiménez wrote:
>>> Hi,
>>>
>>> Thank you for your reply.
>>>> Could you be more specific?  What kernel version exactly, and what
>>>> filesystem are you exporting, and what are the export options?
>>> Kernel version: 2.4.27-3-386
>> 2.4.27 is incredibly old, do you have access to the server and can you try a more recent kernel?
> Yes, we can't make much use of 2.4 bug reports at this point; you should
> probably report this to your distro, or try a more recent kernel.
>
> --b.
>
>> - Bryan
>>
>>> Filesystem exported: ext3
>>> Export options: rw,no_root_squash,sync
>>>
>>> I've shared/exported to the full network 192.168.180.0/24.
>>> The exported directory is /opt/virtual/one and in /opt/virtual it is mounted /dev/cciss/c0d0p4 (with default options), which is a 256GB (8GB used) partition over a 3 disks RAID5.
>>>
>>>> What version of NFS are you using?
>>>>
>>> Vers 3
>>>
>>>> I assume you're not doing anything else with either file or directory at
>>>> the same time?  (E.g., not deleting or renaming the file while it's
>>>> being copied?)
>>>>
>>>>
>>> I'm not doing anything else with either file or directory at the same time.
>>>
>>> -- 
>>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html