Re: 3.16.3..3.17.1 hang in renameat2()

[Duncan <1i5t5.duncan@cox.net>]

Zygo Blaxell posted on Sun, 19 Oct 2014 15:25:26 -0400 as excerpted:

> It is the rename (mv) that is getting stuck.  It seems to hold a lock
> that prevents any process from later traversing d/e with find or ls, but
> does not prevent a stat on the path 'd/e/f' (which reports that d/e/f is
> now a hard link to a/b/c).

Just a btrfs user and list regular here, but this bit sounds very much 
like the symptoms from another current thread, except if a rename got 
stuck, he apparently never noticed.

Try looking up the "strange 3.16.3 problem" thread, OP Russell Coker, 
Sat, 18 Oct 2014 14:54:19 +1100, Message-ID: 
<201410181454.19375.russell@coker.com.au>

Here's the gmane link to the first post; you can follow the link from 
there to get the thread.

<http://permalink.gmane.org/gmane.comp.file-systems.btrfs/39515>

Symptoms:

# find . -name "*546"
./1412233213.M638209P10546
# ls -l ./1412233213.M638209P10546
ls: cannot access ./1412233213.M638209P10546: No such file or directory


-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman