On 2022-03-18 7:42 a.m., Angelo Moreschini wrote:
I would like to ask for help about to choose the pertizioni to leave and those to format .. starting from the current situation that I transcribe below:
As outlined a new install will re-format *everything* as a Fedora install over an existing setup will re-format the '/' and everything contained in it. You have only the '/' partition as /dev/sdb3.
Fedora on needs to re-format the '/' and '/var' folders if you have partitioned any other folders onto their own partitions. The other partitions can be preserved across the install.
So, provided you have created a separate *partition* for /home or (for example) /usr/local/sbin, you can do a 'bare-metal' type install of the OS *without* disturbing those partitions. All of your data can carry over to the new install without problem. Note that those partitions do not need to be btrfs OR lvm. I am not sure why you are using lvm in this case, as there is only one drive being used for Fedora.
I am not sure if the live-install version of Fedora includes gparted. If not you can use sfdisk which I am sure is available on the live-install. But since your objective is to re-format things, the easiest route would just be to do an install which re-formats /dev/sdb3, then using that install with gparted, create partitions for the new separate folders you want, and re-install with that in place.
I would suggest that after /dev/sdb1 and /dev/sdb2, which are efi-required that you set up partitions for '/', '/home', '/usr/local', and 'var', plus any other separate partitions which you might want to segregate (or back up separately, such as any business related data/code/documents etc.) (Anything after '/' will be in an extended partition)
Along with /home I use a separate /misc partition, which has all the business-related stuff, the mysql databases, and web-site backup/local runtime, so none of this needs to be re-installed or even touched on a re-install. But it is easier to back up.
I also have a 5G '/usr/local' which has my 'personal' executables, such as games (FlightGear), and the mythtv setup. This partition also gets the java /ice-tea libraries, and calibre.
/var is given its own partition as it gets over-written on a re-install (even then, with mysql/mariadb on a different partition (misc) you need only create a link for '/var/lib/mysql pointing to /misc/mysql to be up and running.
So basically it is a matter of planning for what you know must happen, and protecting what you what to be untouched in a separate partition. HTH
Geoff
On Fri, 18 Mar 2022 at 13:43, R. G. Newbury newbury@mandamus.org wrote:
On 2022-03-18 7:42 a.m., Angelo Moreschini wrote:
I would like to ask for help about to choose the pertizioni to leave and those to format .. starting from the current situation that I transcribe below:
As outlined a new install will re-format *everything* as a Fedora install over an existing setup will re-format the '/' and everything contained in it. You have only the '/' partition as /dev/sdb3.
Fedora on needs to re-format the '/' and '/var' folders if you have partitioned any other folders onto their own partitions. The other partitions can be preserved across the install.
So, provided you have created a separate *partition* for /home or (for example) /usr/local/sbin, you can do a 'bare-metal' type install of the OS *without* disturbing those partitions. All of your data can carry over to the new install without problem. Note that those partitions do not need to be btrfs OR lvm. I am not sure why you are using lvm in this case, as there is only one drive being used for Fedora.
I am not sure if the live-install version of Fedora includes gparted. If not you can use sfdisk which I am sure is available on the live-install. But since your objective is to re-format things, the easiest route would just be to do an install which re-formats /dev/sdb3, then using that install with gparted, create partitions for the new separate folders you want, and re-install with that in place.
I would suggest that after /dev/sdb1 and /dev/sdb2, which are efi-required that you set up partitions for '/', '/home', '/usr/local', and 'var', plus any other separate partitions which you might want to segregate (or back up separately, such as any business related data/code/documents etc.) (Anything after '/' will be in an extended partition)
Along with /home I use a separate /misc partition, which has all the business-related stuff, the mysql databases, and web-site backup/local runtime, so none of this needs to be re-installed or even touched on a re-install. But it is easier to back up.
I managed *NIX systems for 35 years in a group working with data sets much larger than filesystems until recently, which meant that filesystems were repeatedly filled and emptied. Legacy *NIX filesystems degraded when nearly full due to excessive fragmentation. Not only was that slow, it was very hard on spinning disks, so many systems had measures to prevent users from adding data past 85 to 90% of the capacity..
SSD's are a different story. Fragmentation has little impact on performance. The memory used in SSD's does however, have a limited number of write cycles before failing. Wear-leveling algorithms move blocks that show high numbers of write cycles to prolong the period for which the full capacity is available. I assume wear leveling is done at the lowest level and ignores partitions and filesystems, but choices of filesystem and partitions can have an impact on wear patterns and potential conflicts with wear-leveling.
Fixed partitions invariably end up with different fractions of free space. With llvm you could reserve some space and use it to top up a partition that was running out of space, but once the extra space has been used you can be left with one full partition while another partition has ample free space.
Fedora 35 default filesystem is btrfs. Btrfs makes a pool of the space not needed for other filesystems, and then creates virtual partitions each the size of the entire pool. The virtual partitions can grow as needed until the pool is exhausted. This should simplify the wear-leveling workload, so may prolong the useful life of SSD's,
I also have a 5G '/usr/local' which has my 'personal' executables, such as games (FlightGear), and the mythtv setup. This partition also gets the java /ice-tea libraries, and calibre.
/var is given its own partition as it gets over-written on a re-install (even then, with mysql/mariadb on a different partition (misc) you need only create a link for '/var/lib/mysql pointing to /misc/mysql to be up and running.
So basically it is a matter of planning for what you know must happen, and protecting what you what to be untouched in a separate partition.
Or just letting btrfs create over-sized "virtual partitions" and then allocating physical space as needed.
With either strategy you still need backups of critical data.
On Sat, 19 Mar 2022 at 16:14, Samuel Sieb samuel@sieb.net wrote:
On 3/19/22 05:18, George N. White III wrote:
Or just letting btrfs create over-sized "virtual partitions" and then allocating physical space as needed.
btrfs doesn't do that. That's LVM thin-provisioning.
Fresh install of Fedora 35 using default installation in the free space (after shrinking the OEM Windows partition, leaving a little over 400 GB):
% df -lhT | grep btrfs /dev/nvme0n1p6 btrfs 405G 89G 316G 22% / /dev/nvme0n1p6 btrfs 405G 89G 316G 22% /home % sudo pvs -a PV VG Fmt Attr PSize PFree /dev/nvme0n1p1 --- 0 0 /dev/nvme0n1p2 --- 0 0 /dev/nvme0n1p3 --- 0 0 /dev/nvme0n1p4 --- 0 0 /dev/nvme0n1p5 --- 0 0 /dev/nvme0n1p6 --- 0 0 /dev/sda1 --- 0 0 /dev/sda2 --- 0 0 /dev/sdb1 --- 0 0 /dev/sdb2 --- 0 0
So the 405G btrfs shows / and /home sharing the 405G, and no PV's for lvm to use.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 3/19/22 14:48, George N. White III wrote:
On Sat, 19 Mar 2022 at 16:14, Samuel Sieb <samuel@sieb.net mailto:samuel@sieb.net> wrote:
On 3/19/22 05:18, George N. White III wrote: > Or just letting btrfs create over-sized "virtual partitions" and then > allocating > physical space as needed. btrfs doesn't do that. That's LVM thin-provisioning.Fresh install of Fedora 35 using default installation in the free space (after shrinking the OEM Windows partition, leaving a little over 400 GB):
% df -lhT | grep btrfs /dev/nvme0n1p6 btrfs 405G 89G 316G 22% / /dev/nvme0n1p6 btrfs 405G 89G 316G 22% /home % sudo pvs -a PV VG Fmt Attr PSize PFree /dev/nvme0n1p1 --- 0 0 /dev/nvme0n1p2 --- 0 0 /dev/nvme0n1p3 --- 0 0 /dev/nvme0n1p4 --- 0 0 /dev/nvme0n1p5 --- 0 0 /dev/nvme0n1p6 --- 0 0 /dev/sda1 --- 0 0 /dev/sda2 --- 0 0 /dev/sdb1 --- 0 0 /dev/sdb2 --- 0 0
So the 405G btrfs shows / and /home sharing the 405G, and no PV's for lvm to use.
I don't know what you're trying to show there. "over-size virtual partitions" is LVM thin-provisioning. btrfs in your case has used the 405G partition and that's all the space that's available. It can be used by any of the btrfs volumes, but any space that's used by one volume is no longer available for the other ones. Every btrfs volume shows the same size.
If you meant something else by your initial comment, you'll need to explain it.
On Sat, 19 Mar 2022 at 19:01, Samuel Sieb samuel@sieb.net wrote:
On 3/19/22 14:48, George N. White III wrote:
On Sat, 19 Mar 2022 at 16:14, Samuel Sieb <samuel@sieb.net mailto:samuel@sieb.net> wrote:
On 3/19/22 05:18, George N. White III wrote: > Or just letting btrfs create over-sized "virtual partitions" and then > allocating > physical space as needed. btrfs doesn't do that. That's LVM thin-provisioning.Fresh install of Fedora 35 using default installation in the free space (after shrinking the OEM Windows partition, leaving a little over 400
GB):
% df -lhT | grep btrfs /dev/nvme0n1p6 btrfs 405G 89G 316G 22% / /dev/nvme0n1p6 btrfs 405G 89G 316G 22% /home % sudo pvs -a PV VG Fmt Attr PSize PFree /dev/nvme0n1p1 --- 0 0 /dev/nvme0n1p2 --- 0 0 /dev/nvme0n1p3 --- 0 0 /dev/nvme0n1p4 --- 0 0 /dev/nvme0n1p5 --- 0 0 /dev/nvme0n1p6 --- 0 0 /dev/sda1 --- 0 0 /dev/sda2 --- 0 0 /dev/sdb1 --- 0 0 /dev/sdb2 --- 0 0
So the 405G btrfs shows / and /home sharing the 405G, and no PV's for lvm to use.
I don't know what you're trying to show there. "over-size virtual partitions" is LVM thin-provisioning. btrfs in your case has used the 405G partition and that's all the space that's available. It can be used by any of the btrfs volumes, but any space that's used by one volume is no longer available for the other ones. Every btrfs volume shows the same size.
If you meant something else by your initial comment, you'll need to explain it.
We are comparing the Fedora 35 default to manual partitioning. In btrfs terminology, /root is a top-level subvolume https://btrfs.readthedocs.io/en/latest/Subvolumes.html and /home is a . subvolume sharing storage with the top-level / filesystem. I just wanted point out that a default install doesn't need predetermined space requirements. Having said that, LVM helps adjust sizes based on in-use demands (but needs more steps to set up)..
-
George N. White III -
R. G. Newbury -
Samuel Sieb