<br><br><div class="gmail_quote">2008/11/19 - Tethys <span dir="ltr"><<a href="mailto:tethys@gmail.com">tethys@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
</div>Be careful here. There are likely to be people reading this list that<br>
will see that and think "I want better performance from my<br>
filesystem", and think about using ResierFS. Don't get me wrong, Hans<br>
had some nice ideas, but wasn't able to implement them in a reliable<br>
way[1]. To clarify: ReiserFS is good for losing your data. Nothing<br>
more. Avoid it at all costs.<br>
</blockquote><div><br>ReiserFS was recommended ofr filesystems with lots of small files - such as mail servers.<br>I remember using it on the SuSE mail server which I put in at the Framestore yonks ago now - as you say it<br>
was the recommended filesystem for SuSE.<br>And indeed at my last company older systems had been installed with some big RAID setups with Reiser.<br><br>I had a trip up to Aberdeen to spend a joyful day at an oil company where a filesystem had gone, using lots of nice low-level ReiserFS tools to try to repair it. Truth be told though in this case it wouldn't have mattered if it was Reiser, ext99 or FAT32 - you get a dual disk failure and data is toast.<br>
<br>Wouldn't touch it with a long bargepole these days.<br>XFS is of course the way to go (can you tell I like SGI kit?)<br><br><br><br><br><br><br> </div></div><br>