Bug 2055829 - [RFE] /var/tmp should be on its own partition
Summary: [RFE] /var/tmp should be on its own partition
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: imgbased
Classification: oVirt
Component: General
Version: 1.2.23
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.5.0
: 1.2.24
Assignee: Yedidyah Bar David
QA Contact: cshao
URL:
Whiteboard:
Depends On: 2057475 2058538
Blocks: 2015802 2057338
TreeView+ depends on / blocked
 
Reported: 2022-02-17 18:07 UTC by Yedidyah Bar David
Modified: 2022-04-20 06:33 UTC (History)
12 users (show)

Fixed In Version: imgbased-1.2.24
Doc Type: Enhancement
Doc Text:
`/var/tmp` is now on a separate lvm partition for DISA-STIG support.
Clone Of:
: 2104408 (view as bug list)
Environment:
Last Closed: 2022-04-20 06:33:59 UTC
oVirt Team: Node
Embargoed:
sbonazzo: ovirt-4.5+
pm-rhel: planning_ack?
sbonazzo: devel_ack+
pm-rhel: testing_ack?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt imgbased pull 3 0 None Merged Split /var/tmp to its own partition 2022-02-23 07:30:35 UTC
Red Hat Issue Tracker RHV-44717 0 None None None 2022-02-17 18:15:15 UTC

Internal Links: 2066055 2104408

Description Yedidyah Bar David 2022-02-17 18:07:03 UTC
Description of problem:

DISA STIG requires /var/tmp to be on a separate partition.

A summary of an internal discussion about sizes:

Right now /var is 15GB (not including some subdirs that already have their own partition).

/var/tmp normally does not need to be that large, except for one known case - hosted-engine deployment, which creates a local VM with its disk image on /var/tmp. The ost-images project (used for ovirt-system-tests) already has /var/tmp on a separate partition, and it's set to 9220 MB. I suppose it was done as close-to-minimum, as we try to save space on CI there. So probably something slightly larger than that should be enough for all normal cases. We decided to have /var/tmp of 10GB, and make /var 5GB (instead of current 15) - this will keep the entire minimal storage needs unchanged, and should be enough for most cases.

Comment 1 cshao 2022-03-18 04:52:03 UTC
Test version:
RHVH-4.5-20220315.0-RHVH-x86_64-dvd1.iso

imgbase w 
You are on rhvh-4.5.0.2-0.20220315.0+1
# df -h
Filesystem                                      Size  Used Avail Use% Mounted on
devtmpfs                                        1.8G     0  1.8G   0% /dev
tmpfs                                           1.8G   12K  1.8G   1% /dev/shm
tmpfs                                           1.8G  8.8M  1.8G   1% /run
tmpfs                                           1.8G     0  1.8G   0% /sys/fs/cgroup
/dev/mapper/rhvh-rhvh--4.5.0.2--0.20220315.0+1   23G  3.5G   19G  16% /
/dev/sda1                                      1014M  504M  511M  50% /boot
/dev/mapper/rhvh-home                          1014M   40M  975M   4% /home
/dev/mapper/rhvh-var                             15G  227M   15G   2% /var
/dev/mapper/rhvh-tmp                           1014M   40M  975M   4% /tmp
/dev/mapper/rhvh-var_log                        8.0G  105M  7.9G   2% /var/log
/dev/mapper/rhvh-var_crash                       10G  105M  9.9G   2% /var/crash
/dev/mapper/rhvh-var_tmp                         10G  105M  9.9G   2% /var/tmp
/dev/mapper/rhvh-var_log_audit                  2.0G   48M  2.0G   3% /var/log/audit
tmpfs                                           366M     0  366M   0% /run/user/0

5GB /var and 10GB /var/tmp. So the bug is fixed, change bug status to VERIFIED.

Comment 2 Sandro Bonazzola 2022-04-20 06:33:59 UTC
This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.