Hi Guillaume, When I run analyze-my-lvm from mindi 2.08-2-1 on my amd64 sid test system, I get the attached result. All sizes in the created file look correct to me and everything gets created the rigt size upon restore, so I can't really reproduce this on my end.
Now, you would certainly not have gone and written the patch you sent through (Thanks for that btw!), if you weren't experiencing problems with this. ;-) I am just wondering in what context. Was this maybe a problem that was fixed in the LVM tools between the version in sarge and the version in sid? Could you think of anything else? It would be great if you could give me some more info on this and maybe you could even test the latest version yourself and see whether the problem is gone for you? Cheers, Andree On Wed, 2005-08-31 at 15:20 +0200, guillaume pernot wrote: > Package: mindi > Version: 1.04-4 > Severity: normal > > > lvdisplay and vgdisplay report decimal sizes that lvcreate and vgcreate > can't understand. > > with '-c' option, I was able to restore my lvm volumes. > > the enclosed patch needs also a patch to mondo : i'll follow up the bts > number as soon as I get it. > > cheers, > guillaume pernot > > -- System Information: > Debian Release: 3.1 > Architecture: i386 (i686) > Kernel: Linux 2.4.28-686 > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > > Versions of packages mindi depends on: > ii bzip2 1.0.2-7 high-quality block-sorting file > co > ii file 4.12-1 Determines file type using > "magic" > ii gawk 1:3.1.4-2 GNU awk, a pattern scanning and > pr > ii mindi-busybox 1.00-4 Collection of shell utilities in > a > ii mindi-kernel 2.4.27-2 failsafe Linux kernel for > Mindi/Mo > ii mindi-partimagehack 0.6.2-4 disk partition imaging utility > for > ii mkisofs 4:2.01+01a01-2 Creates ISO-9660 CD-ROM > filesystem > ii ms-sys 1.1.3-1 Write a Microsoft compatible > boot > ii nano 1.2.4-5 free Pico clone with some new > feat > ii parted 1.6.21-1 The GNU Parted disk partition > resi > ii syslinux 2.11-0.1 Bootloader for Linux/i386 using > MS > > -- no debconf information -- Andree Leidenfrost Sydney - Australia
/sbin/lvmdiskscan /sbin/lvm i=2 LVM version >= 2.0 found. Just before you extrapolate mountlist to include RAID partitions, extrapolate it to include the following LVM drives and partitions:- >>>>> /dev/hda5 /dev/md1 To get started, type:- (insmod dm-mod) (insmod dm_mod) # lvm vgchange -an # echo y | lvm pvcreate -ff /dev/hda5 # echo y | lvm pvcreate -ff /dev/md1 # lvm vgscan; echo Create and activate the VG's (volume groups). # lvm vgcreate Debian -l 0 -p 0 -s 4m /dev/hda5 # lvm vgchange -a y Debian # lvm vgcreate Server -l 0 -p 0 -s 4m /dev/md1 # lvm vgchange -a y Server Finally, create the LV's (logical volumes). # lvm lvcreate -L 1024m -r 0 -n root Debian # lvm lvcreate -L 2048m -r 0 -n tmp Debian # lvm lvcreate -L 2048m -r 0 -n var Debian # lvm lvcreate -L 3072m -r 0 -n usr Debian # lvm lvcreate -L 51200m -r 0 -n home Debian # lvm lvcreate -L 2048m -r 0 -n srv Server # lvm vgscan Now you may format the LV's:- (mkfs -t foo /dev/Debian/root or something like that) (mkfs -t foo /dev/Debian/tmp or something like that) (mkfs -t foo /dev/Debian/var or something like that) (mkfs -t foo /dev/Debian/usr or something like that) (mkfs -t foo /dev/Debian/home or something like that) (mkfs -t foo /dev/Server/srv or something like that) Finally, to shut down and delete the volumes, do this:- (lvm lvremove -f /dev/Debian/root) (lvm lvremove -f /dev/Debian/tmp) (lvm lvremove -f /dev/Debian/var) (lvm lvremove -f /dev/Debian/usr) (lvm lvremove -f /dev/Debian/home) (lvm lvremove -f /dev/Server/srv) (lvm vgchange -a n Debian) (lvm vgchange -a n Server) (lvm vgremove Debian) (lvm vgremove Server) (rmmod dm-mod & rmmod dm_mod & )
signature.asc
Description: This is a digitally signed message part
