Could be due to NFS client silly rename.
On Apr 12, 2017 8:06 PM, "Kinglong Mee" <mijinlong@xxxxxxxxxxx> wrote:
When I testing ganesha nfs bases on glusterfs, the runltp always warning as,
rm: cannot remove ‘/mnt/nfs/ltp-JEYAuky2dz/.nfsaa46457a6a72f8ea000014f5’: Device or resource busy
rm: cannot remove ‘/mnt/nfs/ltp-JEYAuky2dz/rmderQsjV’: Directory not empty
and, "rmderQsjV" also contains files at the back-end, and nfs client shows empty.
My test environments are,
Centos 7 (kernel-3.10.0-514.10.2.el7.x86_64),
Glusterfs (glusterfs-3.8.10-1.el7.x86_64),
NFS-Ganesha (nfs-ganesha-2.3.3-1.el7.x86_64).
#cat /etc/ganesha/ganesha.conf
EXPORT
{
SecType = "sys";
Pseudo = "/gvtest";
Squash = "No_Root_Squash";
Access_Type = "RW";
Path = "/gvtest";
Export_Id = 1;
FSAL {
Name = "GLUSTER";
Hostname = "localhost";
Volume = "gvtest";
Volpath = "/";
}
}
# gluster volume info
Volume Name: gvtest
Type: Distribute
Volume ID: 65d20de1-16cd-4ae8-a860-254b3d6c56d0
Status: Started
Snapshot Count: 0
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: 192.168.9.111:/gluster-test/gvtest
Brick2: 192.168.9.112:/gluster-test/gvtest
Options Reconfigured:
nfs.disable: on
performance.readdir-ahead: off
transport.address-family: inet
performance.write-behind: off
performance.read-ahead: off
performance.io-cache: off
performance.quick-read: off
performance.open-behind: off
performance.stat-prefetch: off
------------------------------------------------------------ ------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha- devel
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
