[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#820788: marked as done (partman-auto: max partition size in recipe is ignored in LVM)

Your message dated Mon, 25 Nov 2024 21:24:01 +0100
with message-id <20241125212401.4bbc05184635804f5d22462b@mailbox.org>
and subject line Re: #820788 partman-auto: max partition size in recipe is ignored in LVM
has caused the Debian Bug report #820788,
regarding partman-auto: max partition size in recipe is ignored in LVM
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
820788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820788
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: partman-auto
Severity: normal

I am using following preseed scheme to partition my disks (RAID1+ LVM),
partition with highest priority "eats" all of the free space even tho it has a
max size:





d-i partman-auto-raid/recipe string \
    1 2 0 ext2 /boot                \
          /dev/sda1#/dev/sdb1       \
    .                               \
    1 2 0 lvm -                     \
          /dev/sda2#/dev/sdb2       \
    .

d-i     partman-auto/expert_recipe string        \
           boot-root ::                          \
             1024 30 1024 raid                   \
                $lvmignore{ }                    \
                $primary{ } method{ raid }       \
             .                                   \
             5000 35 -1 raid                     \
                $lvmignore{ }                    \
                $primary{ } method{ raid }       \
             .                                   \
             5000 50 10000 ext4                  \
                $defaultignore{ }                \
                $lvmok{ }                        \
                lv_name{ root }                  \
                method{ format }                 \
                format{ }                        \
                use_filesystem{ }                \
                filesystem{ ext4 }               \
                mountpoint{ / }                  \
             .                                   \
             2000 50 5000 ext4                   \
                $defaultignore{ }                \
                $lvmok{ }                        \
                lv_name{ log }                   \
                method{ format }                 \
                format{ }                        \
                use_filesystem{ }                \
                filesystem{ ext4 }               \
                mountpoint{ /var/log }           \
             .                                   \
             1024 60 1024+10% swap               \
                $defaultignore{ }                \
                $lvmok{ }                        \
                lv_name{ swap }                  \
                method{ swap }                   \
                format{ }                        \
             .


I have also tried to set up partman-auto-lvm/guided_size to both % and in GB
but none of those leave any free space on LVM

results in:

root@debian-test:~# lvs
  LV   VG     Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync
Convert
  log  rootvg -wi-ao----   1.86g
  root rootvg -wi-ao----   4.66g
  swap rootvg -wi-ao---- 129.02g

so swap partition (I assume because of it's priority) eats all free space (I've
tried "1024 60 2048" setting with same result) even tho max is set


--- End Message ---
--- Begin Message --- 
Version: 70

Mariusz Gronczewski <xani666@gmail.com> wrote:
> I have also tried to set up partman-auto-lvm/guided_size to both % and in GB
> but none of those leave any free space on LVM

A solution for this has been introduced years ago in the form of a new
dialog as

_Description: Amount of volume group to use for guided partitioning:
	You may use the whole volume group for guided partitioning, or part of it.
	If you use only part of it, or if you add more disks later, then you will
	be able to grow logical volumes later using the LVM tools, so using a
	smaller part of the volume group at installation time may offer more
	flexibility.

So closing this bug.

-- 
Holger Wansing <hwansing@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

--- End Message ---
Reply to: