From: "Anthony W. Marino" <anthony@AWMObjects.com>
To: linux-lvm@sistina.com, Steve Wray <steve.wray@paradise.net.nz>
Subject: Re: [linux-lvm] LVM System
Date: Mon Mar 4 17:50:02 2002 [thread overview]
Message-ID: <auto-000020002756@front1.mail.megapathdsl.net> (raw)
In-Reply-To: <NBBBKLKHMJHIJLHOGAOJIEFNJFAA.steve.wray@paradise.net.nz>
On Monday 04 March 2002 06:39 pm, Steve Wray wrote:
> I'd recommend ext3 with data journalling for sensitive
> filesystems. Its slower than XFS but (seems to) scale better with
> striping and large files. XFS performance (seems to) fall off
> very rapidly as file size exceeds buffer size.
>
> XFS only journals metadata. So on event of a crash,
> the filesystem structure will (likely) be sound, but theres
> no guarantee that the data blocks will be uncorrupted!!!
>
> XFS is very nice tho, in that volumes and filesystems can
> be grown with no downtime at all (without even unmounting).
>
> You might want to do some benchmarking before committing
> to a build (thats recently saved my butt actually).
It was recommended to me that all large file systems have best performance
with XFS.
> > -----Original Message-----
> > From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On
> > Behalf Of Anthony W. Marino
> > Sent: Tuesday, 5 March 2002 10:39 a.m.
> > To: linux-lvm@sistina.com
> > Subject: [linux-lvm] LVM System
> >
> >
> > Any thoughts or articles that would be usefull in determining the quality
> > on the following combination would be greatly appreciated:
> >
> > LVM 1.x
> > 3Ware 7800 Raid Controller
> > Maxtor 40GB harddrives
> > XFS Journalling FS
> > SuSE 2.4.18+ Linux
> >
> >
> > Thank You,
> > Anthony
> >
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
next prev parent reply other threads:[~2002-03-04 17:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 15:39 [linux-lvm] LVM System Anthony W. Marino
2002-03-04 15:51 ` lembark
2002-03-04 16:03 ` Anthony W. Marino
2002-03-04 16:00 ` Theo Van Dinter
2002-03-04 16:07 ` Anthony W. Marino
2002-03-04 16:11 ` Anthony W. Marino
2002-03-04 16:27 ` Theo Van Dinter
2002-03-04 16:39 ` Anthony W. Marino
2002-03-04 21:21 ` Theo Van Dinter
2002-03-04 21:36 ` Anthony W. Marino
2002-03-04 16:12 ` Anthony W. Marino
2002-03-04 17:39 ` Steve Wray
2002-03-04 17:50 ` Anthony W. Marino [this message]
2002-03-04 18:01 ` Steve Wray
2002-03-04 18:12 ` Austin Gonyou
2002-03-04 18:23 ` Steve Wray
2002-03-04 18:32 ` Austin Gonyou
2002-03-04 18:38 ` Steve Wray
2002-03-04 18:46 ` Goetz Bock
2002-03-04 19:58 ` Petro
2002-03-04 17:53 ` Austin Gonyou
2002-03-04 18:18 ` Anthony W. Marino
2002-03-04 18:39 ` Goetz Bock
2002-03-04 18:47 ` Anthony W. Marino
2002-03-04 18:51 ` Goetz Bock
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=auto-000020002756@front1.mail.megapathdsl.net \
--to=anthony@awmobjects.com \
--cc=linux-lvm@sistina.com \
--cc=steve.wray@paradise.net.nz \
/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