<quote name="Michael Torrie" date="Thu, 9 Sep 2010 at 09:04 -0600"> > On 09/09/2010 07:42 AM, Robert LeBlanc wrote: > > Maybe not the cleanest, but I tried LVM mirror and didn't like it so much. > > What I did was put in a new drive and set up mdadm with raid 1 and a missing > > drive. Then I pvmoved the LV to the MD device. As soon as it was done I > > pvremoved the old disk and added it to the MD raid set. There is a period of > > time that you are vulnerable while the raid set syncs. After I did the move > > I had to remove one of the disk and it is still running happily. I intend to > > put the other disk back in once I move all my MythTV stuff to my ESXi > > server. Then it will be as easy as just syncing the disks again. > > I guess I'm a weird one that never bothers to do Raid or LVM with my > mythtv server. I might do RAID-1 sometime. Myth itself eliminates the
Ya, I'm the same. If I lose all my myth recordings then it's not the end of the world. Maybe a backup of the recording schedules portion of the database, then all them shows can just reaccumulate anyway. ;) > need to do any LVM, really as it can easily handle multiple disks of > various sizes. Of course you don't get the speed increase from > striping, but I don't need that. If my myth disks get full or need > replacing, I just rsync the contents to a new disk, then mount the new > disk into the same location as the old disk and Myth just happily > accommodates the increased space. In my particular case, I was moving the root fs. Yes it was to increase my storage space, but as it was, my root fs was sitting on a small disk as it is small, and I had two big disks, all in lvm. What I wanted then was to replace the small root disk with a larger one. lvm is of course perfect for doing this type of thing. To clarify I did not have a problem with pvmove, it worked beautifully. AFTER the move was complete I went to remove the drive and the next boot failed because the 'new' drive failed. What would have been really nice is to have the old drive remain a mirror, so I could have just put it back in and have it work again and chuck the no-good new drive. I'll have to look into restoring past lvm states thing, not the most straightforward solution, but the _data_ is still on the old pv. (well, not anymore, I did a reinstall, but for future reference). I'll dig deeper into that illusive pvmove mirror option. It seems there should be a way to have mirroring on a pv level, though, and not have to have the lvs worry about the mirroring individually, but just have everything on the pv just have mirroring. Hey, and hotpluggable, too! Like you have a vg, in it several pv, and a few lv. The lv fit nicely on half the pv, the other half become automatic mirrors. If a drive fails, yank and replace, create and add the pv to the vg, and automatically starts using that new pv as a mirror. Could lvm do this? Von Fugal -- Government is a disease that masquerades as its own cure -- Robert Lefevre
signature.asc
Description: Digital signature
-------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
