From: Martin Wege <martin.l.wege@gmail.com>
To: Cedric Blancher <cedric.blancher@gmail.com>
Cc: Ms-nfs41-client-devel@lists.sourceforge.net,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [Ms-nfs41-client-devel] CITI ms-nfsv41 client: IOCTL_NFS41_WRITE failed with 31 xid=5481722 opcode=NFS41_FILE_QUERY?
Date: Fri, 10 Nov 2023 08:20:00 +0100 [thread overview]
Message-ID: <CANH4o6MBpoN2P6B5ri3hBrLJmFawjS0QLCYPAACjkdJkv76XSg@mail.gmail.com> (raw)
In-Reply-To: <CALXu0UfzqBu-T9tZuchqnZBkvfuDUJaBmcDgTaWZfUC_yimGCA@mail.gmail.com>
On Fri, Nov 10, 2023 at 1:07 AM Cedric Blancher
<cedric.blancher@gmail.com> wrote:
>
> On Fri, 1 Sept 2023 at 05:53, Cedric Blancher <cedric.blancher@gmail.com> wrote:
> >
> > Good morning!
> >
> > The CITI ms-nfsv41 client for Windows sometimes prints the following warnings:
> >
> > 1eac: IOCTL_NFS41_WRITE failed with 31 xid=5481722 opcode=NFS41_FILE_QUERY
> >
> > Does anyone know what this means? Data loss?
>
> Roland Mainz fixed the bug in
> https://github.com/kofemann/ms-nfs41-client/commit/7824f2398170d07d2ad83bd23fac4dacd34cd47a
>
> So no data loss, but a Win32 syscall randomly failed.
>
Cool
So we finally get a working opensource Windows NFSv4 client? How far
away is the code from being production-ready?
Thanks,
Martin
prev parent reply other threads:[~2023-11-10 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 3:53 CITI ms-nfsv41 client: IOCTL_NFS41_WRITE failed with 31 xid=5481722 opcode=NFS41_FILE_QUERY? Cedric Blancher
2023-09-07 21:21 ` [Ms-nfs41-client-devel] " Martin Wege
2023-11-10 0:06 ` Cedric Blancher
2023-11-10 7:20 ` Martin Wege [this message]
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=CANH4o6MBpoN2P6B5ri3hBrLJmFawjS0QLCYPAACjkdJkv76XSg@mail.gmail.com \
--to=martin.l.wege@gmail.com \
--cc=Ms-nfs41-client-devel@lists.sourceforge.net \
--cc=cedric.blancher@gmail.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;
as well as URLs for NNTP newsgroup(s).