Partman lvm doesn't keep data
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
partman-auto (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hi,
In preseeding lvm configurations with recipe files, I've found that you cannot specify:
method{ keep } on a partition when installing. When using this specification, all it does is go into a loop on the "Starting up the Partitioner" screen.
Interestingly enough, I've found that during this loop, if I chvt 2 and run fsck.ext3 /dev/mapper/
Output from fsck:
fsck.ext3 -y /dev/mapper/
e2fsck 1.41.4 (27-Jan-2009)
fsck.ext3: Superblock invalid, trying backup blocks...
/dev/mapper/
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #30 (32254, counted=16194).
Fix? yes
Free blocks count wrong for group #924 (32254, counted=32253).
Fix? yes
Free blocks count wrong (31901196, counted=31885135).
Fix? yes
Free inodes count wrong for group #30 (8192, counted=8048).
Fix? yes
Directories count wrong for group #30 (0, counted=4).
Fix? yes
Free inodes count wrong for group #924 (8192, counted=8191).
Fix? yes
Directories count wrong for group #924 (0, counted=1).
Fix? yes
Free inodes count wrong (8118261, counted=8118116).
Fix? yes
/dev/mapper/
/dev/mapper/
Same behavior in Jaunty and Intrepid, have not tried Karmic yet.
This happens every time. I've found that by putting a script into /lib/partman/
Recipe used to configure the drive initially:
1000 1000 1000 ext3
$primary{ }
$bootable{ }
$
method{ format }
format{ }
use_
filesystem{ ext3 }
mountpoint{ /boot } .
5000 100000 -1 lvm
$
device{ /dev/sda }
vg_name{ vg00 }
method{ lvm } .
5000 10000 10000 ext3
$lvmok{ }
in_vg{ vg00 }
lv_name{ root }
method{ format }
format{ }
use_
filesystem{ ext3 }
mountpoint{ / } .
3000 10000 4000 ext3
$lvmok{ }
in_vg{ vg00 }
lv_name{ var }
method{ format }
format{ }
use_
filesystem{ ext3 }
mountpoint{ /var } .
2048 10000 2048 linux-swap
$lvmok{ }
in_vg{ vg00 }
lv_name{ swap }
method{ swap }
format{ } .
1000 10000 -1 ext3
$lvmok{ }
in_vg{ vg00 }
lv_name{ local }
method{ format }
format{ }
use_
filesystem{ ext3 }
mountpoint{ /local } .
5000 10000 10000 ext3
$lvmok{ }
in_vg{ vg00 }
lv_name{ cache }
method{ format }
format{ }
use_
filesystem{ ext3 }
mountpoint{ /usr/vice/cache } .
Recipe to keep the /local partition:
1000 1000 1000 ext3
$primary{ }
$bootable{ }
$
method{ format }
format{ }
use_
filesystem{ ext3 }
mountpoint{ /boot } .
5000 100000 -1 lvm
$
device{ /dev/sda }
vg_name{ vg00 }
method{ lvm } .
5000 10000 10000 ext3
$lvmok{ }
in_vg{ vg00 }
lv_name{ root }
method{ format }
format{ }
use_
filesystem{ ext3 }
mountpoint{ / } .
3000 10000 4000 ext3
$lvmok{ }
in_vg{ vg00 }
lv_name{ var }
method{ format }
format{ }
use_
filesystem{ ext3 }
mountpoint{ /var } .
2048 10000 2048 linux-swap
$lvmok{ }
in_vg{ vg00 }
lv_name{ swap }
method{ swap }
format{ } .
1000 10000 -1 ext3
$lvmok{ }
in_vg{ vg00 }
lv_name{ local }
method{ keep }
use_
filesystem{ ext3 }
mountpoint{ /local } .
5000 10000 10000 ext3
$lvmok{ }
in_vg{ vg00 }
lv_name{ cache }
method{ format }
format{ }
use_
filesystem{ ext3 }
mountpoint{ /usr/vice/cache } .
I also get prompted each time by a dialog about whether or not I want to write the changes to disks. I have not found a value yet that I can pressed this away with.
description: | updated |
affects: | ubuntu → debian-installer (Ubuntu) |
affects: | debian-installer (Ubuntu) → partman-auto (Ubuntu) |