is 'umount' asynchronous?
Subsystems (2)
While testing NFSv4 over TCPv6 on 2.6.36-rc3 + my srcaddr= patch today, I noticed that I was getting 'busy' errors from umount if I closed a file in a program and then had it immediately system("umount ...");
If I retry the umount a few times, it will start returning 'already unmounted'. It took around 50-100ms (I was sleeping 50ms between umount attempts).
Is that expected behaviour? Seems we never needed any retries and never got 'busy' on 2.6.34 and earlier.
Thanks,
Ben
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com
Quoted 9 lines · Ben Greear
While testing NFSv4 over TCPv6 on 2.6.36-rc3 + my srcaddr= patch today, I noticed that I was getting 'busy' errors from umount if I closed a file in a program and then had it immediately
system("umount ...");If I retry the umount a few times, it will start returning 'already unmounted'. It took around 50-100ms (I was sleeping 50ms between umount attempts).
Is that expected behaviour? Seems we never needed any retries and never got 'busy' on 2.6.34 and earlier.
I've had this:
# ARGH: getting a spurious EBUSY on some
# umounts; this helps:
sleep 1;
in my test scripts for a while, and haven't tried to investigate why it's happening. (Checking git logs: I added that in July 2008.)
--b.