On 20/04/2022 17:38, Mark Rogers wrote:
Can anyone explain this?
$ sudo fdisk -l /dev/sda Disk /dev/sda: 50 GiB, 53687091200 bytes, 104857600 sectors Disk model: VBOX HARDDISK Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E225721B-FB64-4D48-B133-6758468EF9F6
Device Start End Sectors Size Type /dev/sda1 2048 4095 2048 1M BIOS boot /dev/sda2 4096 3149823 3145728 1.5G Linux filesystem /dev/sda3 3149824 104855551 101705728 48.5G Linux filesystem
$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/mapper/ubuntu--vg-ubuntu--lv 24G 23G 13M 100% /
The scenario is that this is a new VirtualBox VM with Ubuntu 20.04.4 installed. It has a single 50GB disk as shown in VirtualBox and fdisk, but having copied 23GB to it from elsewhere (using rsync) the disk is now full. What am I missing and how do I get my disk space back?hard caps for work
To me,
/dev/mapper/ubuntu--vg-ubuntu--lv
tells me that there is a Logical Volume (LV) Mapped onto the actual physical disk. I think by default a new install will use Logical Volumes for flexibilty and resiableness, but I've never used one. Why it wouldn't use the full disk I don't know. I've used disk encryption and that shows up as a drive mounted on dev/mapper, so that makes confirms to me that you're not using a file system directly onto the physical disk, but with an intermediary.
Hope that helps.
Steve