Details
-
Bug
-
Resolution: Fixed
-
Major
-
Lustre 2.8.0, Lustre 2.9.0
-
3
-
9223372036854775807
Description
It looks like modern distros: SLES12, Fedora 21+ (possibly earlier) always do statfs on the mountpoint before issuing the umount call.
In case one of the OSTs is not available at that time - the statfs will hang.
In our tests there's a bunch of tests in conf-sanity that have this problem and it was "dealt with" in LU-5472 by just adding the -f umount option.
But this still leaves palces like recovery-single test 89 and something in recovery-small at the very least.
And most of all regular users would be affected too. So I wonder if we should deal with this issue somewhat more intelligently so that the unmount does not really hang in such a case?
Attachments
Issue Links
- is related to
-
LU-4039 Failure on test suite replay-single test_90: wrong stripe: f0, uuid: lustre-OST0000_UUID
- Resolved
-
LU-8544 recovery-double-scale test_pairwise_fail: start client on trevis-54vm5 failed
- Resolved
-
LU-8731 lfs df exits with status 0 on failures
- Resolved
-
LU-6233 recovery-small test_10d failed with 'file contents differ'
- Closed
-
LU-8069 Allow remount to include "flock" and "localflock", as well as "lazystatfs" and "nolazystatfs"
- Open
- is related to
-
LU-5472 conf-sanity test_32a: failed with 1
- Resolved
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...