What takes up space on a fresh install.

11 posts / 0 new
Last post
#1 Mon, 08/04/2014 - 11:36
macneil

What takes up space on a fresh install.

Hi folks,

I recently put virtualmin on a 4tb server, no raid and I was a bit shocked to see 180GB or so taken up after the install.

I've never noticed it to reserve so much with other installs on 1TB and 100GB. So what is taking up all the space...chroot for dns? I'd like to reclaim it back ideally. It only seems applicable to my dedi boxes as opposed to my VPS... I don't think it's how I'm formatting?

DEDI: Operating system CentOS Linux 6.5 Webmin version 1.690 Virtualmin version 4.09.gpl GPL

Filesystem      Size  Used Avail Use% Mounted on
rootfs           20G  2.9G   16G  16% /
/dev/root        20G  2.9G   16G  16% /
devtmpfs        7.9G  260K  7.9G   1% /dev
/dev/md3        3.6T  2.1T  1.4T  61% /home
tmpfs           7.9G     0  7.9G   0% /dev/shm
/dev/root        20G  2.9G   16G  16% /var/named/chroot/etc/named
/dev/root        20G  2.9G   16G  16% /var/named/chroot/var/named
/dev/root        20G  2.9G   16G  16% /var/named/chroot/etc/named.conf
/dev/root        20G  2.9G   16G  16% /var/named/chroot/etc/named.rfc1912.zones
/dev/root        20G  2.9G   16G  16% /var/named/chroot/etc/rndc.key
/dev/root        20G  2.9G   16G  16% /var/named/chroot/usr/lib64/bind
/dev/root        20G  2.9G   16G  16% /var/named/chroot/etc/named.iscdlv.key
/dev/root        20G  2.9G   16G  16% /var/named/chroot/etc/named.root.key

VPS: Operating system CentOS Linux 6.3 Webmin version 1.675 Virtualmin version 4.04.gpl GPL

Filesystem            Size  Used Avail Use% Mounted on
/dev/simfs            100G   78G   23G  78% /
none                  1.0G  4.0K  1.0G   1% /dev
none                  1.0G     0  1.0G   0% /dev/shm

Thanks in advance

Mon, 08/04/2014 - 12:33
andreychek

Howdy,

Installing Virtualmin uses up very little space. I think with a typical distribution installation that you'd normally be looking at a total of 1GB or 2GB in all.

What you may want to do is use "du" to determine what is using up all the space.

To do that, you can go into the "/" directory (which you can do by running "cd /"), then run this command:

du -sh *

What does that command output?

-Eric

Mon, 08/04/2014 - 12:47
macneil

Hi Eric

Thanks for the quick reply :) - I tried a reboot to see if it was temp but only device names changed.

Running du -sh gave me errors also:

[root@host /]# du -sh
du: mount point `./var/named/chroot/var/named' already traversed
du: cannot access `./proc/6099/task/6099/fd/4': No such file or directory
du: cannot access `./proc/6099/task/6099/fdinfo/4': No such file or directory
du: cannot access `./proc/6099/fd/4': No such file or directory
du: cannot access `./proc/6099/fdinfo/4': No such file or directory
2.1T    .
[root@host /]# df -h
Filesystem      Size  Used Avail Use% Mounted on
rootfs           20G  2.9G   16G  16% /
devtmpfs        7.8G  216K  7.8G   1% /dev
tmpfs           7.8G     0  7.8G   0% /dev/shm
/dev/md2         20G  2.9G   16G  16% /
/dev/md3        3.6T  2.1T  1.4T  61% /home
/dev/md2         20G  2.9G   16G  16% /var/named/chroot/etc/named
/dev/md2         20G  2.9G   16G  16% /var/named/chroot/var/named
/dev/md2         20G  2.9G   16G  16% /var/named/chroot/etc/named.conf
/dev/md2         20G  2.9G   16G  16% /var/named/chroot/etc/named.rfc1912.zones
/dev/md2         20G  2.9G   16G  16% /var/named/chroot/etc/rndc.key
/dev/md2         20G  2.9G   16G  16% /var/named/chroot/usr/lib64/bind
/dev/md2         20G  2.9G   16G  16% /var/named/chroot/etc/named.iscdlv.key
/dev/md2         20G  2.9G   16G  16% /var/named/chroot/etc/named.root.key
Mon, 08/04/2014 - 13:31
andreychek

Hmm, did you add the "*" character to the end of that 'du -sh` command? The full command should look like this:

du -sh *

And that should be run from "/".

-Eric

Mon, 08/04/2014 - 13:39
andreychek

Hmm, I wonder if maybe I mis-understood the issue initially.

I think you're saying that you're expecting to see more space available on your dedicated server.

Now, the usage in the / partition isn't all that unusual.

I see that /dev/md3, mounted on /home, is 3.6TB, 2.1TB used, and has 1.4TB remaining.

Is that what you're asking about?

Are you surprised as to how much is being used?

Or are you thinking that it should be larger than 3.6TB?

-Eric

