Absolutely
On Sat, Apr 4, 2015 at 1:30 AM, sf...@users.sourceforge.net
[1]sf...@users.sourceforge.net wrote:
Jean-Ray Arseneau:
Apologies, I sent the wrong log file.
Here is the correct one, I am quite sure the patch is installed, as I
see =
sf...@users.sourceforge.net:
Your case looks different a little bit from Christoph Pleger's, but it
must be same essentially. I've found linux NFS client always sets
MS_POSIXACL (which is a flag in VFS layer) even if it was mounted with
'noacl.' I don't think it illegal or violation something,
Jean-Ray Arseneau:
Absolutely
Here is an additional debug patch.
J. R. Okajima
b.patch.bz2
Description: BZip2 compressed data
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by
Hereâs the updated log after applying the latest debug b.patch:
https://dl.dropboxusercontent.com/u/26943/syslog-20150404.zip
Jean
On Sat, Apr 4, 2015 at 11:53 AM, sf...@users.sourceforge.net
[1]sf...@users.sourceforge.net wrote:
Jean-Ray Arseneau:
Absolutely
I'm running into a problem using tar(1) to create a read-only file on an
aufs file system with two nfs4 branches.
test@sivtar-8e3b7f91b4ed:~/test$ ls
test@sivtar-8e3b7f91b4ed:~/test$ echo test x
test@sivtar-8e3b7f91b4ed:~/test$ chmod 0400 x
Jean-Ray Arseneau:
Here=E2=80=99s the updated log after applying the latest debug b.patch:
Thank you very much.
I think I could see the scenario.
As you might know, the mfs policy caches the free-space value per
branch, and pmfsrr policy internally runs the mfs rourtine twice. The
first one is
