[Lustre-discuss] Permanently removing an OST

[Florent Parent]

On Wed, May 26, 2010 at 19:08, Andreas Dilger <andreas.dilger at oracle.com> wrote:
> On 2010-05-26, at 16:49, Florent Parent wrote:
>>
>> on MGS:
>> lctl conf_param osc.lustre1-OST002f-osc.active.osc.active=0
>
> If you specified the above, it is possible that you only deactivated it on the MDS, not on the clients as well.

Right. It was executed on all clients as well.

>
>> Many days later, and even following a complete server/clients reboot,
>> we are now seeing this target being active on clients:
>>
>> on MDT:
>> [root at mds2 ~]# lctl get_param osc.lustre1-OST002f-osc.active
>> osc.lustre1-OST002f-osc.active=0
>> [root at mds2 ~]# lctl dl|grep 002f
>> 51 UP osc lustre1-OST002f-osc lustre1-mdtlov_UUID 5
>
> The device is configured, but if it is not active it will not be used for anything.
>
>> on client:
>> # ssh r101-n33 lctl dl |grep 002f
>> 50 UP osc lustre1-OST002f-osc-ffff810377354000
>> ef3f455a-7f67-134e-cf38-bcc0d9b89f26 4
>
> What does "active" report for this OSC on a client?

Shows 0 (I don't know why we are seeing a double entry here). So I
guess it's inactive. I was under the impression references to the OST
would go away. It's also confusing to have the OST show as UP in "lctl
dl".

# ssh r101-n33 lctl get_param osc.lustre1-OST002f-osc*.active
osc.lustre1-OST002f-osc-ffff810371ac3c00.active=0
osc.lustre1-OST002f-osc-ffff810377354000.active=0

Thanks
Florent