I figured out my problem. It's the RAID patches that RH adds. RH adds a LOT of patches to the stock kernel. Someone suggested grabbing a stock kernel and using that, but a lot of the RH patches are ones I really want, and I don't want to sift through them carefully figuring out which ones. So, I grabbed the kernel source RPM, used rpm2cpio on it, unpacked the cpio, and then used patch -R (what a wonderful tool) to reverse the patches I didn't want out of the kernel source tree RH ships. After that, the LVM patches applied just fine. I only wanted RAID0 anyway, and LVM does that just fine by itself. :-) It works beautifully! The only thing I could ask for (and it is something that would be complicated to dp) is to allow the root filesystem to be a logical volume. A graphical (say tk or Python based) manager might be nice to, but there are already several people working on that. Thanks a LOT for providing such a neat, useful tool. Virtual memory for hard drives. It's great! One question... Is the warning about moving the physical extents of a mounted logical volume based on hard evidence, or uneasiness? As I recall from Hans's talk, there shouldn't be any problem. I think I remember that the blocks are locked from being read or written to while they're being moved. And besides, the buffer cache entries point at the logical volume anyway. Have fun (if at all possible), -- Its name is Public Opinion. It is held in reverence. It settles everything. Some think it is the voice of God. Loyalty to petrified opinion never yet broke a chain or freed a human soul. ---Mark Twain -- Eric Hopper (hopper omnifarious mn org http://omnifarious.mn.org/~hopper) --
Attachment:
pgp00000.pgp
Description: PGP signature