From: Brad Campbell <brad@wasp.net.au>
To: Stephan van Hienen <raid@a2000.nu>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid5 code ok with 2TB + ?
Date: Sun, 28 Nov 2004 15:28:25 +0400 [thread overview]
Message-ID: <41A9B659.2080703@wasp.net.au> (raw)
In-Reply-To: <Pine.LNX.4.61.0411281215310.17548@adsl.a2000.nu>
Stephan van Hienen wrote:
> On Sun, 28 Nov 2004, Brad Campbell wrote:
>
>> I hope so, I have been using it on a 2.2TB raid-5 for months now. (I
>> have completely filled the partition and e2fsck it monthly so I would
>> hope any glitches should have surfaced by now)
>
>
> ok looks ok
> when i tried 2.3TB last year it failed within a few days (data written
> to the 2TB+ was written to the first part (0-0.3TB)
>
> btw which filesystem are you using ?
> (and which stripesize?)
Ext3 and ...
brad@srv:~$ sudo mdadm --misc --detail /dev/md0
/dev/md0:
Version : 00.90.01
Creation Time : Sun May 2 18:02:14 2004
Raid Level : raid5
Array Size : 2206003968 (2103.81 GiB 2258.95 GB)
Device Size : 245111552 (233.76 GiB 250.99 GB)
Raid Devices : 10
Total Devices : 10
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sun Nov 28 06:44:04 2004
State : clean
Active Devices : 10
Working Devices : 10
Failed Devices : 0
Spare Devices : 0
Layout : left-asymmetric
Chunk Size : 128K
UUID : 05cc3f43:de1ecfa4:83a51293:78015f1e
Events : 0.1031147
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/devfs/scsi/host0/bus0/target0/lun0/part1
1 8 17 1 active sync /dev/devfs/scsi/host1/bus0/target0/lun0/part1
2 8 33 2 active sync /dev/devfs/scsi/host2/bus0/target0/lun0/part1
3 8 49 3 active sync /dev/devfs/scsi/host3/bus0/target0/lun0/part1
4 8 65 4 active sync /dev/devfs/scsi/host4/bus0/target0/lun0/part1
5 8 81 5 active sync /dev/devfs/scsi/host5/bus0/target0/lun0/part1
6 8 97 6 active sync /dev/devfs/scsi/host6/bus0/target0/lun0/part1
7 8 113 7 active sync /dev/devfs/scsi/host7/bus0/target0/lun0/part1
8 8 129 8 active sync /dev/sdi1
9 8 145 9 active sync /dev/sdj1
--
Brad
/"\
Save the Forests \ / ASCII RIBBON CAMPAIGN
Burn a Greenie. X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2004-11-28 11:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 10:48 raid5 code ok with 2TB + ? Stephan van Hienen
2004-11-28 10:57 ` Brad Campbell
2004-11-28 11:19 ` Stephan van Hienen
2004-11-28 11:28 ` Brad Campbell [this message]
2004-11-28 18:19 ` Guy
2004-11-28 19:20 ` Brad Campbell
2004-11-28 20:17 ` raid5 code ok with 2TB + ? NEGATIVE :( Stephan van Hienen
2004-11-28 20:27 ` Stephan van Hienen
2004-11-28 20:45 ` Stephan van Hienen
2004-11-28 23:34 ` raid5 code ok with 2TB + ? Stephan van Hienen
2004-11-29 4:49 ` Guy
2004-11-29 8:33 ` Stephan van Hienen
2004-11-29 8:51 ` raid5 slow Stephan van Hienen
2004-11-29 17:13 ` Guy
2004-11-29 18:11 ` Stephan van Hienen
2004-11-30 0:06 ` raid5 slow (looks like 2.6 problem) Stephan van Hienen
2004-11-30 0:30 ` raid5 slow Neil Brown
2004-11-30 0:50 ` Stephan van Hienen
2004-11-30 19:37 ` Stephan van Hienen
2004-11-30 23:26 ` Neil Brown
2004-11-30 23:39 ` Stephan van Hienen
2004-11-30 23:55 ` Stephan van Hienen
2004-12-01 19:23 ` raid5 slow (test on another system) Stephan van Hienen
2004-12-01 22:21 ` Stephan van Hienen
2004-12-02 22:01 ` Stephan van Hienen
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=41A9B659.2080703@wasp.net.au \
--to=brad@wasp.net.au \
--cc=linux-raid@vger.kernel.org \
--cc=raid@a2000.nu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.