At least 94MB more space needed on the /var filesystem.

Latest response

Error Summary

Disk Requirements:
At least 94MB more space needed on the /var filesystem.


I just did a yum update on a new server I just from Dell.

I'm not sure how to proceed so I don't mess up my file system.

I can not update because /var is full.

I've got 2 2tb hard-drive.


Notes:
uname -a
3.10.0-123.el7.x86_64 #1 SMP Mon May 5 11:16:57 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux

df -h

Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00 1014M 67M 948M 7% /
devtmpfs 12G 0 12G 0% /dev
tmpfs 12G 0 12G 0% /dev/shm
tmpfs 12G 8.6M 12G 1% /run
tmpfs 12G 0 12G 0% /sys/fs/cgroup
/dev/mapper/VolGroup00-LogVol02 7.0G 3.0G 4.1G 43% /usr
/dev/mapper/VolGroup00-LogVol05 1014M 151M 864M 15% /home
/dev/sda3 197M 64M 134M 33% /boot
/dev/mapper/VolGroup00-LogVol04 5.0G 4.8G 222M 96% /var
/dev/mapper/VolGroup00-LogVol03 509M 34M 476M 7% /tmp
[root@tritechsc lab]#

Responses

I'm missing something, here. You say you've got two 1TiB drives, but I'm only seeing like 14GiB allocated. I'm assuming you've got unallocated space - possibly even in VolGroup00, already. What does vgdisplay -s and lsblk show?

This helped:

# lsblk 
NAME                    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                       8:0    0   1.8T  0 disk 
├─sda1                    8:1    0 349.5M  0 part 
├─sda2                    8:2    0     5G  0 part 
├─sda3                    8:3    0   200M  0 part /boot
├─sda4                    8:4    0     1K  0 part 
└─sda5                    8:5    0   1.8T  0 part 
  ├─VolGroup00-LogVol01 253:0    0  11.7G  0 lvm  [SWAP]
  ├─VolGroup00-LogVol00 253:1    0     1G  0 lvm  /
  ├─VolGroup00-LogVol02 253:2    0    10G  0 lvm  /usr
  ├─VolGroup00-LogVol05 253:3    0     2G  0 lvm  /home
  ├─VolGroup00-LogVol04 253:4    0    16G  0 lvm  /var
  └─VolGroup00-LogVol03 253:5    0   512M  0 lvm  /tmp
sdb                       8:16   0  19.3G  0 disk 
sr0                      11:0    1  1024M  0 rom  
[root@tritechsc updates]# vgdisplay -s 
  "VolGroup00" 1.80 TiB  [41.22 GiB used / 1.76 TiB free]

I do believe I am making progress.

Hi craigcoleman,

By seeing the out of df -h, i can see that you are using the LVM,

/var is mount on on /dev/mapper/VolGroup00-LogVol04 LVM volume so you can increase the size of LVM using below method, if your your server is hosted on VMware by adding a new Virtual disk or adding a physical if hosted on a physical server you can do this easily. follow the below link.

https://www.rootusers.com/how-to-increase-the-size-of-a-linux-lvm-by-adding-a-new-disk/

Hope it will help you.

This is not a VM. The OS was installed when I got the server from Dell .
I've already registered it with Redhat without looking at the partition table. Lesson learned.

Dell told me to use fdisk or parted and suggested: https://access.redhat.com/solutions/4009

I'm considering an old fashion reinstall.

Thanks for the lines.

The size allocated for root and other file systems is too small for enterprise level usage. Hence, try increasing the size of logical volumes instead of re-installation which I feel ideal solution. Yes, the above article provided by craigcoleman is a good one for changing root lvm siz.e

Thank you.

I issued the following commands: xfs_info /dev/VolGroup00/LogVol04 and xfs_growfs /dev/VolGroup00/LogVol04

I I got /var to resize a bit.
data blocks changed from 1310720 to 1572864

I tried the same thing with / with no luck. xfs_growfs /dev/VolGroup00/LogVol00

I did not use -n

From this example: https://access.redhat.com/solutions/57263

I do believe I need to do the following but I am not sure: vextend -L +500M /dev/mapper/VolGroup-lv_root -r

#xfs_info /dev/VolGroup00/LogVol04 
meta-data=/dev/mapper/VolGroup00-LogVol04 isize=256    agcount=4, agsize=327680 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=0
data     =                       bsize=4096   blocks=1310720, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=0
log      =internal               bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
[root@tritechsc ~]# xfs_growfs /dev/VolGroup00/LogVol04 
meta-data=/dev/mapper/VolGroup00-LogVol04 isize=256    agcount=4, agsize=327680 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=0
data     =                       bsize=4096   blocks=1310720, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=0
log      =internal               bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
data blocks changed from 1310720 to 1572864
[root@tritechsc ~]# xfs_info /dev/VolGroup00/LogVol04 
meta-data=/dev/mapper/VolGroup00-LogVol04 isize=256    agcount=5, agsize=327680 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=0
data     =                       bsize=4096   blocks=1572864, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=0
log      =internal               bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

Just did the following add added 10G to /var How I just need to do some math and expand everything else. Please throw me a bone if I am on the right track.

# lvextend -L +10G /dev/VolGroup00/LogVol04 -r
  Size of logical volume VolGroup00/LogVol04 changed from 6.00 GiB (192 extents) to 16.00 GiB (512 extents).
  Logical volume VolGroup00/LogVol04 successfully resized.
meta-data=/dev/mapper/VolGroup00-LogVol04 isize=256    agcount=5, agsize=327680 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=0        finobt=0 spinodes=0
data     =                       bsize=4096   blocks=1572864, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=0
log      =internal               bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
data blocks changed from 1572864 to 4194304
[root@tritechsc updates]# lsblk
NAME                    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                       8:0    0   1.8T  0 disk 
├─sda1                    8:1    0 349.5M  0 part 
├─sda2                    8:2    0     5G  0 part 
├─sda3                    8:3    0   200M  0 part /boot
├─sda4                    8:4    0     1K  0 part 
└─sda5                    8:5    0   1.8T  0 part 
  ├─VolGroup00-LogVol01 253:0    0  11.7G  0 lvm  [SWAP]
  ├─VolGroup00-LogVol00 253:1    0     1G  0 lvm  /
  ├─VolGroup00-LogVol02 253:2    0    10G  0 lvm  /usr
  ├─VolGroup00-LogVol05 253:3    0     2G  0 lvm  /home
  ├─VolGroup00-LogVol04 253:4    0    16G  0 lvm  /var
  └─VolGroup00-LogVol03 253:5    0   512M  0 lvm  /tmp
sdb                       8:16   0  19.3G  0 disk 
sr0                      11:0    1  1024M  0 rom  

From your statement I could say that "/dev/sda5" partition has been allocated complete space out of which you've allocated around 41GB of space to "swap, /, /usr/, /home, /var, & /tmp". So, there is still space remaining which you can use. Run "vgs" command and check out free space which can used to create a new or to extend the space of existing lv. So, here /dev/sda5 is your physical volume. Also, show "pvs, lvs" outputs.

@craigcoleman: yes, you're on the right track. You might want to use the "lvs", "vgs" and "pvs" commands: although the total overview given by "lsblk" is nice, "vgs" will tell you directly how much capacity you have available for extending any logical volumes (LogVols) within a volume group (VolGroup). And you've already discovered the commands to use for the extension.

Thank you!

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.