Hi and thank you for support,

I tried to run  pts/disk of Phoronix Test Suite in the mounted nfsv4 partition 
and I not experienced any failure, after that I executed also iozone without 
errors.

But this test targets only on writable branch, so I try to stress also the 
read only nfs branch with some concurrent readers, same results.

It seems that this configuration works with NFSv4, performance are not great 
but this is not the focus.

Bye


In data mercoledì 11 marzo 2020 09:42:58 CET, J. R. Okajima ha scritto:
> Hello Leonardo,
> 
> Leonardo Secci:
> > I have an issue exporting an aufs filesystem usiing nfsv3, I can mount NFS
> > export with success but I get an error reading a file or a directory.
> > 
> > Into syslog I see:
> > [  183.774819] aufs aufs_encode_fh:763:nfsd[1467]: nfs encode_fh failed
> > 
> > 
> > [CLIENTc7]# ls /mail/01/BOX1/Maildir/
> > 
> > [CLIENTc7]# cat /mail/01/BOX1/Maildir/maildirsize cat:
> > /mail/01/BOX1/Maildir/maildirsize: Input/output error
> 
> According to your additional info, I can see that
> - you have two aufs mounts on your nfs server SERVERc7, /mail/overlay/0[13]
>       + /mail/overlay/01 = /mail/new/01 + /mail/prod/01
>       + /mail/overlay/03 = /mail/new/03 + /mail/prod/03
> - /mail/new/0[13] are xfs
> - /mail/prod/0[13] are nfs
> 
> The aufs manual describes some limitations about "Exporting Aufs via
> NFS",
> 
> (quote)
> ----------------------------------------
> .SH Exporting Aufs via NFS
> Aufs is supporting NFS\-exporting.
> Since aufs has no actual block device, you need to add NFS `fsid' option at
> exporting. Refer to the manual of NFS about the detail of this option.
> 
> There are some limitations or requirements.
> .RS
> .Bu
> The branch filesystem must support NFS\-exporting.
> ----------------------------------------
> 
> Your branch fs /mail/prod/0[13] are nfs and they don't support
> NFS\-exporting itself.
> 
> I don't know why /mail/03, nfs4 on CLIENTc7.
> Is it stably working?  Is it OK if you try giving some heavy workloads
> on CLIENTc7?
> 
> 
> J. R. Okajima






Reply via email to