![]() |
Slackware 10.1 how to go to the testing/2.6 kernel and back again?
Dear all,
I'm running a slackware 10.1 with the 2.4 IDE kernel and LVM1. Root is on a normal EXT3 partition. I want to setup an encrypted file system (not root) with truecrypt. However truecrypt requires a 2.6 kernel. So I installed the 2.6.10 kernel from /testing. I then found out that LVM1 does not work with the 2.6 kernels. My question is: when I install the devicemapper and LVM2 packages (after removing LVM1), will I be able to return to my old 2.4 kernel with LVM1 by just removing LVM2 and re-installing LVM1? Will activating the PV/LV's with LVM2 change them, to make them incompatible with LVM1? I have a few custom written programs running on this system so I try to modify the 10.1 defaults as little as I can. Thanks for your time. Chera |
Quote:
"... Be warned that it's not always possible to revert back to lvm 1 format metadata." http://www.tldp.org/HOWTO/LVM-HOWTO/lvm2faq.html#AEN348 I suggest you post your question to the LVM mailing list to get a more definative answer. http://www.tldp.org/HOWTO/LVM-HOWTO/maillists.html This is a case where system backups will come in *real* handy! :) Good Luck. |
BSDunix, thanks for your reply. The same documents states that
"4.1.6. Does LVM 2 support VGs and LVs created with LVM 1? Yes. LVM 2 will activate and operate on VG and LVs created with LVM 1. The exception to this is snapshots created with LVM 1 - these should be removed before upgrading. Snapshots that remain after upgrading will have to be removed before their origins can be activated by LVM 2. " That seems to imply that you can run LVM1 VG/LV's with LVM2 without converting them to LVM2 format, as long as you have no snapshots, which I don't have. Also the quick start for going from LVM1 to LVM2 does not say that you need to use vgconvert to update LVM1 volumes to the LVM2 format. regards Chera |
| All times are GMT -5. The time now is 04:29 AM. |