*has changed the partition types without issue previously*
Also, im pretty sure fsck runs off of /etc/fstab ... not the partition
type. Running fsck for ext2 on a ext3 breaks ext3, and partition
listings don't give file system info. 'fsck -A' runs off of the fstab
file, so i dont know why it wouldn't do the same on boot. So my answer
would be fsck wouldn't hurt lvm unless the fstab file is configed
incorrectly even if the partitions are incorrectly labeled (aka make
sure you're fstab listings point to your lvm volumes and not your
devices directly).
Michael
Kevin McGehee wrote:
I'm pretty sure that's the case. As long as you don't change the
boundaries, the type can be changed non-destructively (don't quote me
on that). And even so, I wouldn't think that you could fsck it and
break it unless you were really trying... I've had partitions before
that were totally the wrong type in the partition table (like an ext3
declared as NTFS) and everything still ran fine.
Kevin
On 9/25/07, *Derek Juba* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
wrote:
Rob Sherwood wrote:
> So I just setup LVM for the first time and everything works great...
> except the guide I was following never told me to set the partition
> type of the disks to LVM (8e). My partitions are still "Linux"
(83):
> does it matter? I had a friend tell me he lost data b/c he
booted off
> a boot disk with an older version of linux and it fsck'ed his LVM
> partitions like they were plain ext2.
>
> Does anyone know if this matters?
>
> Thanks in advance,
>
> - Rob
> .
>
Isn't it possible to just change the partition type with fdisk without
losing any data?
-Derek
