\ufeff<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18813">
<STYLE>@font-face {
font-family: \u5b8b\u4f53;
}
@font-face {
font-family: Verdana;
}
@font-face {
font-family: @\u5b8b\u4f53;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt 90.0pt; layout-grid: 15.6pt; }
P.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; FONT-SIZE: 10.5pt
}
LI.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; FONT-SIZE: 10.5pt
}
DIV.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; FONT-SIZE: 10.5pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
FONT-STYLE: normal; FONT-FAMILY: Verdana; COLOR: windowtext; FONT-WEIGHT: normal; TEXT-DECORATION: none; mso-style-type: personal-compose
}
DIV.Section1 {
page: Section1
}
UNKNOWN {
FONT-SIZE: 10pt
}
BLOCKQUOTE {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>
</HEAD>
<BODY style="MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE: 10pt">
<DIV><FONT color=#000080 size=2 face=Verdana>Hi, Andreas</FONT></DIV>
<DIV><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080>Yeah, Thank you very much. I failed to make e2fsck on
ost weeks ago, As a result, some files were destroyed. Then I find the reason
why we failed doing it. I find someone said that there is some bugs for e2fsck.
Due to this and the time pressure, our team is talking about whether to run
e2fsck.</FONT></DIV>
<DIV><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080>So I really you can give some tips for it and show some
points to pay attention!</FONT></DIV>
<DIV><FONT color=#ff00ff>see inline...</FONT></DIV>
<DIV><FONT color=#ff00ff></FONT> </DIV>
<DIV><FONT color=#ff00ff></FONT> </DIV>
<DIV><FONT color=#ff00ff></FONT> </DIV>
<DIV>thanks,</DIV>
<DIV>Sarea</DIV>
<DIV><FONT color=#000080 size=2 face=Verdana></FONT> </DIV>
<DIV><FONT color=#000080 size=2 face=Verdana></FONT> </DIV>
<DIV><FONT color=#c0c0c0 size=2 face=Verdana>2009-07-30 </FONT></DIV><FONT
color=#000080 size=2 face=Verdana>
<HR style="WIDTH: 100px" align=left color=#b5c4df SIZE=1>
</FONT>
<DIV><FONT color=#c0c0c0 size=2 face=Verdana><SPAN>huangql</SPAN> </FONT></DIV>
<HR color=#b5c4df SIZE=1>
<DIV><FONT size=2 face=Verdana><STRONG>\u53d1\u4ef6\u4eba\uff1a</STRONG> Andreas Dilger
</FONT></DIV>
<DIV><FONT size=2 face=Verdana><STRONG>\u53d1\u9001\u65f6\u95f4\uff1a</STRONG> 2009-07-30 11:41:13
</FONT></DIV>
<DIV><FONT size=2 face=Verdana><STRONG>\u6536\u4ef6\u4eba\uff1a</STRONG> huangql </FONT></DIV>
<DIV><FONT size=2 face=Verdana><STRONG>\u6284\u9001\uff1a</STRONG> lustre-discuss </FONT></DIV>
<DIV><FONT size=2 face=Verdana><STRONG>\u4e3b\u9898\uff1a</STRONG> Re: [Lustre-discuss] How to
estimate the time for e2fsck on OST </FONT></DIV>
<DIV><FONT size=2 face=Verdana></FONT> </DIV>
<DIV><FONT size=2 face=Verdana>
<DIV>On Jul 30, 2009 09:00 +0800, huangql wrote:</DIV>
<DIV>> Thanks so much to you. The variables of our filesystem as follow:</DIV>
<DIV>> </DIV>
<DIV>> size of the filesystem: 400TB</DIV>
<DIV></DIV>
<DIV>This cannot be correct, given you have 1.7B 4kB blocks. Note that</DIV>
<DIV>e2fsck time is in parallel on all OSTs.</DIV>
<DIV> </DIV>
<DIV><FONT color=#ff00ff>Sorry I don't know what you said, our filesystem is up
to 400TB, and the inode, block parameters were set as default value. As you
mentioned, a 7TB filesystem
would take on the order of 2h or less.
Is the time in parallel on all OSTs?</FONT></DIV>
<DIV> </DIV>
<DIV></DIV>
<DIV>> number of inodes: 427220992 (set as the default inode size 256)</DIV>
<DIV>> number of allocated blocks:1708867323 (set as the default block size 4096)</DIV>
<DIV>> distribution of the above on the disk: 4 OSTs on one disk</DIV>
<DIV></DIV>
<DIV>Putting 4 OSTs on a single disk doesn't make sense. A single OST</DIV>
<DIV>can be up to 8TB, and if you have multiple OSTs on the same disk(s)</DIV>
<DIV>it will cause terrible performance problems due to seeking.</DIV>
<DIV></DIV>
<DIV>> amount of RAM on server: 16GB</DIV>
<DIV>> speed of the CPU: Intel(R) Core 8 CPU</DIV>
<DIV>> speed of the disks:7200</DIV>
<DIV>> </DIV>
<DIV>> Can you give us the more details according to the parameters? And give</DIV>
<DIV>> us some suggestions to do e2fsck or make it do faster. We are worried</DIV>
<DIV>> about it may destroy the filesystem.</DIV>
<DIV>> </DIV>
<DIV>> Thank you in advanced for your help!</DIV>
<DIV></DIV>
<DIV>Sorry for your misunderstanding, but providing anything more than</DIV>
<DIV>a rough estimate of e2fsck time is the best that is possible. I</DIV>
<DIV>would estimate (excluding errors in the filesystem) a 7TB filesystem</DIV>
<DIV>would take on the order of 2h or less.</DIV>
<DIV></DIV>
<DIV>> </DIV>
<DIV>> \u53d1\u4ef6\u4eba\uff1a Andreas Dilger </DIV>
<DIV>> \u53d1\u9001\u65f6\u95f4\uff1a 2009-07-29 18:33:13 </DIV>
<DIV>> \u6536\u4ef6\u4eba\uff1a huangql </DIV>
<DIV>> \u6284\u9001\uff1a lustre-discuss </DIV>
<DIV>> \u4e3b\u9898\uff1a Re: [Lustre-discuss] How to estimate the time for e2fsck on OST </DIV>
<DIV>> </DIV>
<DIV>> On Jul 29, 2009 15:16 +0800, huangql wrote:</DIV>
<DIV>> > We want to run e2fsck on OSTs to finish them. However, as to the</DIV>
<DIV>> > running time, we should estimate how long it takes to run e2fsck on</DIV>
<DIV>> > OSTs. We hopefully to know what elements to affect the running time like</DIV>
<DIV>> > the size of OST, the average size of files and so on. Can you give us</DIV>
<DIV>> > the tips for it? And I hope to receive you email as soon as possible.</DIV>
<DIV>> The variables in your question are numerous:</DIV>
<DIV>> - size of the filesystem</DIV>
<DIV>> - number of inodes</DIV>
<DIV>> - number of allocated blocks</DIV>
<DIV>> - distribution of the above on the disk</DIV>
<DIV>> - speed of the disks</DIV>
<DIV>> - speed of the CPU</DIV>
<DIV>> - amount of RAM on server</DIV>
<DIV>> Reasonable e2fsck times (without serious filesystem problems) might</DIV>
<DIV>> take between 5 minutes and 2 hours.</DIV>
<DIV>> Cheers, Andreas</DIV>
<DIV>> --</DIV>
<DIV>> Andreas Dilger</DIV>
<DIV>> Sr. Staff Engineer, Lustre Group</DIV>
<DIV>> Sun Microsystems of Canada, Inc.</DIV>
<DIV></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> Lustre-discuss mailing list</DIV>
<DIV>> Lustre-discuss@lists.lustre.org</DIV>
<DIV>> http://lists.lustre.org/mailman/listinfo/lustre-discuss</DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>Cheers, Andreas</DIV>
<DIV>--</DIV>
<DIV>Andreas Dilger</DIV>
<DIV>Sr. Staff Engineer, Lustre Group</DIV>
<DIV>Sun Microsystems of Canada, Inc.</DIV>
<DIV></DIV>
<DIV></DIV></FONT></DIV></BODY></HTML>