Hi Brian, I think I have seen the persistent "UP", too. But I managed to deactivate my OST nevertheless, by > root@MDS:~# lctl set_param osc.WORK-OST008-osc*.active=0
And this has to be done on the MDS - to take effect everywhere. Cheers, Thomas On 05/01/2015 05:42 PM, Andrus, Brian Contractor wrote: > Ok, I have an OST that is pretty full and I want to rebalance the data on it. > I am using the RPMS for lustre-2.6.0-2.6.32_431.20.3.el6_lustre.x86_64.x86_64 > Also following the steps described in > https://build.hpdd.intel.com/job/lustre-manual/lastSuccessfulBuild/artifact/lustre_manual.pdf > section > 19.1.2<https://build.hpdd.intel.com/job/lustre-manual/lastSuccessfulBuild/artifact/lustre_manual.pdf%20section%2019.1.2> > > I see: > root@nas-01 ~]# lctl dl > 0 UP osd-ldiskfs MGS-osd MGS-osd_UUID 5 > . > . > 16 UP osp WORK-OST0008-osc-MDT0000 WORK-MDT0000-mdtlov_UUID 5 > > (OST8 is the one I want to migrate from) > So I do: > [root@nas-01 ~]# lctl --device 16 deactivate > > And see in dmesg: > Lustre: setting import WORK-OST0008_UUID INACTIVE by administrator request > > But... it doesn't seem to be deactivated when I do 'lctl dl': > [root@nas-01 ~]# lctl dl > 0 UP osd-ldiskfs MGS-osd MGS-osd_UUID 5 > . > . > 16 UP osp WORK-OST0008-osc-MDT0000 WORK-MDT0000-mdtlov_UUID 5 > > And, indeed, when I try to copy data around, it still stripes onto OST8. > > Am I missing something here?? > > Brian Andrus > ITACS/Research Computing > Naval Postgraduate School > Monterey, California > voice: 831-656-6238 > > > > > _______________________________________________ > lustre-discuss mailing list > [email protected] > http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org > _______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
