On 2021-01-02 at 03:36, Andrei POPESCU wrote:

> On Vi, 01 ian 21, 23:09:01, deloptes wrote:
>> 
>> Each LSI card has a 6 bay cage attached and I have raided 6x2TB WD
>> RED spinning discs (for data) and 2x1TB WD RED spinning discs (for
>> OS)
> 
> 1TB for OS (assuming RAID1) seems... excessive to me. All my current
> installations are in 10 GiB partitions with only a separate /home.
> 
> Even if I'd go "wild" with several desktops installed (I'm only
> using LXDE), LibreOffice, etc. I'd probably get away with 50 GiB or
> so. Check the output of:
> 
> du -hx --max-depth=1 /

That would take a while to run, so I'm not going to do it just offhand,
but here's what I for my part get from a remotely analogous 'df' command
(piped through grep to include only actual on-disk partitions, since I
do everything through LVM whenever possible):

$ df -h | grep vg_
/dev/mapper/vg_system-lv_root 92G 23G 65G 26% /
/dev/mapper/vg_system-lv_usr 92G 19G 69G 22% /usr
/dev/mapper/vg_system-lv_boot 22G 137M 21G 1% /boot
/dev/mapper/vg_data-lv_home 9.9T 4.9T 4.5T 53% /home
/dev/mapper/vg_data-lv_opt 503G 33G 445G 7% /opt
/dev/mapper/vg_system-lv_tmp 7.3G 321M 6.6G 5% /tmp
/dev/mapper/vg_data-lv_var 503G 247G 231G 52% /var

vg_system totals something on the vague order of 750GB to 800GB.

/ itself (excluding child filesystems) contains 23GB of data. 22GB of
that is under /root. 17GB of *that* consists of backups of other
data that isn't read-time-accessible to any other user - both because it
isn't convenient to create the backup without that access, and because
some of that data may be read-restricted for good reason and I don't
want to put it somewhere more generally accessible in backed-up form any
more than in its production form. Another 2.4GB of the 22GB is in a
"packaging" subdirectory, and comes from an earlier point in my work
with Debian packages, when there was a reason for part of the process to
be done with root access.

/usr contains another 19GB.

/boot contains only 137MB, and could definitely stand to be way, way
less than 22GB in size.

/tmp is irrelevant here because it gets wiped on every reboot, but I
*have* actually managed to fill it up at least once; I'd probably make
it bigger on a full from-scratch system rebuild.

/var (which is part of my "data" LV, because of its tendency towards
large size, even though apparently the installed system won't operate
correctly without its exact contents and so it should properly go in the
"system" LV) contains 247GB - but that includes at least three
at-least-partial copies of the rest of the partition, from a recovery
operation from when the RAID array failed, as well as a mass redownload
of the damaged-at-array-failure-time contents of
/var/cache/apt/archives/. After I subtract off those, however, the
"real" size of that partition is still in the vicinity of 100GB (give or
take about 5GB) - of which 94GB is under /var/cache/apt/archives/.

Add those up and you get at least 120GB, even excluding the 22GB of data
under /root and the extra copies under /var.

Maybe 1TB of space for the installed OS is excessive, although I'm not
entirely convinced - but I don't see how you get away with 10GB, except
in the very short term after installation.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to