| To: | Greg Cormier <gcormier@xxxxxxxxx> |
|---|---|
| Subject: | Re: Linux Software RAID 5 + XFS Multi-Benchmarks / 10 Raptors Again |
| From: | Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx> |
| Date: | Fri, 18 Jan 2008 10:58:40 -0500 (EST) |
| Cc: | linux-raid@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, Alan Piszcz <ap@xxxxxxxxxxxxx> |
| In-reply-to: | <29a863790801180743y2e90e37aj70c556dc9192a15d@mail.gmail.com> |
| References: | <alpine.DEB.0.999999.0801161105510.16168@p34.internal.lan> <29a863790801180735n379a27f1t4987686b2ec1aa50@mail.gmail.com> <alpine.DEB.0.999999.0801181036260.23565@p34.internal.lan> <29a863790801180743y2e90e37aj70c556dc9192a15d@mail.gmail.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Alpine 0.999999 (DEB 847 2007-12-06) |
On Fri, 18 Jan 2008, Greg Cormier wrote: Also, don't use ext*, XFS can be up to 2-3x faster (in many of the benchmarks). Recovery is actually easier with XFS because the repair filesystem code is built-into the kernel (you dont need a utility to fix it)-- however, there is xfs_repair (if) the in-kernel-tree part could not fix it. I have been using it for > 4-5 years? now. Also, with CoRaids (ATA over Ethernet) many of them are above 8TB and ext3 only works up to 8TB, so its not even an option any longer. Justin. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Linux Software RAID 5 + XFS Multi-Benchmarks / 10 Raptors Again, Greg Cormier |
|---|---|
| Next by Date: | RE: Repairing a possibly incomplete xfs_growfs command?, Mark Magpayo |
| Previous by Thread: | Re: Linux Software RAID 5 + XFS Multi-Benchmarks / 10 Raptors Again, Greg Cormier |
| Next by Thread: | Repairing a possibly incomplete xfs_growfs command?, Mark Magpayo |
| Indexes: | [Date] [Thread] [Top] [All Lists] |