You are not logged in.
Pages: 1
I installed Arch on a 150Gb HD lately and I'm experiencing a pretty annoying thing regarding available space on the drive.
Here is some info:
fdisk
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104422 83 Linux
/dev/sda2 14 79 530145 82 Linux swap / Solaris
/dev/sda3 80 19457 155653785 83 Linux
ncdu
5.2GiB /home
1.3GiB /usr
. 250.6MiB /var
82.0MiB /lib
. 11.2MiB /boot
10.5MiB /sbin
. 6.0MiB /etc
3.9MiB /bin
164.0kiB /dev
20.0kiB /tmp
4.0kiB /media
! 4.0kiB /root
. 0.0 B /proc
0.0 B /sys
0.0 B /srv
e 0.0 B /mnt
e 0.0 B /opt
Everything looks good so far and I should have plenty of space left on the device to play with. But using Thunar in xfce I am told that I have only 350Mb free. This is confirmed by the df command and I can see that I have a huge kcore in /proc.
df
/dev/sda3 7655940 7267696 388244 95% /
udev 10240 164 10076 2% /dev
none 1033064 140 1032924 1% /dev/shm
/dev/sda1 101105 13014 82870 14% /boot
ll /proc
-r-------- 1 root root 1065349120 Mar 6 13:08 kcore
Now, I understand that the kcore file is a virtual file that really doesn't affect my available space. But yet, it does affect how eg Thunar operates as it doesn't let me use the gigabytes of free space that I should have available.
I like the simple partition layout that I'm using, but is there some way to let the system ignore kcore and show the correct available space? Or am I forced to reinstall and use another partition scheme and work around the kcore size?
Usually I use ext2/3 but this time I thought I'd try jfs. Can that have something to do with this fenomenon? I have never seen this before...
Offline
Pages: 1