From: Andreas Radke <a.radke@arcor.de>
To: linux-nfs@vger.kernel.org
Subject: NFSv4 ACL issues since 3.0.72 leading to corrupt files (xfs)
Date: Fri, 10 May 2013 21:55:53 +0200 [thread overview]
Message-ID: <20130510215553.0a1130be@laptop64.home> (raw)
I'm running a server with a NFSv4 share drive that also hosts a Mail
directory I provide with dovecot IMAP server. Dovecot has ACL plugin
disabled.
Since the 4 NFSv4 ACL related commits in kernel 3.0.72 (and all other
stable kernels) all kernels until the recent stable releases give such
errors when changing :
imap(andyrtr):
Error:maildir_file_do(/mnt/share/andyrtr/Mail/.Mailinglisten.Linux-stable/cur/msg.MFVZBC:2,):
Filename keeps changing
These are file system errors. I need to run xfs_repair on the drive
and then need to stay with an outdated kernel.
I think this is a serious regression. Can somebody confirm it and
tell me if this should be reported somewhere to a bug tracker
against nfs/xfs/... and how to solve this?
-Andy
ArchLinux
next reply other threads:[~2013-05-10 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 19:55 Andreas Radke [this message]
2013-05-11 2:56 ` NFSv4 ACL issues since 3.0.72 leading to corrupt files (xfs) Myklebust, Trond
2013-05-11 9:56 ` Andreas Radke
2013-05-12 3:59 ` Myklebust, Trond
2013-05-12 10:19 ` Andreas Radke
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=20130510215553.0a1130be@laptop64.home \
--to=a.radke@arcor.de \
--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