How to find the system calamares installed partition details?

[fhins]

I recently installed the latest Manjaro Plasma KDE through calamares system installation with no issues at all. However, I’m trying to find out the partition detail break down for the installation for the boot size, root and etc out of curiosity? I tried “KDE partition manager”, but it only shows this:
KDE Partition Manager:

inxi -Fxz:

Partition:
  ID-1: / size: 978.09 GiB used: 119.27 GiB (12.2%) fs: btrfs dev: /dev/sda1
  ID-2: /home size: 978.09 GiB used: 119.27 GiB (12.2%) fs: btrfs
    dev: /dev/sda1
  ID-3: /var/log size: 978.09 GiB used: 119.27 GiB (12.2%) fs: btrfs
    dev: /dev/sda1

lsblk -f:

NAME   FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                           
└─sda1 btrfs              cec7ad8a-4582-4889-8304-16e85a337af3  856.9G    12% /home
                                                                              /var/log
                                                                             /var/cache

df -h /boot:

Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1       979G  120G  857G  13% /

^{Mod edit: added 3 backticks ``` before and after each command output to format it as code}
Where is the boot partition installed and what is boot size?

[Teo]

Try sudo parted -l

[soundofthunder]

@fhins

I’m trying to find out the partition detail break down for the installation for the boot size, root and etc out of curiosity

inxi has already given an adequate overview of partition sizes and used space, though, unless /etc is on a partition of it’s own, that won’t reveal anything useful.

For that, you could try the tree command; specifically:

tree -s /etc

Too much detail? See man tree to learn how to tailor it a little.

---

Edit:- As btrfs has been mentioned (see below).

Btrfs - ArchWiki

[scotty65]

btrfs uses subvolumes rather than partitions, so getting the size of individual directories such as /home/ or /etc/ is a different process to that used with ext4, which was manjaro’s previous default file system.

These topics may help:

How can I see the disk usage with btrfs?

Thanks Linux-aarhus. I read you’re remark about btrfs. Is there a proper way to determine the real size on disk for a btrfs subvol ? They all have the same size on my system. /dev/sda2 50G 14G 36G 28% /.snapshots /dev/sda2 50G 14G 36G 28% /home /dev/sda2 50G 14G 36G 28% /var/cache /dev/sda2 50G 14G 36G 28% /var/log /dev/sda3 49G 2G 47G 4% /storage /dev/sda2 50G 14G 36G 28%…

[HowTo] get Space on BTRFS

If you encounter a situation where a Btrfs volume is out of space, There is a way out However, you have to accept that Btrfs is a “strange” filesystem. So if you’re doing things that would help with other filesystems, it might NOT help with btrfs. If you want to know why, check out the wiki Here are a few simple tips: 1. Only use btrfs to meassure the unallocated space on your filesystem: sudo btrfs filesystem usage / 2. Look at “Device unallocated:” If the Unallocated size is less than 10GB…

Btrfs Best Practice

calamares already does that automatically, or at least, if you go with automatic partitioning. It will create four subvolumes in addition to the top-level subvolume (which cannot be deleted)… @, which will be mounted as / @home, which will be mounted as /home @cache, which will be mounted as /var/cache @log, which will be mounted as /var/log calamares will however not create any additional subvolumes, nor will it set the default subvolume when the partition is mounted without e…

Required Disclaimer: I’ve never used btrfs, so my knowledge of its workings is very limited.

Also, as you are a Plasma user, the filelight application (may require installation) is a good way of seeing your file system usage in a GUI:

Filelight

pamac info filelight

❯ pamac info filelight
Name                  : filelight
Version               : 26.04.3-1
Description           : View disk usage information
URL                   : https://apps.kde.org/filelight/
Licenses              : GPL-2.0-or-later LGPL-2.0-or-later
Repository            : extra
Installed Size        : 1.6 MB
Groups                : kde-applications kde-utilities
Depends On            : glibc kconfig kcoreaddons kcrash ki18n kio kirigami
                        kirigami-addons kwidgetsaddons libstdc++
                        qqc2-desktop-style qt6-base qt6-declarative
Optional Dependencies : --
Required By           : --
Optional For          : dolphin
Provides              : --
Replaces              : --
Conflicts With        : --
Packager              : Antonio Rojas <arojas@archlinux.org>
Build Date            : Wed 01 Jul 2026 02:00:04
Install Date          : Sat 04 Jul 2026 12:00:38
Install Reason        : Explicitly installed
Validated By          : Signature
Backup files          : --

[linux-aarhus]

btrfs is not like other file systems when it comes to disk space, it does not make use of partitions but sub-volumes.

You should use btrfs to get an idea of space used or free space.

Use the subvolume mount point e.g. / for root and /home for home

btrfs filesystem du /

[pwx]

df -ah | grep nvme                                                                                                                                            
/dev/nvme0n1p3                               952G     76G  874G    8% /
/dev/nvme0n1p3                               952G     76G  874G    8% /home
/dev/nvme0n1p2                               2,0G    239M  1,7G   13% /boot
/dev/nvme0n1p3                               952G     76G  874G    8% /var/cache
/dev/nvme0n1p3                               952G     76G  874G    8% /var/log
/dev/nvme0n1p1                                50M     35M   16M   70% /boot/efi

In your case df -ah | grep sda

[Molski]

@fhins

However, I’m trying to find out the partition detail break down for the installation for the boot size, root and etc out of curiosity?

The kernel generally doesn’t need a separate /boot partition. You can see that the kernel and initramfs images still live in there.

Most systems today use UEFI boot, which requires a small FAT32 EFI System Partition (ESP). This is commonly mounted at /boot/efi.

So I assume you are legacy BIOS (or CSM) booting?

This is a very small partition with no filesystem that may not come up in lsblk -f.

Others have mentioned other tools.. (Even sudo fdisk -l works.)

[nikgnomic]

@fhins

I’m trying to find out the partition detail break down for the installation

grep '/dev/sd*' /var/log/Calamares.log

[Teo]

I hope we do not have an XY problem here (and that the OP boots in efi mode, since it doesn’t look so). For educational purposes this seems more than enough.

Home - The XY Problem

[fhins]

Thank you all! A lot to study and learn.

[Aragorn]

Just a friendly Moderator note… You are not supposed to mark your own post as the solution unless you yourself found a solution that was not presented by any other interlocutor on the thread first, nor if your self-decided solution involves reinstalling the system.

I’ve moved the solution mark to @scotty65’s post, given that he posted the most elaborate btrfs-related information.

[fhins]

Sorry, I wasn’t aware of that!