From: "Monsees, Steven C (US)" <steven.monsees@baesystems.com>
To: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: NFS under yocto
Date: Wed, 17 Nov 2021 17:20:29 +0000 [thread overview]
Message-ID: <20211117172136.9E61DC433F5@smtp.lore.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
Current yocto build is based on zeus...
We have one board running Yocto Embedded linux that is sharing a drive partition via NFS.
Another board is mounting the NFS share and has a few processes that can write data to the drive.
We are seeing conditions were concurrent writes (two client processes) appear to result in "Stale File Handles".
The drive partition is using the NTFS file system.
We are wondering if there are any issues in the NFS Server or Client that could be causing these "Stale File Handles".
We have tried to change some of the options used to mount the NFS share.
Are there any options in how the location is shared that we should try?
Anyone hear about or experienced similar issues ?
Thanks,
Steve
[-- Attachment #2: Type: text/html, Size: 2991 bytes --]
reply other threads:[~2021-11-17 17:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211117172136.9E61DC433F5@smtp.lore.kernel.org \
--to=steven.monsees@baesystems.com \
--cc=yocto@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.