From: Bryan Schumaker <bjschuma@netapp.com>
To: "Carlos Jiménez" <cjimenez@eneotecnologia.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, linux-nfs@vger.kernel.org
Subject: Re: Stale NFS file handle - persistent error
Date: Thu, 30 Aug 2012 12:02:04 -0400 [thread overview]
Message-ID: <503F8E7C.1030102@netapp.com> (raw)
In-Reply-To: <503F0BEF.4020104@eneotecnologia.com>
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?
- 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
next prev parent reply other threads:[~2012-08-30 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <503E131F.2040904@eneotecnologia.com>
2012-08-29 13:06 ` Stale NFS file handle - persistent error Carlos Jiménez
2012-08-29 17:11 ` J. Bruce Fields
2012-08-30 6:45 ` Carlos Jiménez
2012-08-30 9:17 ` Carlos Jiménez
2012-08-30 16:02 ` Bryan Schumaker [this message]
2012-08-30 18:59 ` J. Bruce Fields
2012-08-31 6:09 ` Carlos Jiménez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=503F8E7C.1030102@netapp.com \
--to=bjschuma@netapp.com \
--cc=bfields@fieldses.org \
--cc=cjimenez@eneotecnologia.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox