Details
-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
Lustre 1.8.x (1.8.0 - 1.8.5)
-
None
-
scientific linux 5
-
3
-
10551
Description
I have in the past removed an OST from lustre. I drained it, stopped lustre, writeconf everything and fired lustre up without it. I have not had any issues until today. When I run lfs find on the OST next in line after the missing OST no files are found. For example:
smuhpc-OST000d_UUID 5.4T 5.3T 85.1G 98% /lustre[OST:13]
smuhpc-OST000e_UUID 4.5T 4.4T 82.5G 98% /lustre[OST:14]
smuhpc-OST000f_UUID 10.7T 5.2T 5.5T 48% /lustre[OST:15]
smuhpc-OST0010_UUID 9.0T 4.5T 4.4T 50% /lustre[OST:16]
smuhpc-OST0013_UUID 4.5T 3.8T 674.9G 85% /lustre[OST:19]
smuhpc-OST0014_UUID 4.5T 473.8M 4.5T 0% /lustre[OST:20]
smuhpc-OST0015_UUID 4.5T 474.1M 4.5T 0% /lustre[OST:21]
smuhpc-OST0016_UUID 4.5T 474.2M 4.5T 0% /lustre[OST:22]
As you can see there is a jump between OST0010 and OST0013. lfs find will not find any files on OST0013. All files are there and everything else seems to work. I am able to find files by traversing the file system and runing lfs getstripe.
I am draining the OSTs to do some work on the underlying hardware.
Attachments
Issue Links
- is duplicated by
-
LU-1738 lfs find cannot find files in OST that died, whilst lfs getstripe can
- Resolved
- Trackbacks
-
Lustre 1.8.x known issues tracker While testing against Lustre b18 branch, we would hit known bugs which were already reported in Lustre Bugzilla https://bugzilla.lustre.org/. In order to move away from relying on Bugzilla, we would create a JIRA