Re: switching / to lvm
On 1/26/06, Mike McCarty <[EMAIL PROTECTED]> wrote: > David Kirchner wrote: > > On 1/26/06, Mike McCarty <[EMAIL PROTECTED]> wrote: > > > >>You can play with things as you like, but I wouldn't do it. > >>I had problems with LVM and got rid of it. Over on Fedora, > >>I've only seen one say "I'm glad I used LVM", but on a regular > >>basis someone gets bitten. > > > > > > Agreed. I haven't used LVM, but if you're having problems with a flaky > > drive, adding another layer of complexity (LVM, software RAID, etc) > > won't usually end up helping. > > Well, he did say he was replacing the drive. > > [snip] > well, just to attach the answer to the thread: I tried various things ( installing a number of stock and custom kernels, generating various initrds using initramfs & yaird, chroots, grub-installs, etc... In the end, I did the following: -shrank the logical volume with my main system by about 5 gigs -did a quick server install of ubuntu dapper with manual partition -- I used the same /boot partition as I use for the main system, put the new system on the new lv, and left the main lv alone. -at boot time, manually edited the kernel stanza to pointt o my main system. - voila! it worked! Now I've permanently edited /boot/grub/menu.lst and the system seems to be booting just fine. Presumably there was some problem either with the way I was installing grub OR with the menu.lst listings I myself had tried. either way, it works now. not exactly a success, but a crude hack anyway. Matt > Mike > --
Re: switching / to lvm
David Kirchner wrote:
On 1/26/06, Mike McCarty <[EMAIL PROTECTED]> wrote:
You can play with things as you like, but I wouldn't do it.
I had problems with LVM and got rid of it. Over on Fedora,
I've only seen one say "I'm glad I used LVM", but on a regular
basis someone gets bitten.
Agreed. I haven't used LVM, but if you're having problems with a flaky
drive, adding another layer of complexity (LVM, software RAID, etc)
won't usually end up helping.
Well, he did say he was replacing the drive.
[snip]
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: switching / to lvm
On 1/26/06, Mike McCarty <[EMAIL PROTECTED]> wrote: > You can play with things as you like, but I wouldn't do it. > I had problems with LVM and got rid of it. Over on Fedora, > I've only seen one say "I'm glad I used LVM", but on a regular > basis someone gets bitten. Agreed. I haven't used LVM, but if you're having problems with a flaky drive, adding another layer of complexity (LVM, software RAID, etc) won't usually end up helping. What will more likely help is a "transparent" layer, such as a hardware RAID card.
Re: switching / to lvm
Matt Price wrote:
my /dev/hda is getting a little flaky, so I am replacing it with a new
one. I also am tired of constantly juggling partitions around ( I
made too many when I setthis ocmputer up) so I am looking to try out
lvm. I've set up a new disk as follows:
[snip]
You can play with things as you like, but I wouldn't do it.
I had problems with LVM and got rid of it. Over on Fedora,
I've only seen one say "I'm glad I used LVM", but on a regular
basis someone gets bitten.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
switching / to lvm
my /dev/hda is getting a little flaky, so I am replacing it with a new one. I also am tired of constantly juggling partitions around ( I made too many when I setthis ocmputer up) so I am looking to try out lvm. I've set up a new disk as follows: Device Boot Start End Blocks Id System /dev/hde1 * 1 31 248976 83 Linux /dev/hde2 329729778991855 Extended /dev/hde5 32972977899153+ 8e Linux LVM within the lvm I have one partition for / and so far no others (may change that e.g. to give /var its own fs). This setup will be great, I hope, but it also means that the lvm needs to be active on boot. I notice two things: 1 -- my current kernel doesn't use an initrd & doesn't have lvm support compiled into the main kernel. (I'm assuming this is "CONFIG_MD" which is set to "M" -- I don't see any other obvious config options) I think I can do this manually with yaird or mkinitrd -- am I correct in thinking so? I'd like to avoid recompiling as i use several 3rd-party modules & the suspend2 patches, which makes compilation cumbersome. 2 -- I notice that the lvm isn't recognized and activated on reboot -- I assume this is because I don't have the requisite "vgscan -ay" in my init scripts. I don't like messing witht hose manually -- I'm wondering whether I'm somehow missing the package that would have installed these scripts, or whether that package needs to be reinstalled. Haven't found an obvious candidate. Appreciate the help as always. thanks, matt -- .''`. Matt Price : :' : Debian User `. `'` & hemi-geek `- -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
