From: Adam Talbot <talbotx@comcast.net>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Neil Brown <neilb@suse.de>,
Francois Barre <francois.barre@gmail.com>,
linux-raid@vger.kernel.org
Subject: Re: Large single raid and XFS or two small ones and EXT3?
Date: Sun, 25 Jun 2006 17:42:40 -0700 [thread overview]
Message-ID: <449F2D80.6080100@comcast.net> (raw)
In-Reply-To: <449F22D7.2090604@tmr.com>
Not exactly sure how to tune for stripe size.
What would you advise?
-Adam
Bill Davidsen wrote:
> winspeareAdam Talbot wrote:
>
>> OK, this topic I relay need to get in on.
>> I have spent the last few week bench marking my new 1.2TB, 6 disk, RAID6
>> array. I wanted real numbers, not "This FS is faster because..." I have
>> moved over 100TB of data on my new array running the bench mark
>> testing. I have yet to have any major problems with ReiserFS, EXT2/3,
>> JFS, or XFS. I have done extensive testing on all, including just
>> trying to break the file system with billions of 1k files, or a 1TB
>> file. Was able to cause some problems with EXT3 and RiserFS with the 1KB
>> and 1TB tests, respectively. but both were fixed with a fsck. My basic
>> test is to move all data from my old server to my new server
>> (whitequeen2) and clock the transfer time. Whitequeen2 has very little
>> storage. The NAS's 1.2TB of storage is attached via iSCSI and a cross
>> over cable to the back of whitequeen2. The data is 100GB of user's
>> files(1KB~2MB), 50GB of MP3's (1MB~5MB) and the rest is movies and
>> system backups 600MB~2GB. Here is a copy of my current data sheet,
>> including specs on the servers and copy times, my numbers are not
>> perfect, but they should give you a clue about speeds... XFS wins.
>>
>>
>
> In many (most?) cases I'm a lot more concerned about filesystem
> stability than performance. That is, I want the fastest <reliable>
> filesystem. With ext2 and ext3 I've run multiple multi-TB machines
> spread over four time zones, and not had a f/s problem updating ~1TB/day.
>
>> The computer: whitequeen2
>> AMD Athlon64 3200 (2.0GHz)
>> 1GB Corsair DDR 400 (2X 512MB's running in dual DDR mode)
>> Foxconn 6150K8MA-8EKRS motherboard
>> Off brand case/power supply
>> 2X os disks, software raid array, RAID 1, Maxtor 51369U3, FW DA620CQ0
>> Intel pro/1000 NIC
>> CentOS 4.3 X86_64 2.6.9
>> Main app server, Apache, Samba, NFS, NIS
>>
>> The computer: nas
>> AMD Athlon64 3000 (1.8GHz)
>> 256MB Corsair DDR 400 (2X 128MB's running in dual DDR mode)
>> Foxconn 6150K8MA-8EKRS motherboard
>> Off brand case/power supply and drive cages
>> 2X os disks, software raid array, RAID 1, Maxtor 51369U3, FW DA620CQ0
>> 6X software raid array, RAID 6, Maxtor 7V300F0, FW VA111900
>> Gentoo linux. X86_64 2.6.16-gentoo-r9
>> System built very lite, only built as an iSCSI based NAS.
>>
>> EXT3
>> Config=APP+NFS-->NAS+iSCSI
>> RAID6 64K chunk
>> [root@whitequeen2 tmp]# time tar cf - . | (cd /data ; tar xf - )
>> real 371m29.802s
>> user 1m28.492s
>> sys 46m48.947s
>> /dev/sdb1 1.1T 371G 674G 36% /data
>> 6.192 hours @ 61,262M/hour or 1021M/min or 17.02M/sec
>>
>>
>> EXT2
>> Config=APP+NFS-->NAS+iSCSI
>> RAID6 64K chunk
>> [root@whitequeen2 tmp]# time tar cf - . | ( cd /data/ ; tar xf - )
>> real 401m48.702s
>> user 1m25.599s
>> sys 30m22.620s
>> /dev/sdb1 1.1T 371G 674G 36% /data
>> 6.692 hours @ 56,684M/hour or 945M/min or 15.75M/sec
>>
> Did you tune the extN filesystems to the stripe size of the raid?
>
next prev parent reply other threads:[~2006-06-26 0:42 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 19:11 Large single raid and XFS or two small ones and EXT3? Chris Allen
2006-06-22 19:16 ` Gordon Henderson
2006-06-22 19:23 ` H. Peter Anvin
2006-06-22 19:58 ` Chris Allen
2006-06-22 20:00 ` Chris Allen
2006-06-23 8:59 ` PFC
2006-06-23 9:26 ` Francois Barre
2006-06-23 12:50 ` Chris Allen
2006-06-23 13:14 ` Gordon Henderson
2006-06-23 13:30 ` Francois Barre
2006-06-23 14:46 ` Martin Schröder
2006-06-23 14:59 ` Francois Barre
2006-06-23 15:13 ` Bill Davidsen
2006-06-23 15:34 ` Francois Barre
2006-06-23 19:49 ` Nix
2006-06-24 5:19 ` Neil Brown
2006-06-24 7:59 ` Adam Talbot
2006-06-24 9:34 ` David Greaves
2006-06-24 22:52 ` Adam Talbot
2006-06-25 13:06 ` Joshua Baker-LePain
2006-06-28 3:45 ` I need a PCI V2.1 4 port SATA card Guy
2006-06-28 4:29 ` Brad Campbell
2006-06-28 10:20 ` Justin Piszcz
2006-06-28 11:55 ` Christian Pernegger
2006-06-28 11:59 ` Gordon Henderson
2006-06-29 18:45 ` Bill Davidsen
2006-06-28 19:38 ` Justin Piszcz
2006-06-28 12:12 ` Petr Vyskocil
2006-06-25 14:51 ` Large single raid and XFS or two small ones and EXT3? Adam Talbot
2006-06-25 20:35 ` Chris Allen
2006-06-25 23:57 ` Bill Davidsen
2006-06-26 0:42 ` Adam Talbot [this message]
2006-06-26 14:03 ` Bill Davidsen
2006-06-24 12:40 ` Justin Piszcz
2006-06-26 0:06 ` Bill Davidsen
2006-06-26 8:06 ` Justin Piszcz
2006-06-23 15:17 ` Chris Allen
2006-06-23 14:01 ` Al Boldi
2006-06-23 16:06 ` Andreas Dilger
2006-06-23 16:41 ` Christian Pedaschus
2006-06-23 16:46 ` Christian Pedaschus
2006-06-23 19:53 ` Nix
2006-06-23 16:21 ` Russell Cattelan
2006-06-23 18:19 ` Tom Vier
2006-06-27 12:05 ` Large single raid... - XFS over NFS woes Dexter Filmore
2006-06-23 19:48 ` Large single raid and XFS or two small ones and EXT3? Nix
2006-06-25 19:13 ` David Rees
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=449F2D80.6080100@comcast.net \
--to=talbotx@comcast.net \
--cc=davidsen@tmr.com \
--cc=francois.barre@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).