Gentoo Archives: gentoo-amd64

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-amd64@l.g.o
Subject: [gentoo-amd64] Re: Root on Raid and LVM - Solved
Date: Tue, 08 Nov 2005 12:49:44
Message-Id: pan.2005.11.08.12.43.34.795152@cox.net
In Reply to: [gentoo-amd64] Re: Root on Raid and LVM - Solved by Edward Middleton
1 Edward Middleton posted <4368286D.90909@××××××××××××.jp>, excerpted below,
2 on Wed, 02 Nov 2005 11:46:05 +0900:
3
4 >>It appears most aren't running into this bug, yet the number of bugs
5 >>suggests there's a fair number of users.
6 > This bug will only effect users of root on lvm2 users
7
8 BTW, I'm not fully up and working yet, but I've decided to put root
9 directly on (a partitioned) raid6, so it can be directly auto-assembled by
10 the kernel and I won't have to use an initrd/initramfs, as (I believe??) I
11 would if root was on LVM2. (The software raid howto is outdated when it
12 says Linux raid can't be partitioned. The 2.6 kernel handles that just
13 fine, but with different device numbers than the traditional
14 non-partitionable raid.)
15
16 I got 4-300 gig Seagates -- 1.2 terabyte of raw disk space (plus my
17 existing PATA drive space). One of the reasons I'm not up and running yet
18 is that I double-checked the raw drives by running badblocks -w on each
19 entire drive. That's four patterns, written out one at a time to four
20 drives, 300 gig each, then read back in and verified. 4x4x300 gig = 4.8
21 terabytes written, 4.8 terabytes read. That took me a couple days! =8^)
22 Fortunately, I didn't feel it much at all, save for the wait, because that
23 was traffic on drives I'm not yet using in production, and while it did
24 run 1 CPU to 100% for the entire period, that was mostly I/O wait, and my
25 other CPU kept up with the normal desktop stuff just fine. Anyway... it
26 was waiting for that, that I realized just how much drive space I now
27 have! =8^)
28
29 I have the raid6 partitioned three ways, my traditional root and
30 backup-root-snapshot as two partitions with the third being the big one --
31 to hold the rest of my raid6 volumes in LVM, again, for the additional
32 flexibility. There's enough space on the LVM-on-raid6 partition to keep a
33 working and a snapshot copy of everything there, too, guarding against
34 fat-fingering as well as hard drive failure. (A second copy of everything
35 means very little risk playing with reiser4 or the like, as well! =8^)
36
37 Right now, I have three raids set up (altho I haven't installed
38 filesystems on them yet), a small raid0 (mirrored) for booting, the
39 majority of the space as the three-way-partitioned raid6 mentioned above,
40 and a raid0 (striped for speed, non-redundant) for semi-volatile storage,
41 the portage tree as it can easily be resynced for recovery, /tmp, etc (no,
42 not /etc! <g>). However, after reading up on LVM and realizing it had
43 built-in striping capabilities, I may kill the raid0 and simply use
44 striped LVM directly on the physical volume partitions underneath.
45
46 Anyway... it was quite cool to realize the 2.6 kernel handles partitioned
47 raid, now, and with direct boot-time kernel raid assembly, I could run
48 root on raid6 without an initrd/initramfs! As I was dreading the
49 complexity of an initrd solution, I grabbed the opportunity to avoid it
50 and still have a raid-backed root, when I saw it! So, no root on LVM
51 here!
52
53 --
54 Duncan - List replies preferred. No HTML msgs.
55 "Every nonfree program has a lord, a master --
56 and if you use the program, he is your master." Richard Stallman in
57 http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
58
59
60 --
61 gentoo-amd64@g.o mailing list