Debian Jessie LVM Issues - Full Disk, Large Logs & gParted

Kernels & Hardware, configuring network, installing services

Debian Jessie LVM Issues - Full Disk, Large Logs & gParted

Postby nathank1989 » 2015-09-23 15:31

Hello again. So, my issues since upgrading to Jessie seem to compound. When I fix one issue, two more arise.
Right now, I have a full system disk. I have no idea how it got so full. So I started poking around. I ran
Code: Select all
find / -type f -size +50M -exec ls -lh {} \; | awk '{ print $NF ": " $5 }'
Found a few files I could delete, and did, but I also found
Code: Select all
/var/log/syslog.1: 33G
/var/log/messages: 33G
/var/log/user.log: 33G

What I find strange is that they're all exactly 33G each. So that accounts for the missing 99GB I deleted them, however only recovered 27Gb. Whats weird is when I type df -h I get
Code: Select all
Filesystem      Size  Used Avail Use% Mounted on
/dev/dm-0       106G   74G   27G  74% /
udev             10M     0   10M   0% /dev
tmpfs           3.2G  9.7M  3.2G   1% /run
tmpfs           7.9G     0  7.9G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/sda1       228M   27M  189M  13% /boot
/dev/sdb1       1.9T   62G  1.8T   4% /media/ntfs
tmpfs           1.6G     0  1.6G   0% /run/user/0

What are the tmpfs's and how can I reclaim that space, and what is /dev/dm-0 and why is that taking up so much space?
I have 2 LVGs vgdisplay -v
Code: Select all
root@SETV-007-WOWZA:~# vgdisplay -v
    DEGRADED MODE. Incomplete RAID LVs will be processed.
    Finding all volume groups
    Finding volume group "WOWZASERVER"
  --- Volume group ---
  VG Name               WOWZASERVER
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  3
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                2
  Open LV               2
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               111.55 GiB
  PE Size               4.00 MiB
  Total PE              28556
  Alloc PE / Size       28556 / 111.55 GiB
  Free  PE / Size       0 / 0
  VG UUID               ml8xX2-tlTN-wH8p-oXxU-ImAf-GUkb-uBA7B9

  --- Logical volume ---
  LV Path                /dev/WOWZASERVER/root
  LV Name                root
  VG Name                WOWZASERVER
  LV UUID                VzeRl1-1jAx-kuGO-qTY5-ae7W-uU6a-e5MFS1
  LV Write Access        read/write
  LV Creation host, time WOWZASERVER, 2015-03-31 16:47:09 -0400
  LV Status              available
  # open                 1
  LV Size                106.98 GiB
  Current LE             27388
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:0

  --- Logical volume ---
  LV Path                /dev/WOWZASERVER/swap_1
  LV Name                swap_1
  VG Name                WOWZASERVER
  LV UUID                nx8WD0-oU4d-WrHI-Pnsy-0cuE-IjK5-Mk8qaj
  LV Write Access        read/write
  LV Creation host, time WOWZASERVER, 2015-03-31 16:47:09 -0400
  LV Status              available
  # open                 2
  LV Size                4.56 GiB
  Current LE             1168
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:1

  --- Physical volumes ---
  PV Name               /dev/sda5
  PV UUID               AFVBeD-s1Y6-fVHC-5Zc4-53Tk-atS7-4bIQpu
  PV Status             allocatable
  Total PE / Free PE    28556 / 0

What am I missing?

After deleting the log files, I was able to regain access to my GDM session. But I still cant find out what /dev/dm-0 is, and where all the 75 GB is being taken up.

EDIT:
I just noticed, however, even though I can access the drive A-OK via browser, terminal, and web services (Our wowza) when I enter gParted I get this error for sda, my primary OS drive!
Code: Select all
  Libparted Bug Found!
    Error informing the kernel about modifications to partition /dev/sda2 -- Invalid argument. This means Linux won't know about any changes you made to /dev/sda2 until you reboot -- so you shouldn't mount it or use it in any way before rebooting


Now that I'm in gParted I see 3 partitions:
http://imgur.com/MN2NmTr

It reports now, that I have used ALL of my disk space.
Post Log delete, and fresh reboot, this is what
Code: Select all
df -h
outputs

Code: Select all
Filesystem      Size  Used Avail Use% Mounted on
/dev/dm-0       106G  8.7G   92G   9% /
udev             10M     0   10M   0% /dev
tmpfs           3.2G  9.8M  3.2G   1% /run
tmpfs           7.9G   80K  7.9G   1% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/sda1       228M   27M  189M  13% /boot
/dev/sdb1       1.9T   68G  1.8T   4% /media/ntfs
tmpfs           1.6G   24K  1.6G   1% /run/user/1000
tmpfs           1.6G     0  1.6G   0% /run/user/0

What the heck is going on? lol
nathank1989
 
Posts: 5
Joined: 2014-05-04 11:21

Return to System configuration

Who is online

Users browsing this forum: No registered users and 7 guests

fashionable