[lustre-discuss] Disabling max creates and migrating data doesn't seem to be reducing the usage on an OST
G.Iannetti at gsi.de
Tue Feb 16 06:50:00 PST 2021
did you check if writes to OST000f can be done while the max_create_count of the OST is 0?
I would validate that with a write to that OST...
You should use `lfs setstripe` on that OST.
As I can remember, Lustre should choose another OST for creating the new file.
Of course you should than check the OST index, where the new file was created at with `lfs getstripe`.
From: lustre-discuss <lustre-discuss-bounces at lists.lustre.org> on behalf of Kurt Strosahl <strosahl at jlab.org>
Sent: Thursday, February 11, 2021 16:51
To: lustre-discuss at lists.lustre.org
Subject: [lustre-discuss] Disabling max creates and migrating data doesn't seem to be reducing the usage on an OST
One of the OSTs in a lustre file system I manage is showing a higher usage. I attempted to stop writes by setting the max_create_count to zero and then moving data off it but that doesn't seem to be working.
> lfs df | grep OST:15lustre19-OST000f_UUID 71145018368 62653382656 8491631616 89% /lustre19[OST:15]
MDS> lctl set_param osp.lustre19-OST000f*.max_create_count=0
MDS> lctl get_param osp.lustre19-OST000f*.max_create_count
lfs find /lustre19/expphy/volatile --ost lustre19-OST000f -size +50M | lfs_migrate -y
I've been watching it, and the ost in question isn't shrinking. I can see its size usage go down a bit... and then tick up a bit
Kurt J. Strosahl
System Administrator: Lustre, HPC
Scientific Computing Group, Thomas Jefferson National Accelerator Facility
More information about the lustre-discuss