From: Nathaniel Rutman <[EMAIL PROTECTED]>
Date: Fri, 17 Nov 2006 12:11:25 -0800
John R. Dunning wrote:
> From: Nathaniel Rutman <[EMAIL PROTECTED]>
> Date: Fri, 17 Nov 2006 11:39:59 -0800
>
> Deactivate the device on the MDT side for a currently-running server
> e.g. 13 UP osc lustre-OST0001-osc lustre-mdtlov_UUID 5
> lctl --device 13 deactivate
>
> Ok, did that. It still shows as UP when I lctl dl, though.
>
Yes, it does. Your question prompted me to take a look at changing that...
For now, you can get to it here:
cfs21:~# cat /proc/fs/lustre/lov/lustre-mdtlov/target_obd
0: lustre-OST0000_UUID ACTIVE
1: lustre-OST0001_UUID INACTIVE
Ok.
>
> To start a client or MDT with a known down OST:
> mount -t lustre -o exclude=lustre-OST0001 ...
>
> Ah, ok. So there isn't any way to say "Remove all traces of this OST
from the
> system so that nobody knows it was ever there" ?
>
That is an eventual planned feature, but isn't implemented yet.
Ok.
You could --writeconf the MDT to nuke the config logs, then restart the
servers,
Example?
and
that will truly erase all traces of OSTs that don't restart. Beware,
any file that has
stripes on such an erased OST will be very confusing to Lustre...
Sure, of course. I suppose to do it really right, you'd want some kind of
tool that could examine the MD and gripe about anything that had stripes on
the OST in question. But that would be pretty slow.
Beware #2: I don't claim to have tried this myself.
Understood. Perhaps I'll try this next week, or perhaps I'll just blow it
away and rebuild it without the offending unit.
Thanks...
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
