Linux LVM users
 help / color / mirror / Atom feed
From: Spam <spam@tnonline.net>
To: Greg Freemyer <linux-lvm@sistina.com>
Subject: Re: [linux-lvm] JFS or XFS
Date: Thu Jan 15 19:02:02 2004	[thread overview]
Message-ID: <366082581.20040116010404@tnonline.net> (raw)
In-Reply-To: <1074209631.19419.24.camel@david.internal.NorcrossGroup.com>


> On Thu, 2004-01-15 at 18:22, neuron wrote:
>> reiserfs, guaranteed personally.  Especially on a mail server.

> I agree, reiserfs was tuned for handling lots of small files.  Sounds
> perfect for a mail server.

  Also,  ReiserFS  tools  are  very mature when it comes to repair and
  recover  from  damages. I do not know how the JFS/XFS tools are, but
  it  would  be  a good idea to investigate how you can repair your FS
  _if_ you end up with some sort of failure..

>> I've used jfs, I crashed it twice on purpose (network swap,
>> then disable network card), both times jfs failed to boot.  (this
>> is because it trusts it's own journal, which a lot of people love
>> about it, both times for me it was wrong..)
>> Personally I haven't had any problems with XFS though, but I haven't used it that much.
>> 

> If you go with XFS, stay away from anything older than 1.3.1.

> The 1.2 and prior releases had this really nice feature that they
> ignored the sync command (and fsync I think).

> The end result is that with a power outage or kernel lockup you could
> lose lots of work.  I had one failure on a lightly used machine that had
> a whole days activities still sitting in the OS disk cache when the
> kernel locked up.

> This is fixed in 1.3.1, 

> Greg




> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

  reply	other threads:[~2004-01-15 19:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 18:19 [linux-lvm] JFS or XFS Rajesh Saxena
2004-01-15 18:24 ` neuron
2004-01-15 18:33   ` Austin Gonyou
2004-01-15 18:46   ` Greg Freemyer
2004-01-15 19:02     ` Spam [this message]
2004-01-20 16:15       ` Steven Lembark
2004-01-15 22:38     ` Austin Gonyou
2004-01-15 19:30 ` Rajesh Saxena
2004-01-16  8:57   ` Heinz Mauelshagen
2004-01-16 17:55     ` Rajesh Saxena
2004-01-16 19:43       ` Alasdair G Kergon
2004-01-16 19:48         ` Dan Sully
2004-01-16 20:06           ` Alasdair G Kergon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=366082581.20040116010404@tnonline.net \
    --to=spam@tnonline.net \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox