Hello, we need to replace one of the OSS in the cluster. We wounder whether simply copying(eg. rsync) over network the content of all /dev/sdX(ldiskfs mounted) from OSS to be replaced to the new, already lustre formatted OSS (all /dev/sdX on both servers are the same) will work? Sorry if the question was already asked, can not find it. Thank you for any help. Gizo Nanava
Hi, On Thu, Feb 24, 2011 at 10:39:32AM +0100, Gizo Nanava wrote:> we need to replace one of the OSS in the cluster. We wounder whether > simply copying(eg. rsync) over network > the content of all /dev/sdX(ldiskfs mounted) from OSS to be replaced to > the new, already lustre formatted OSS > (all /dev/sdX on both servers are the same) will work?Yes, the procedure is detailed in the manual: http://wiki.lustre.org/manual/LustreManual18_HTML/LustreTroubleshooting.html#50651190_pgfId-1291458 Johann -- Johann Lombardi Whamcloud, Inc. www.whamcloud.com
Hi Johann, interesting. Is there no need to set the file system volume of the new OSS name via tune2fs to the same string? Michael Am Donnerstag, den 24.02.2011, 10:48 +0100 schrieb Johann Lombardi:> Hi, > > On Thu, Feb 24, 2011 at 10:39:32AM +0100, Gizo Nanava wrote: > > we need to replace one of the OSS in the cluster. We wounder whether > > simply copying(eg. rsync) over network > > the content of all /dev/sdX(ldiskfs mounted) from OSS to be replaced to > > the new, already lustre formatted OSS > > (all /dev/sdX on both servers are the same) will work? > > Yes, the procedure is detailed in the manual: > http://wiki.lustre.org/manual/LustreManual18_HTML/LustreTroubleshooting.html#50651190_pgfId-1291458 > > Johann >-- Michael Kluge, M.Sc. Technische Universit?t Dresden Center for Information Services and High Performance Computing (ZIH) D-01062 Dresden Germany Contact: Willersbau, Room A 208 Phone: (+49) 351 463-34217 Fax: (+49) 351 463-37773 e-mail: michael.kluge at tu-dresden.de WWW: http://www.tu-dresden.de/zih -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5973 bytes Desc: not available Url : http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110224/ba434231/attachment-0001.bin
Hi Michael, On Thu, Feb 24, 2011 at 10:51:59AM +0100, Michael Kluge wrote:> interesting. Is there no need to set the file system volume of the new > OSS name via tune2fs to the same string?That''s what i was checking :) It seems that the disk label is only updated when the MGS asks for the LDD to be rewritten. I don''t think we are in this case, so I would change the label on the new device with e2label. HTH Cheers, Johann -- Johann Lombardi Whamcloud, Inc. www.whamcloud.com
Hello, thank you all for your replies. One question to be on safe side, if something goes wrong, would it be possible to reuse the replaced OSS? Unfortunately no time for tests. Thank you. GN On 02/24/2011 11:14 AM, Johann Lombardi wrote:> Hi Michael, > > On Thu, Feb 24, 2011 at 10:51:59AM +0100, Michael Kluge wrote: >> interesting. Is there no need to set the file system volume of the new >> OSS name via tune2fs to the same string? > That''s what i was checking :) > It seems that the disk label is only updated when the MGS asks for the LDD to be rewritten. I don''t think we are in this case, so I would change the label on the new device with e2label. > > HTH > > Cheers, > Johann >
On Thu, Feb 24, 2011 at 12:01:59PM +0100, Gizo Nanava wrote:> One question to be on safe side, if something goes wrong, would it be > possible to reuse the replaced OSS?Well, the problem is if the clients & the MDS reconnect and start performing operations (writes, creations, ...) on the new OST, you will of course miss all those updates on the old one. BTW, i have just realized that you want to replace the whole OSS and not just the storage. Is the new OSS going to have the same nid as the old one? If not, the procedure becomes more complicated since you need to update the configuration logs on the MGS: http://wiki.lustre.org/manual/LustreManual18_HTML/ConfiguringLustre.html#50651184_pgfId-1303457 HTH Cheers, Johann -- Johann Lombardi Whamcloud, Inc. www.whamcloud.com