Mon, 08/04/2014 - 14:10 (Reply to #5)
macneil

Hi Eric

Im expecting to see more than 3.6TB

I'm pretty sure it was 3.8TB before i put virutalmin on.

Thanks again

Mon, 08/04/2014 - 14:05
macneil

Sorry Eric - I didn't see the *

Going further into those user11, user22, user33 - only leads to the data i moved and nothing that would suggest the missing 180G.

This is 2 x 2TB SATA

[root@host /]# du -sh *
7.5M    bin
32M boot
4.0K    cgroup
216K    dev
33M etc
2.1T    home
133M    lib
23M lib64
16K lost+found
68K Maildir
4.0K    media
4.0K    mnt
4.0K    opt
du: cannot access `proc/12214/task/12214/fd/4': No such file or directory
du: cannot access `proc/12214/task/12214/fdinfo/4': No such file or directory
du: cannot access `proc/12214/fd/4': No such file or directory
du: cannot access `proc/12214/fdinfo/4': No such file or directory
0   proc
38M root
26M sbin
4.0K    selinux
4.0K    srv
0   sys
92K tmp
2.0G    usr
du: mount point `var/named/chroot/var/named' already traversed
477M    var
[root@host /]# du -sh /home/*
8.0K    /home/aquota.group
8.0K    /home/aquota.user
552G    /home/user33
16K /home/lost+found
705G    /home/user22
48K /home/xr20bmx
846G    /home/user11

This is a 1TB box (1SATA) with the same provider - (708G /home/s10nix/files) is user data only created after virtualmin install:

[root@host /]# du -sh *
7.5M    bin
32M boot
4.0K    cgroup
212K    dev
46M etc
708G    home
133M    lib
23M lib64
16K lost+found
68K Maildir
4.0K    media
4.0K    mnt
4.0K    opt
du: cannot access `proc/23762/task/23762/fd/4': No such file or directory
du: cannot access `proc/23762/task/23762/fdinfo/4': No such file or directory
du: cannot access `proc/23762/fd/4': No such file or directory
du: cannot access `proc/23762/fdinfo/4': No such file or directory
0   proc
38M root
26M sbin
4.0K    selinux
4.0K    srv
du: cannot access `sys/kernel/slab/L2TP/IPv6': No such file or directory
du: cannot access `sys/kernel/slab/L2TP/IP': No such file or directory
0   sys
60K tmp
2.0G    usr
du: mount point `var/named/chroot/var/named' already traversed
466M    var
[root@host /]# du -sh /home/*
8.0K    /home/aquota.group
8.0K    /home/aquota.user
16K /home/lost+found
708G    /home/s10nix
[root@host /]# du -sh /home/s10nix/*
4.0K    /home/s10nix/cgi-bin
708G    /home/s10nix/files
4.0K    /home/s10nix/homes
4.0K    /home/s10nix/logs
4.0K    /home/s10nix/public_html
[root@host /]# 
Mon, 08/04/2014 - 14:13
macneil

The local disk space indicator on Virtualmin home page, showed 180GB used after a fresh install of both OS and Vrtualmin.

I'm willing to reformat a smaller 1TB box to test?

Cheers

Mon, 08/04/2014 - 14:24
macneil

Is it really TB vs TiB?

:(

[root@host /]# df -H
Filesystem      Size  Used Avail Use% Mounted on
rootfs           21G  3.1G   17G  16% /
devtmpfs        8.4G  222k  8.4G   1% /dev
tmpfs           8.4G     0  8.4G   0% /dev/shm
/dev/md2         21G  3.1G   17G  16% /
/dev/md3        4.0T  2.3T  1.5T  61% /home
/dev/md2         21G  3.1G   17G  16% /var/named/chroot/etc/named
/dev/md2         21G  3.1G   17G  16% /var/named/chroot/var/named
/dev/md2         21G  3.1G   17G  16% /var/named/chroot/etc/named.conf
/dev/md2         21G  3.1G   17G  16% /var/named/chroot/etc/named.rfc1912.zones
/dev/md2         21G  3.1G   17G  16% /var/named/chroot/etc/rndc.key
/dev/md2         21G  3.1G   17G  16% /var/named/chroot/usr/lib64/bind
/dev/md2         21G  3.1G   17G  16% /var/named/chroot/etc/named.iscdlv.key
/dev/md2         21G  3.1G   17G  16% /var/named/chroot/etc/named.root.key
Mon, 08/04/2014 - 14:50
andreychek

Howdy,

Well, I think we're talking about a couple of different things here, and I'm struggling with where to start :-)

I assure you that installing Virtualmin doesn't take up 180GB of space.

A good many installs don't have anything near that much space to work with, as a lot of folks use VPS's these days.

So if you're seeing 180GB used, something else is going on.

Now, with the total disk size -- 3.6TB vs 3.8TB -- that's just the disk size as reported by the Linux kernel. It's showing the partition, as it was formatted before Linux was even installed. So the Virtualmin installation wouldn't be affecting that either.

-Eric

Mon, 08/04/2014 - 15:14
macneil

Hi Eric

I think I've confused myself somewhere along the way with the /named/chroot difference between my installs. I have virtualmin running on 100GB servers also, so I understand it works well :).

I'll reformat a 1TB later in the month before it expires. I'll recheck then and come back.

Thanks again for your help.

Topic locked