Details
-
Bug
-
Resolution: Incomplete
-
Minor
-
None
-
None
-
None
-
rhel6.3
-
3
-
8542
Description
When mounting a lustre client, if we use the 'exclude' option to ignore inactive OSTs this option is not well taken into account.
From the mount.lustre manpage:
exclude=ostlist Start a client or MDT with a (colon-separated) list of known inactive OSTs.
We run the mount command:
[root@berlin105 ~]# mount -t lustre -o user_xattr,exclude=b8-OST0007 60.64.2.84@o2ib0,160.64.2.84@o2ib1:/b8 /b8
In the dmesg we can see the option is seen by lustre:
[root@berlin105 ~]# dmesg
Lustre: MGC60.64.2.84@o2ib: Reactivating import
Lustre: 18527:0:(obd_mount.c:1892:lustre_check_exclusion()) Excluding b8-OST0007 (on exclusion list)
Lustre: Mounted b8-client
But the osc is always up and we can still write or read:
[root@berlin105 ~]# lctl dl | grep b8-OST0007
14 UP osc b8-OST0007-osc-ffff8808773f9c00 6dafd66d-9939-a1d6-cf40-529950167a65 5
Whether the OST is disabled in the MDT or not the problem is always present and we are always accessing this OST from the client. If we try to deactivate the OST with 'lctl --device b8-OST0007-osc-ffff8808773f9c00 deactivate' then the OST is well disabled but never when using exclude option.
Attachments
Issue Links
- is related to
-
LU-2200 Test failure on test suite conf-sanity, subtest test_32a
- Resolved