Re: getcwd failure on NFS exported dir

2017-11-01 Thread Eddie Horng
-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Re: getcwd failure on NFS exported dir

2017-10-31 Thread sfjro--- via Aufs-users
Hi, Eddie Horng: > I have another workaround is to touch all dirs right after aufs mount, this > will force aufs always return copied-up file handle, although the cost is > extra time and space, but it does work for me to complete the building of > my codebase. Here is another workaround from

Re: getcwd failure on NFS exported dir

2017-10-25 Thread sfjro--- via Aufs-users
Eddie Horng: > I noticed that ls(1) and "stat ." work but getcwd(2) still fail after those > commands, I got so confused when I just beginning to understand this issue. Yes, that is why I wrote that I could not reproduce in the beginning. All commands I have tried worked. I might be confused

Re: getcwd failure on NFS exported dir

2017-10-24 Thread Eddie Horng
-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Re: getcwd failure on NFS exported dir

2017-10-24 Thread sfjro--- via Aufs-users
Eddie Horng: > I printed some logs of above test case, looks like my trace in initial post > is not exactly correct, d_invalidate is not directly call from mkdir > syscall, but I think mkdir triggers nfsd send a changed file handler then > d_invalidate is eventually invoked. Ok, so the scenario

Re: getcwd failure on NFS exported dir

2017-10-24 Thread Eddie Horng
-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Re: getcwd failure on NFS exported dir

2017-10-24 Thread sfjro--- via Aufs-users
Eddie Horng: > VFS does re-lookup the dropped dentry, but seems only happened if there's a > user-mode command trigger it, for example "cd ." > Look at below log, the dropped dentry instance 0x8fc22d3066c0 is > exactly the one getcwd used and is unlinked no matter how many times getcwd > is

Re: getcwd failure on NFS exported dir

2017-10-23 Thread Eddie Horng
-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Re: getcwd failure on NFS exported dir

2017-10-23 Thread sfjro--- via Aufs-users
Eddie Horng: > I printed some logs of above test case, looks like my trace in initial post > is not exactly correct, d_invalidate is not directly call from mkdir > syscall, but I think mkdir triggers nfsd send a changed file handler then > d_invalidate is eventually invoked. I don't think

Re: getcwd failure on NFS exported dir

2017-10-23 Thread Eddie Horng
-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Re: getcwd failure on NFS exported dir

2017-10-23 Thread Eddie Horng
-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Re: getcwd failure on NFS exported dir

2017-10-23 Thread sfjro--- via Aufs-users
sf...@users.sourceforge.net: > I have confirmed on Ubuntu-4.10.0-34.38 kernel. The kernel configuration > is for my test environment, so it must be different from yours. But I am > not sure whether the config is related. I mean that I could not reproduce the problem. J. R. Okajima

Re: getcwd failure on NFS exported dir

2017-10-23 Thread sfjro--- via Aufs-users
Eddie Horng: > e. in step 8, mkdir invokes nfs_lookup_revalidate > f. server side again run into: nfsd -> nfsd_lookup -> aufs::aufs_encode_fh > g. this time, aufs_encode_fh returns filehander of folderA in br0(rw) > i. in nfs_lookup_revalidate, nfs_compare_fh(NFS_FH(inode), fhandle) is > called

Re: getcwd failure on NFS exported dir

2017-10-23 Thread sfjro--- via Aufs-users
Hello Eddie, Eddie Horng: > I encountered a getcwd() failure problem on a NFS mounted dir, in server > side, the dir is aufs mounted. > This problem can be always reproduced as below steps: ::: Thanx for the detailed report and the analysis. But I could not reproduce the problem on my