Would somebody help me sort out what I've got here? This setup I've inherited because the admin quit. I'm not sure if some level of raid is setup. This is an IBM blade server in a chassis, it's directly attached storage, no Sans. The IBM Director app is down so I can't use it to check the number of drive, etc.
My immediate problem is I'm out of disk space allocated to pve-data.
df -h if I add up the gb in the size column I come up with roughly a 150 gb. fdisk -l tells me that /dev/sda is a 145 gb disk. I was thinking everything is loaded on just this one drive.
But the numbers don't add up.
Then I've got /dev/sdb/ that's a 293gb drive that doesn't contain a valid partition table.
Is this a drive that's not being used?
Or does Proxmox have something to do with the o\s not seeing it as being a valid partition table?
If you need additional info let me know. And thanks in advance for any helpful suggestions. I've read the doc on Storage for starters.
Proxmox version 1.5
Storage:
Storage Name Type Enabled Active Shared Used(GB) Capacity
local Directory Yes Yes No 84.16 85.36
backups LVM Yes Yes Yes 131.47 135.47
vzbackups Directory Yes Yes Yes 1.00 31.53
server:/etc# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/pve/root 34G 1020M 31G 4% /
tmpfs 5.9G 0 5.9G 0% /lib/init/rw
udev 10M 2.7M 7.4M 27% /dev
tmpfs 5.9G 4.0K 5.9G 1% /dev/shm
/dev/mapper/pve-data 86G 85G 1.2G 99% /var/lib/vz
/dev/sda1 504M 32M 448M 7% /boot
overflow 1.0M 4.0K 1020K 1% /tmp
server:/etc# more fstab
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext3 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext3 defaults 0 1
UUID=203c49a5-6a5c-486a-9a8e-dc79fcf1ba4f /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
server:/# fdisk -l
Disk /dev/sda: 145.9 GB, 145999527936 bytes
255 heads, 63 sectors/track, 17750 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 * 1 66 524288 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 66 17750 142052555 8e Linux LVM
Disk /dev/sdb: 293.3 GB, 293389467648 bytes
255 heads, 63 sectors/track, 35669 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/dm-0: 11.8 GB, 11811160064 bytes
255 heads, 63 sectors/track, 1435 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 36.2 GB, 36238786560 bytes
255 heads, 63 sectors/track, 4405 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2: 93.1 GB, 93117743104 bytes
255 heads, 63 sectors/track, 11320 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-2 doesn't contain a valid partition table
My immediate problem is I'm out of disk space allocated to pve-data.
df -h if I add up the gb in the size column I come up with roughly a 150 gb. fdisk -l tells me that /dev/sda is a 145 gb disk. I was thinking everything is loaded on just this one drive.
But the numbers don't add up.
Then I've got /dev/sdb/ that's a 293gb drive that doesn't contain a valid partition table.
Is this a drive that's not being used?
Or does Proxmox have something to do with the o\s not seeing it as being a valid partition table?
If you need additional info let me know. And thanks in advance for any helpful suggestions. I've read the doc on Storage for starters.
Proxmox version 1.5
Storage:
Storage Name Type Enabled Active Shared Used(GB) Capacity
local Directory Yes Yes No 84.16 85.36
backups LVM Yes Yes Yes 131.47 135.47
vzbackups Directory Yes Yes Yes 1.00 31.53
server:/etc# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/pve/root 34G 1020M 31G 4% /
tmpfs 5.9G 0 5.9G 0% /lib/init/rw
udev 10M 2.7M 7.4M 27% /dev
tmpfs 5.9G 4.0K 5.9G 1% /dev/shm
/dev/mapper/pve-data 86G 85G 1.2G 99% /var/lib/vz
/dev/sda1 504M 32M 448M 7% /boot
overflow 1.0M 4.0K 1020K 1% /tmp
server:/etc# more fstab
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext3 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext3 defaults 0 1
UUID=203c49a5-6a5c-486a-9a8e-dc79fcf1ba4f /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
server:/# fdisk -l
Disk /dev/sda: 145.9 GB, 145999527936 bytes
255 heads, 63 sectors/track, 17750 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 * 1 66 524288 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 66 17750 142052555 8e Linux LVM
Disk /dev/sdb: 293.3 GB, 293389467648 bytes
255 heads, 63 sectors/track, 35669 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/dm-0: 11.8 GB, 11811160064 bytes
255 heads, 63 sectors/track, 1435 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 36.2 GB, 36238786560 bytes
255 heads, 63 sectors/track, 4405 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2: 93.1 GB, 93117743104 bytes
255 heads, 63 sectors/track, 11320 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-2 doesn't contain a valid partition table