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
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
