On 24/04/2013 10:24, Neil Bothwick wrote: > On Wed, 24 Apr 2013 01:22:37 -0400, Walter Dnes wrote: > >> I have mix of various sizes. The best feature about ReiserFS is that >> it doesn't do inodes, so I don't have to be psychic about my future file >> mix when I format the partition. For that reason alone, I'm tempted to >> stay with ReiserFS3. I'm aware of the booby traps... >> >> - *NEVER EVER* have an uncompressed ReiserFS image on a ReiserFS >> partition >> >> - avoid Postfix and Qmail > > Why? I ask because I have a mail server with reiserfs on the mail spool, > it's been running for several years and behaved impeccably, but if there > is a good reason to switch, I will.
It's one of those maybe-it-is, maybe-it-isn't scenarios. Wiki has a pretty accurate description of the scene wrt mail spools: http://en.wikipedia.org/wiki/ReiserFS#Criticism Personally, I dunno. Yes, it could be an issue but it's not one I've actually seen rear it's head. I suspect Walter has an unfair opinion tainted my a few personal bad experiences (but that can happen with any system and software). His first statement though is very good advice. Never store a reiser image on a feiser fs, and never use reiser in a VM on a host fs that is also reiser. The reason is what happens when you try fsck it - reiser metadata (unlike ext*) is not all in fixed pre-determined locations on disk, so fsck can employ heuristics to go and look for it's metadata. If it finds it's own metadata and also the metadata in the stored image, it can't tell them apart. The results of that are not pretty. -- Alan McKinnon alan.mckin...@gmail.com
