[SOLVED] df -h does not reflect true root filesystem size

domentoi · 2014-12-22 11:17:01

Why does df -h show root filesystem as being only 20G?

df -h
Filesystem              Size  Used Avail Use% Mounted on
/dev/mapper/cryptroot    20G   15G  4.6G  76% /
dev                     7.7G     0  7.7G   0% /dev
run                     7.7G  668K  7.7G   1% /run
tmpfs                   7.7G   70M  7.7G   1% /dev/shm
tmpfs                   7.7G     0  7.7G   0% /sys/fs/cgroup
tmpfs                   7.7G  224K  7.7G   1% /tmp
/dev/sda1               239M   40M  183M  18% /boot
tmpfs                   1.6G  8.0K  1.6G   1% /run/user/1000

That is what my df -h output looks like. My setup is full disk encryption using dm-crypt with LUKS, per the guide on arch wiki. I basically created one /boot partition and left the rest of the disk to be an encrypted partition for the root filesystem. So why is my system complaining about (and acting as if it's running out of space)? Have I forgotten something?

Thank you for reading this. Let me know if you need any more logs or info on my setup - I realise I haven't provided very much info here, but I can't think of what to provide.

Last edited by domentoi (2014-12-24 19:02:32)

qinohe · 2014-12-22 11:44:37

Hi, a little more info would be okay, check 'lsblk', and share.

Lone_Wolf · 2014-12-22 11:59:28

the output of lsblk & fdisk -l should help to clarify what partitions your system sees.

Your /etc/fstab contents might als be useful.

Last edited by Lone_Wolf (2014-12-22 11:59:41)

graysky · 2014-12-22 11:59:40

How big is the partition you created?

domentoi · 2014-12-22 12:20:14

This is lsblk:

NAME          MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda             8:0    0 465.8G  0 disk  
├─sda1          8:1    0   250M  0 part  /boot
└─sda2          8:2    0 465.5G  0 part  
  └─cryptroot 254:0    0 465.5G  0 crypt /
sdb             8:16   0  14.9G  0 disk  
└─sdb1          8:17   0  14.9G  0 part

and fdisk -l

Disk /dev/sdb: 14.9 GiB, 16013942784 bytes, 31277232 sectors
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: dos
Disk identifier: 0x5da5572f

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdb1        2048 31275007 31272960 14.9G 73 unknown

Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xa5018820

Device     Boot  Start       End   Sectors   Size Id Type
/dev/sda1  *      2048    514047    512000   250M 83 Linux
/dev/sda2       514048 976773167 976259120 465.5G 83 Linux

Disk /dev/mapper/cryptroot: 465.5 GiB, 499842572288 bytes, 976255024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdc: 1.4 TiB, 1500301908480 bytes, 2930277165 sectors
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: dos
Disk identifier: 0x445e51a8

And graysky: I thought I made the partition for /boot 250 MB and the encrypted partition 465.5 GB but I'm now quite sure I did something wrong...

Thank you all

jasonwryan · 2014-12-22 16:08:13

Not a Sysadmin issue, moving to NC...

domentoi · 2014-12-23 03:55:17

Anyone?

MSC · 2014-12-23 07:24:34

Your partition layout looks fine. Most likely the filesystem is not the correct size.

If it's an ext4 partition, you should be able to fix it by running "sudo resize2fs /dev/mapper/cryptroot". Since resize2fs defaults to the full size of the partition, that will grow it appropriately. If you're using a different FS you may need a different command.

Mr.Elendig · 2014-12-23 16:31:03

What filesystem?

domentoi · 2014-12-24 07:53:59

Wow! Thank you so much MSC! I didn't know that the filesystem could be a different size from the partition it was located in...Your command worked for me. Thanks so much - I've learned something new today...huh...

jasonwryan · 2014-12-24 08:16:11

Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.

Arch Linux

#1 2014-12-22 11:17:01

[SOLVED] df -h does not reflect true root filesystem size

#2 2014-12-22 11:44:37

Re: [SOLVED] df -h does not reflect true root filesystem size

#3 2014-12-22 11:59:28

Re: [SOLVED] df -h does not reflect true root filesystem size

#4 2014-12-22 11:59:40

Re: [SOLVED] df -h does not reflect true root filesystem size

#5 2014-12-22 12:20:14

Re: [SOLVED] df -h does not reflect true root filesystem size

#6 2014-12-22 16:08:13

Re: [SOLVED] df -h does not reflect true root filesystem size

#7 2014-12-23 03:55:17

Re: [SOLVED] df -h does not reflect true root filesystem size

#8 2014-12-23 07:24:34

Re: [SOLVED] df -h does not reflect true root filesystem size

#9 2014-12-23 16:31:03

Re: [SOLVED] df -h does not reflect true root filesystem size

#10 2014-12-24 07:53:59

Re: [SOLVED] df -h does not reflect true root filesystem size

#11 2014-12-24 08:16:11

Re: [SOLVED] df -h does not reflect true root filesystem size

Board footer