<div dir="ltr"><div dir="ltr"></div>Hi,<div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 27, 2021 at 3:00 PM Sreyan Chakravarty <<a href="mailto:sreyan32@gmail.com">sreyan32@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>I have just installed a new Fedora 33 KDE system. </div><div><br></div><div>So this is my layout:</div><div><br></div><div><br></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
</span><br>sda 8:0 0 931.5G 0 disk <br>├─sda1 8:1 0 512M 0 part /boot/efi
<br>├─sda2 8:2 0 1G 0 part /boot
<br>└─sda3 8:3 0 930G 0 part <br> └─luks-aee439f3-528c-4481-ab09-622304e727bc 253:0 0 930G 0 crypt <br> ├─vgfedora-pool00_tmeta 253:1 0 424M 0 lvm <br> │ └─vgfedora-pool00-tpool 253:3 0 829.2G 0 lvm <br> │ ├─vgfedora-fedora 253:4 0 829.2G 0 lvm /
<br> │ └─vgfedora-pool00 253:5 0 829.2G 1 lvm <br> └─vgfedora-pool00_tdata 253:2 0 829.2G 0 lvm <br> └─vgfedora-pool00-tpool 253:3 0 829.2G 0 lvm <br> ├─vgfedora-fedora 253:4 0 829.2G 0 lvm /
<br> └─vgfedora-pool00 253:5 0 829.2G 1 lvm <br>
<br>The same thing as above in pastebin: </span><a href="https://pastebin.com/raw/xwXngMRh" target="_blank">https://pastebin.com/raw/xwXngMRh</a><span style="font-family:monospace"><br><br></span><div>If you notice that /dev/sda3 is of size 930G, but the volume group is only 829.2 G.</div><div><br></div><div>Why is that ? I have selected the size of the volume group as "Large as possible", but still 100G is left out.</div><div><br></div><div>Is this some kind of recommended setting for thin-LVMs ?</div><div><br></div><div>I am selecting Thin-LVM with LUKS2 during the install.</div><div><br></div><div>Can someone help me understand why this is happening and how I can fix it ? </div></div></div></blockquote><div><br></div><div>There are some circumstances under which LVM may need additional space for thin pool metadata. When we added support for thin provisioning they strongly recommended that we reserve a portion of the volume group space for this purpose.Initially it was 20% of the pool size, but the calculation may be more nuanced now. I wouldn't consider removing this bit of free space "fixing" anything unless you plan to actively monitor your system to ensure that your thin pool doesn't run out of space for metadata.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><br></div><div>Will making a custom kickstart help here ?</div></div></div></blockquote><div><br></div><div>Maybe... It has been a while since I worked on this code, but you _might_ be able to override this in kickstart using `--reserved-space` or `--reserved-percent` options to the `volgroup` command.</div><div><br></div><div>HTH,</div><div>David</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><br></div>-- <br><div dir="ltr"><div dir="ltr">Regards,<div>Sreyan Chakravarty</div></div></div></div></div>
_______________________________________________<br>
Kickstart-list mailing list<br>
<a href="mailto:Kickstart-list@redhat.com" target="_blank">Kickstart-list@redhat.com</a><br>
<a href="https://listman.redhat.com/mailman/listinfo/kickstart-list" rel="noreferrer" target="_blank">https://listman.redhat.com/mailman/listinfo/kickstart-list</a></blockquote></div></div></div>