<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Is this the same issue as at "<span class="Apple-style-span" style="font-family: Times; font-size: 15px; ">backup MDT question</span><span class="Apple-style-span" style="font-family: Helvetica; font-weight: normal; font-size: medium; ">" </span>(and follow up)</div><div><span class="Apple-tab-span" style="white-space:pre"> </span><a href="http://lists.lustre.org/pipermail/lustre-discuss/2009-April/010151.html">http://lists.lustre.org/pipermail/lustre-discuss/2009-April/010151.html</a></div><div>due to sparse files on MDT? Does tar take a lot of CPU?</div><div>Alex.</div><div><br><div><div>On May 30, 2012, at 5:02 PM, Andreas Dilger wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><blockquote type="cite"><blockquote type="cite">The tar backup of the MDT is taking a very long time. So far it has<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">backed up 1.6GB of the 5.0GB used in nine hours. In watching the tar<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">process pointers to small or average size files are backed up quickly<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">and at a consistent pace. When tar encounters a pointer/inode<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">belonging to a very large file (100GB+) the tar process stalls on that<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">file for a very long time, as if it were trying to archive the real<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">filesize amount of data rather than the pointer/inode.</blockquote></blockquote></div></blockquote></div><br></div></body></html>