[SOLVED] /home folder is taking space on two partitions after install

Question

Hi everyone,
At first I thought that I would just read these forums, however even after a few days of using Arch Linux I found one issue that was never been asked before (or asked in different way that I couldn't find).
So the problem that I cannot find solution for is that the files in /home folder are taking space on two partitions - on /dev/sda2 and /dev/sda4 and therefore making root partition run out of space.
Some information from commands to get more clear view:
[root@localhost ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 20511356 18790980 655416 97% /
dev 5109884 0 5109884 0% /dev
run 5112632 592 5112040 1% /run
tmpfs 5112632 2696 5109936 1% /dev/shm
tmpfs 5112632 0 5112632 0% /sys/fs/cgroup
tmpfs 5112632 34612 5078020 1% /tmp
/dev/sda4 215038368 15923256 188168744 8% /home
tmpfs 1022528 12 1022516 1% /run/user/1000
[root@localhost ~]# cat /etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=a2160300-9ce0-4a88-8e29-ee87d1ee0d96 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda4
UUID=7e762343-1762-481e-b433-be9edaca18bb /home ext4 rw,relatime,data=ordered 0 2
# /dev/sda3
UUID=096fb727-255c-4aac-b200-0baa929dd9b7 none swap defaults 0 0
[root@localhost ~]# cat /etc/mtab
rootfs / rootfs rw 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
sys /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
dev /dev devtmpfs rw,nosuid,relatime,size=5109884k,nr_inodes=1277471,mode=755 0 0
run /run tmpfs rw,nosuid,nodev,relatime,mode=755 0 0
/dev/sda2 / ext4 rw,relatime,data=ordered 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/net_cls cgroup rw,nosuid,nodev,noexec,relatime,net_cls 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=21,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
configfs /sys/kernel/config configfs rw,relatime 0 0
tmpfs /tmp tmpfs rw 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0
/dev/sda4 /home ext4 rw,relatime,data=ordered 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=1022528k,mode=700,uid=1000,gid=100 0 0
gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=100 0 0
[root@localhost ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 238.5G 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 20G 0 part /
├─sda3 8:3 0 10G 0 part [SWAP]
└─sda4 8:4 0 208.5G 0 part /home
sr0 11:0 1 1024M 0 rom
I have checked three times the commands that I ran when installing Arch Linux with a few tutorials including beginner's guide but don't see where could be the issue. Maybe any of you know what could be the problem here?
Last edited by juraskaz (2014-10-29 18:13:02)

Answer 1

drcouzelis wrote:
juraskaz wrote:Some information from commands to get more clear view:
I'm so confused. O_O What is the problem? The output of those commands are all consistent: "/dev/sda2" is mounted as "/" and "/dev/sda4" is mounted as "/home".
Are you saying that when you create a 1GB file in "/home" that 1GB of space becomes used in BOTH "/home" and "/"?
One thing that MIGHT be suspicious is your use of "/dev/sda4". In a traditional BIOS setup, partitions 1 - 3 are primary partitions and partition 4 is an extended partition. How is your drive partitioned? Could that be related to whatever problem you're seeing?
Thank you drcouzelis for pointing me in the right direction! I thought that creating 1 GB in /home would be used in both /home and /, however when I did that only /home have changed. So I started checking what is causing / to fill out and found that it was the backup of home to the root!
Thank you for your time