[Lustre-discuss] how do I deactivate a very wonky OST

[Sean Brisbane]

This caught me out in a recent upgrade:

cat /proc/fs/lustre/lov/{yourmdt}/target_obd

rather than

"lctl dl"

Shows the state of the OST.

Cheers,
Sean

________________________________
From: lustre-discuss-bounces at lists.lustre.org [lustre-discuss-bounces at lists.lustre.org] on behalf of Andrus, Brian Contractor [bdandrus at nps.edu]
Sent: 13 January 2015 17:28
To: lustre-discuss at lists.lustre.org
Subject: [Lustre-discuss] how do I deactivate a very wonky OST

All,

We are still trying to move forward getting our filesystem at least partially up with a failed OST.

Currently the OST will kernel panic any device that mounts it. That seems to be a constant.

So, the plan is to bring the system up without that OST and find what data will be lost.
Now, I am trying to deactivate the OST on the MGS, but it seems to have no effect.
Running lctl --device 14 deactivate does not change anything. The OST still shows ‘UP’

Is there a way to force lustre to deactivate an OST altogether when it is showing ‘UP’ and the OST is not going to be happily mounted?

I can mount the filesystem, but many actions hang (ls, df, etc).

Brian Andrus
ITACS/Research Computing
Naval Postgraduate School
Monterey, California
voice: 831-656-6238

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20150114/3d12bb13/attachment.htm>