From: maarten <maarten@ultratux.net>
To: linux-raid@vger.kernel.org
Subject: Re: Spares and partitioning huge disks
Date: Sat, 8 Jan 2005 20:01:09 +0100 [thread overview]
Message-ID: <200501082001.09317.maarten@ultratux.net> (raw)
In-Reply-To: <200501081749.32816.maarten@ultratux.net>
On Saturday 08 January 2005 17:49, maarten wrote:
> On Saturday 08 January 2005 15:52, Frank van Maarseveen wrote:
> > On Fri, Jan 07, 2005 at 04:57:35PM -0500, Guy wrote:
> > > His plan is to split the disks into 6 partitions.
> > > Each of his six RAID5 arrays will only use 1 partition of each physical
> > > disk.
> > > If he were to lose a disk, all 6 RAID5 arrays would only see 1 failed
> > > disk. If he gets 2 read errors, on different disks, at the same time,
> > > he has a 1/6 chance they would be in the same array (which would be
> > > bad). His plan is to combine the 6 arrays with LVM or a linear array.
> >
> > Intriguing setup. Do you think this actually improves the reliability
> > with respect to disk failure compared to creating just one large RAID5
> > array?
As the system is now online again, busy copying, I can show the exact config:
dozer:~ # fdisk -l /dev/hde
Disk /dev/hde: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hde1 1 268 2152678+ fd Linux raid autodetect
/dev/hde2 269 331 506047+ fd Linux raid autodetect
/dev/hde3 332 575 1959930 fd Linux raid autodetect
/dev/hde4 576 30401 239577345 5 Extended
/dev/hde5 576 5439 39070048+ fd Linux raid autodetect
/dev/hde6 5440 10303 39070048+ fd Linux raid autodetect
/dev/hde7 10304 15167 39070048+ fd Linux raid autodetect
/dev/hde8 15168 20031 39070048+ fd Linux raid autodetect
/dev/hde9 20032 24895 39070048+ fd Linux raid autodetect
/dev/hde10 24896 29759 39070048+ fd Linux raid autodetect
/dev/hde11 29760 30401 5156833+ 83 Linux
dozer:~ # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid5] [multipath]
read_ahead 1024 sectors
md1 : active raid1 hdg2[1] hde2[0]
505920 blocks [2/2] [UU]
md0 : active raid1 hdg1[1] hde1[0]
2152576 blocks [4/2] [UU__]
md2 : active raid1 sdb2[0] sda2[1]
505920 blocks [2/2] [UU]
md3 : active raid5 sdb5[2] sda5[3] hdg5[1] hde5[0]
117209856 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
md4 : active raid5 sdb6[2] sda6[3] hdg6[1] hde6[0]
117209856 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
md5 : active raid5 sdb7[2] sda7[3] hdg7[1] hde7[0]
117209856 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
md6 : active raid5 sdb8[2] sda8[3] hdg8[1] hde8[0]
117209856 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
md7 : active raid5 sdb9[2] sda9[3] hdg9[1] hde9[0]
117209856 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
md8 : active raid5 sdb10[2] sda10[3] hdg10[1] hde10[0]
117209856 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
# Where md0 is "/" (temporary degraded), and md1 and md2 are swap.
# The md3 through md8 are the big arrays that are part of LVM.
dozer:~ # pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- ACTIVE PV "/dev/md3" of VG "lvm_video" [111.72 GB / 0 free]
pvscan -- ACTIVE PV "/dev/md4" of VG "lvm_video" [111.72 GB / 0 free]
pvscan -- ACTIVE PV "/dev/md5" of VG "lvm_video" [111.72 GB / 0 free]
pvscan -- ACTIVE PV "/dev/md6" of VG "lvm_video" [111.72 GB / 0 free]
pvscan -- ACTIVE PV "/dev/md7" of VG "lvm_video" [111.72 GB / 0 free]
pvscan -- ACTIVE PV "/dev/md8" of VG "lvm_video" [111.72 GB / 0 free]
pvscan -- total: 6 [670.68 GB] / in use: 6 [670.68 GB] / in no VG: 0 [0]
dozer:~ # vgdisplay
--- Volume group ---
VG Name lvm_video
VG Access read/write
VG Status available/resizable
VG # 0
MAX LV 256
Cur LV 1
Open LV 1
MAX LV Size 2 TB
Max PV 256
Cur PV 6
Act PV 6
VG Size 670.31 GB
PE Size 32 MB
Total PE 21450
Alloc PE / Size 21450 / 670.31 GB
Free PE / Size 0 / 0
VG UUID F0EF61-uu4P-cnCq-6oQ6-CO5n-NE9g-5xjdTE
dozer:~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/md0 1953344 1877604 75740 97% /
/dev/lvm_video/mythtv
702742528 42549352 660193176 7% /mnt/store
# As of yet there are no spares. This is a todo, the most important thing is
to get the app back in working state now. I'll probably make a /usr md
device in future from hdX3, as "/" is completely full. This was because of
legacy constraints, migrating drives...
Maarten
next prev parent reply other threads:[~2005-01-08 19:01 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 14:16 Spares and partitioning huge disks maarten
2005-01-06 16:46 ` Guy
2005-01-06 17:08 ` maarten
2005-01-06 17:31 ` Guy
2005-01-06 18:18 ` maarten
[not found] ` <41DD83DA.9040609@h3c.com>
2005-01-06 19:42 ` maarten
2005-01-07 20:59 ` Mario Holbe
2005-01-07 21:57 ` Guy
2005-01-08 10:22 ` Mario Holbe
2005-01-08 12:19 ` maarten
2005-01-08 16:33 ` Guy
2005-01-08 16:58 ` maarten
2005-01-08 14:52 ` Frank van Maarseveen
2005-01-08 15:50 ` Mario Holbe
2005-01-08 16:32 ` Guy
2005-01-08 17:16 ` maarten
2005-01-08 18:55 ` Guy
2005-01-08 19:25 ` maarten
2005-01-08 20:33 ` Mario Holbe
2005-01-08 23:01 ` maarten
2005-01-09 10:10 ` Mario Holbe
2005-01-09 16:23 ` Guy
2005-01-09 16:36 ` Michael Tokarev
2005-01-09 17:52 ` Peter T. Breuer
2005-01-09 17:59 ` Michael Tokarev
2005-01-09 18:34 ` Peter T. Breuer
2005-01-09 20:28 ` Guy
2005-01-09 20:47 ` Peter T. Breuer
2005-01-10 7:19 ` Peter T. Breuer
2005-01-10 9:05 ` Guy
2005-01-10 9:38 ` Peter T. Breuer
2005-01-10 12:31 ` Peter T. Breuer
2005-01-10 13:19 ` Peter T. Breuer
2005-01-10 18:37 ` Peter T. Breuer
2005-01-11 11:34 ` Peter T. Breuer
2005-01-08 23:09 ` Guy
2005-01-09 0:56 ` maarten
2005-01-13 2:05 ` Neil Brown
2005-01-13 4:55 ` Guy
2005-01-13 9:27 ` Peter T. Breuer
2005-01-13 15:53 ` Guy
2005-01-13 17:16 ` Peter T. Breuer
2005-01-13 20:40 ` Guy
2005-01-13 23:32 ` Peter T. Breuer
2005-01-14 2:43 ` Guy
2005-01-08 16:49 ` maarten
2005-01-08 19:01 ` maarten [this message]
2005-01-10 16:34 ` maarten
2005-01-10 16:36 ` Gordon Henderson
2005-01-10 17:10 ` maarten
2005-01-16 16:19 ` 4 questions. Chieftec chassis case CA-01B, resync times, selecting ide driver module loading, raid5 :2 drives on same ide channel Mitchell Laks
2005-01-16 17:53 ` Gordon Henderson
2005-01-16 18:22 ` Maarten
2005-01-16 19:39 ` Guy
2005-01-16 20:55 ` Maarten
2005-01-16 21:58 ` Guy
2005-01-10 17:13 ` Spares and partitioning huge disks Guy
2005-01-10 17:35 ` hard disk re-locates bad block on read Guy
2005-01-11 14:34 ` Tom Coughlan
2005-01-11 22:43 ` Guy
2005-01-12 13:51 ` Tom Coughlan
2005-01-10 18:24 ` Spares and partitioning huge disks maarten
2005-01-10 20:09 ` Guy
2005-01-10 21:21 ` maarten
2005-01-11 1:04 ` maarten
2005-01-10 18:40 ` maarten
2005-01-10 19:41 ` Guy
2005-01-12 11:41 ` RAID-6 Gordon Henderson
2005-01-13 2:11 ` RAID-6 Neil Brown
2005-01-15 16:12 ` RAID-6 Gordon Henderson
2005-01-17 8:04 ` RAID-6 Turbo Fredriksson
2005-01-11 10:09 ` Spares and partitioning huge disks KELEMEN Peter
2005-01-09 19:33 ` Frank van Maarseveen
2005-01-09 21:26 ` maarten
2005-01-09 22:29 ` Frank van Maarseveen
2005-01-09 23:16 ` maarten
2005-01-10 8:15 ` Frank van Maarseveen
2005-01-14 17:29 ` Dieter Stueken
2005-01-14 17:46 ` maarten
2005-01-14 19:14 ` Derek Piper
2005-01-15 0:13 ` Michael Tokarev
2005-01-15 9:34 ` Peter T. Breuer
2005-01-15 9:54 ` Mikael Abrahamsson
2005-01-15 10:31 ` Brad Campbell
2005-01-15 11:10 ` Mikael Abrahamsson
2005-01-15 10:33 ` Peter T. Breuer
2005-01-15 11:07 ` Mikael Abrahamsson
2005-01-09 23:20 ` Guy
2005-01-10 7:42 ` Gordon Henderson
2005-01-10 9:03 ` Guy
2005-01-10 12:21 ` Stats... [RE: Spares and partitioning huge disks] Gordon Henderson
2005-01-10 0:42 ` Spares and partitioning huge disks Guy
-- strict thread matches above, loose matches on Subject: below --
2005-01-13 9:53 Bene Martin
2005-01-13 10:11 ` Peter T. Breuer
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=200501082001.09317.maarten@ultratux.net \
--to=maarten@ultratux.net \
--cc=linux-raid@vger.kernel.org \
/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).