dm-0 is full causing mysql to stop

asked 2016-10-31 17:39:22 -0500

kaleem gravatar image

updated 2016-11-04 15:44:25 -0500

rbowen gravatar image

I'm installing Mitaka on Ubuntu 14.04 and my /dev/dm-0 file which is located on root is only 4.1G and 100% full. I've tried changing the size from the vsphere menu and even tried the lvextend & resize2fs bullshit commands that never work but dm-0 is unaffected.

How do I delete some extra log files on there/and or extend the size of that volume? and please provide CLI commands if you know them, I am kind of new to ubuntu. Thank you.

root@controller1:~# df -h
Filesystem                        Size  Used Avail Use% Mounted on
udev                              7.9G  428K  7.9G   1% /dev
tmpfs                             1.6G  800K  1.6G   1% /run
/dev/dm-0                         4.1G  4.1G     0 100% /
none                              4.0K     0  4.0K   0% /sys/fs/cgroup
none                              5.0M     0  5.0M   0% /run/lock
none                              7.9G     0  7.9G   0% /run/shm
none                              100M     0  100M   0% /run/user
/dev/sda1                         236M   71M  153M  32% /boot
/dev/mapper/controller1--vg-home   11G   28M   11G   1% /home
overflow                          1.0M     0  1.0M   0% /tmp

root@controller1:~# fdisk -l
Disk /dev/sda: 68.7 GB, 68719476736 bytes
255 heads, 63 sectors/track, 8354 cylinders, total 134217728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00013dc4

Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      499711      248832   83  Linux
/dev/sda2          501758    33552383    16525313    5  Extended
/dev/sda5          501760    33552383    16525312   8e  Linux LVM

Disk /dev/sdb: 17.2 GB, 17179869184 bytes
255 heads, 63 sectors/track, 2088 cylinders, total 33554432 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/mapper/controller1--vg-root: 4567 MB, 4567597056 bytes
80 heads, 36 sectors/track, 3097 cylinders, total 8921088 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x344a8654

Device Boot      Start         End      Blocks   Id  System
/dev/mapper/controller1--vg-root1   *     5872320     8919359     1523520   83  Linux

Disk /dev/mapper/controller1--vg-swap_1: 574 MB, 574619648 bytes
255 heads, 63 sectors/track, 69 cylinders, total 1122304 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/controller1--vg-swap_1 doesn't contain a valid partition table

Disk /dev/mapper/controller1--vg-home: 11.8 GB, 11752439808 bytes
255 heads, 63 sectors/track, 1428 cylinders, total 22953984 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/controller1--vg-home doesn't contain a valid partition table

edit retag flag offensive close merge delete

Comments

4GB is a bit small. Perhaps you can make room by deleting log files (see /var/log, and use find +size to find large files), but the condition will come back to haunt you. To increase the size, you have to first increase the size of your disk, from vsphere.

Bernd Bausch gravatar imageBernd Bausch ( 2016-11-01 06:57:03 -0500 )edit

Then ensure that the guest is aware of the new size: echo > /sys/block/sda/device/rescan should do the trick, or a reboot. Then you can use lvextend and resize the filesystem. Alternatively, add another disk to the guest, make it a physical volume, add it to the root VG and lvextend.

Bernd Bausch gravatar imageBernd Bausch ( 2016-11-01 06:59:20 -0500 )edit

To understand how your disks are used, by the way, use the commands lsblk, blkid and the LVM commands pvs, vgs and lvs. Concise and very useful.

Bernd Bausch gravatar imageBernd Bausch ( 2016-11-01 07:01:31 -0500 )edit