Hello list,
the manual (May 2008) describes on page 4-14 how to remove an OST from LUSTRE.
Its says "deactivate the OST (make it read-only).
Hm, i'am a bit puzzled here.
When i deactivate the OST on the MDS using
'lctl --device 18 conf_param foo-OST000d.osc.active=0' the device is
deactivated bu
Sorry, i forgot.
Lustre Version 1.6.6
Kernel 2.6.22.19 vanilla with lustre patches.
Thanks and Regards
Heiko
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss
On Jan 16, 2009 13:45 +0100, Heiko Schroeter wrote:
> the manual (May 2008) describes on page 4-14 how to remove an OST from LUSTRE.
> Its says "deactivate the OST (make it read-only).
>
> Hm, i'am a bit puzzled here.
> When i deactivate the OST on the MDS using
> 'lctl --device 18 conf_param foo
Thanks very much for the clarification and it works.
Actually i wasn't aware of the differences between set_param and config_param.
Ashes on me.
Is it possible to get these infos into the documentation as it may hit one or
the other in the lustre community ?
The manual only gives two 'general' a
Andreas, thank you very much for this log sought-after explanation!
As far as I have read manuals and the mailing list, no one ever put these two
commands side by side.
One would only find the advice to "make the OST read-only" - and the how-to
side I also only found
the "lctl --conf_param..."
On Mon, 2009-01-19 at 16:45 +0100, Thomas Roth wrote:
> Andreas, thank you very much for this log sought-after explanation!
>
> As far as I have read manuals and the mailing list, no one ever put these two
> commands side by side.
> One would only find the advice to "make the OST read-only" - an
On Jan 19, 2009 10:18 +0100, Heiko Schroeter wrote:
> Is it possible to get these infos into the documentation as it may hit one or
> the other in the lustre community ?
Yes, we always welcome improvements to the documentation. As you can
imagine, I rarely need to reference the documentation my
Hm, i do got it that one has to 'move' the file back. But ...
> > Copy the data on a client to a temp storage outside (does it has to be
> > outside?) the lustre system and 'move' them back into lustre to create
> > new inodes entries on the MDS.
>
> Actually, it should NOT be on storage outside L
You have to copy the file to a new name _on Lustre_ to allocate a new
inode (new storage) on Lustre, and then "mv" it to replace the
original file.
Mv across filesystems is basically a cp, which will overwrite the
destination file, not replace the inode.
Kevin
On Jan 20, 2009, at 3:55 AM,
In the Lustre manual 4.2.10.1 "Removing an OST from the File System", it
tells you to how to deactivate the OSC on the MDT so no files are
written to the OST, then says:
3 Use "lfs find" to discover all files that have objects residing on the
deactivated OST.
4 Copy (not move) the files to a
On Sat, 2009-09-19 at 22:22 +0200, Christopher J. Walker wrote:
> In the Lustre manual 4.2.10.1 "Removing an OST from the File System", it
> tells you to how to deactivate the OSC on the MDT so no files are
> written to the OST, then says:
> I can't convince myself there isn't a race condition
11 matches
Mail list logo
