I have some basic lustre questunes wich i didnt get answares from lustre official maulals and think maybee people here allready run into some of those issues and can be of help . - Asuming an OST is gone and a new server (new install need to replcace it) On my tests after formating the new OTS with --index=0002 for example when trying to mount it it cant / error code say that this OST index id allready in use so i may missing a procedure maybee on the MDT etc.. - I tested the dump/restore utility wich suppose to make a minimal dump including the EA of file systems the MDT is dumping ok but on the OST it say that the file system isnt supported I just explore all options of backing up a single OST/MDT drives including LVM backup but the dump/restore looks better seens its backing up only the data rather then the entire drive - Just want to make sure that the default policy(if not mentioned otherwise on the format) is not to stipe files My tests show that this is the case but i just want to make sure If soo where is the --param="lov.stripe.count=...." need to come ? OST''s or MDT on MDT for example its making the MDT unmoutables - If i want to stripe a single file i need to create it first (not existing file) so if i create it with a stripe policy then how can i use the real file with this policy , will overwrite the file with the real file will work ? Any help will be apruciated . ---------------------------------------------------------- Outgoing messages are virus free checked by NOD32 system -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080223/819bf220/attachment-0002.html
On Sat, 2008-02-23 at 13:17 +0200, Mailer PH wrote:> > - Asuming an OST is gone and a new server (new install need to > replcace it) > On my tests after formating the new OTS with --index=0002 for example > when trying to mount it it cant / error code say that this OST index > id allready in use > so i may missing a procedure maybee on the MDT etc..You need to use --write-conf.> - Just want to make sure that the default policy(if not mentioned > otherwise on the format) is not to stipe filesThat is correct. Striping certainly helps in particular situations, but is not a good general default for all files.> - If i want to stripe a single file i need to create it first (not > existing file) so if i create it with a stripe policy then how can > i use the real file with this policy , will overwrite the file with > the real file will work ?Hrm. I''m not sure if you are asking what I think you are asking, but you can create a file with a specific policy with "lfs setstripe". b. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080225/cb7bb1bb/attachment-0002.bin
Thanks ,> You need to use --write-conf.On the MTD ? or on all OST''s ?> Hrm. I''m not sure if you are asking what I think you are asking, but > you can create a file with a specific policy with "lfs setstripe".I meant that it is not possible to stripe existing file , just to create new file So i was wondering what is a best practic for stripe existing file It doesnt matter that the file will get the new setting from this point on as long as it will get the stripe config at the end Thanks , On Sat, 2008-02-23 at 13:17 +0200, Mailer PH wrote:> > - Asuming an OST is gone and a new server (new install need to > replcace it) > On my tests after formating the new OTS with --index=0002 for example > when trying to mount it it cant / error code say that this OST index > id allready in use > so i may missing a procedure maybee on the MDT etc..You need to use --write-conf.> - Just want to make sure that the default policy(if not mentioned > otherwise on the format) is not to stipe filesThat is correct. Striping certainly helps in particular situations, but is not a good general default for all files.> - If i want to stripe a single file i need to create it first (not > existing file) so if i create it with a stripe policy then how can > i use the real file with this policy , will overwrite the file with > the real file will work ?Hrm. I''m not sure if you are asking what I think you are asking, but you can create a file with a specific policy with "lfs setstripe". b. ---------------------------------------------------------- Outgoing messages are virus free checked by NOD32 system -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080225/77413342/attachment-0002.html
On Mon, 2008-02-25 at 23:29 +0200, Mailer PH wrote:> Thanks ,NP.> On the MTD ? or on all OST''s ?On whatever node you are trying to re-use/re-deploy. I''m afraid I forget the context of your original question.> I meant that it is not possible to stripe existing file ,Right. Once a file is created, you cannot change it''s striping policy without re-creating it. You could achieve that with a simple: $ lfs setstripe foo <stripe params> $ cp $file foo $ mv foo $file> just to create new fileRight.> So i was wondering what is a best practic for stripe existing fileAs above.> It doesnt matter that the file will get the new setting from this > point on as long as it will get the stripe config at the endNo, that is not supported. A file has to have a consistent striping policy from start to end which is why you cannot specify the striping on an existing file using lfs setstripe. b. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080225/f71e6887/attachment-0002.bin
> On the MTD ? or on all OST''s ?> On whatever node you are trying to re-use/re-deploy. I''m afraid I > forget the context of your original question.The initial thread was a problem to mount an OST after it crashes and reformated on a new server with --index=.... When mouting it get error --> OST with the same ID allready in use So the --write-conf as a solution to delete all logs make sense But i just wanted to make sure i fully understand and asked Where the tunefs.lustre ........ --write-conf need to be on MDT only ? the crashed OST ? or on all nodes on the claster ? Thanks , ---------------------------------------------------------- Outgoing messages are virus free checked by NOD32 system -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080226/4187fd15/attachment-0002.html
On Tue, 2008-02-26 at 00:14 +0200, Mailer PH wrote:> > The initial thread was a problem to mount an OST after it crashes and > reformated on a new server with --index=.... > When mouting it get error --> OST with the same ID allready in use > So the --write-conf as a solution to delete all logs make sense > But i just wanted to make sure i fully understand and asked > Where the tunefs.lustre ........ --write-conf need to be on > MDT only ? the crashed OST ? or on all nodes on the claster ?Yes, on the new OST. b. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080225/5c16f6d6/attachment-0002.bin