LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Enterprise Linux Forums > Linux - Enterprise
User Name
Password
Linux - Enterprise This forum is for all items relating to using Linux in the Enterprise.

Notices


Reply
  Search this Thread
Old 11-19-2008, 01:51 PM   #1
pobman
Member
 
Registered: Jun 2005
Location: Wellington, New Zealand
Distribution: Fedora 9
Posts: 31

Rep: Reputation: 16
HELP I don't understand my LVM, no space left??


Hi all,

I have a problem to day with an LVM on a machine I have been asked
to "sort out"
I am not too familiar with LVM so wondered if someone could look at my
output and put me straight.

This is what I think I can see:

The VolGroup00 contains 2 physical disks, on is 29.90GB and one at
75.00GB these are on a san. This gives me a LOGVol00 of 102.91GB and a
LogVol01 of 1.94GB according to lvdisplay.

Total LE are 3355 and they are 32M in size this = 104.8GB

It shows I have no extents free so ???
Why can I only see 28G of disk space?
How do I check and create more
space for the root filesystem?
The only thing I can think of is I have exceeded the number of extents allowed?
if so why did it show 3355 in use?

Cheers

Code:
[root@NZAKLEIPWEBRH3 ~]# cat /etc/fstab
/dev/VolGroup00/LogVol00 /                       ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
/dev/VolGroup00/LogVol01 swap                    swap    defaults        0 0

[root@NZAKLEIPWEBRH3 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      28G   22G  4.4G  83% /
/dev/sda1              99M   32M   62M  34% /boot
tmpfs                 2.0G     0  2.0G   0% /dev/shm

[root@NZAKLEIPWEBRH3 ~]# fdisk -l

Disk /dev/sda: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   83  Linux
/dev/sda2              14        3916    31350847+  8e  Linux LVM

Disk /dev/sdc: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1          13      104391   83  Linux
/dev/sdc2              14        3916    31350847+  8e  Linux LVM

Disk /dev/sdg: 80.5 GB, 80530636800 bytes
255 heads, 63 sectors/track, 9790 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

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

Disk /dev/sdh: 80.5 GB, 80530636800 bytes
255 heads, 63 sectors/track, 9790 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

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

[root@NZAKLEIPWEBRH3 ~]# pvdisplay
 /dev/sdb: read failed after 0 of 4096 at 0: Input/output error
 Found duplicate PV pDEdbop5MSsClGwaXKeL3DzKU6HXSDHK: using /dev/sdc2
not /dev/                                             sda2
 /dev/sdd: read failed after 0 of 4096 at 0: Input/output error
 /dev/sde: read failed after 0 of 4096 at 0: Input/output error
 /dev/sdf: read failed after 0 of 4096 at 0: Input/output error
 Found duplicate PV uhQBHbhkUPxQkMg1quWpBuoEk4KrJ6Sa: using /dev/sdh
not /dev/s                                             dg
 --- Physical volume ---
 PV Name               /dev/sdc2
 VG Name               VolGroup00
 PV Size               29.90 GB / not usable 24.06 MB
 Allocatable           yes (but full)
 PE Size (KByte)       32768
 Total PE              956
 Free PE               0
 Allocated PE          956
 PV UUID               pDEdbo-p5MS-sClG-waXK-eL3D-zKU6-HXSDHK

 --- Physical volume ---
 PV Name               /dev/sdh
 VG Name               VolGroup00
 PV Size               75.00 GB / not usable 32.00 MB
 Allocatable           yes (but full)
 PE Size (KByte)       32768
 Total PE              2399
 Free PE               0
 Allocated PE          2399
 PV UUID               uhQBHb-hkUP-xQkM-g1qu-WpBu-oEk4-KrJ6Sa

[root@NZAKLEIPWEBRH3 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      28G   22G  4.4G  83% /
/dev/sda1              99M   32M   62M  34% /boot
tmpfs                 2.0G     0  2.0G   0% /dev/shm

[root@NZAKLEIPWEBRH3 ~]# lvdisplay
 /dev/sdb: read failed after 0 of 4096 at 0: Input/output error
 Found duplicate PV pDEdbop5MSsClGwaXKeL3DzKU6HXSDHK: using /dev/sdc2
not /dev/sda2
 /dev/sdd: read failed after 0 of 4096 at 0: Input/output error
 /dev/sde: read failed after 0 of 4096 at 0: Input/output error
 /dev/sdf: read failed after 0 of 4096 at 0: Input/output error
 Found duplicate PV uhQBHbhkUPxQkMg1quWpBuoEk4KrJ6Sa: using /dev/sdh
not /dev/sdg
 --- Logical volume ---
 LV Name                /dev/VolGroup00/LogVol00
 VG Name                VolGroup00
 LV UUID                1hSztS-wn5X-10Ok-sxpa-UDOs-6oao-onPRlZ
 LV Write Access        read/write
 LV Status              available
 # open                 2
 LV Size                102.91 GB
 Current LE             3293
 Segments               2
 Allocation             inherit
 Read ahead sectors     auto
 - currently set to     256
 Block device           253:0

 --- Logical volume ---
 LV Name                /dev/VolGroup00/LogVol01
 VG Name                VolGroup00
 LV UUID                8kSh33-Cls6-y7pg-xHwp-4bbq-3TGX-07gr9Z
 LV Write Access        read/write
 LV Status              available
 # open                 1
 LV Size                1.94 GB
 Current LE             62
 Segments               1
 Allocation             inherit
 Read ahead sectors     auto
 - currently set to     256
 Block device           253:1
  [root@NZAKLEIPWEBRH3 ~]# vgdisplay
  /dev/sdb: read failed after 0 of 4096 at 0: Input/output error
  Found duplicate PV pDEdbop5MSsClGwaXKeL3DzKU6HXSDHK: using /dev/sdc2 not /dev/sda2
  /dev/sdd: read failed after 0 of 4096 at 0: Input/output error
  /dev/sde: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdf: read failed after 0 of 4096 at 0: Input/output error
  Found duplicate PV uhQBHbhkUPxQkMg1quWpBuoEk4KrJ6Sa: using /dev/sdh not /dev/sdg
  --- Volume group ---
  VG Name               VolGroup00
  System ID
  Format                lvm2
  Metadata Areas        2
  Metadata Sequence No  5
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                2
  Open LV               2
  Max PV                0
  Cur PV                2
  Act PV                2
  VG Size               104.84 GB
  PE Size               32.00 MB
  Total PE              3355
  Alloc PE / Size       3355 / 104.84 GB
  Free  PE / Size       0 / 0
  VG UUID               3xZhBf-G8nY-Y21L-oO9P-iIf7-S4uQ-fcVfT8

Last edited by pobman; 11-19-2008 at 01:57 PM.
 
Old 11-19-2008, 02:03 PM   #2
rayfordj
Member
 
Registered: Feb 2008
Location: Texas
Distribution: Fedora, RHEL, CentOS
Posts: 488

Rep: Reputation: 78
is it possible that the root LV (/dev/VolGroup00/LogVol00) was at one point smaller? say, ~28GB? and at some point, it was realized that it needed to be bigger so an lvextend was run on it but never anything done to grow the filesystem?

depending on OS/Release/Version/...:
Code:
resize2fs /dev/VolGroup00/LogVol00
  -or-
resize2fs /
  -or-
ext2online /
 
Old 11-19-2008, 03:11 PM   #3
pobman
Member
 
Registered: Jun 2005
Location: Wellington, New Zealand
Distribution: Fedora 9
Posts: 31

Original Poster
Rep: Reputation: 16
Is there a way to this out without causing any damage as it is a clients server?
 
Old 11-19-2008, 08:55 PM   #4
rayfordj
Member
 
Registered: Feb 2008
Location: Texas
Distribution: Fedora, RHEL, CentOS
Posts: 488

Rep: Reputation: 78
Quote:
Originally Posted by pobman View Post
Is there a way to this out without causing any damage as it is a clients server?
yup, one of the following should do it with the filesystem on-line and running...
Code:
resize2fs /dev/VolGroup00/LogVol00
  -or-
resize2fs /
  -or-
ext2online /
performed successfully on dozens of customers' systems.

As always, should have a backup of any data worth keeping and you would need to assess risk/reward given a scenario.

;-)
 
Old 11-19-2008, 09:01 PM   #5
jschiwal
LQ Guru
 
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 682Reputation: 682Reputation: 682Reputation: 682Reputation: 682Reputation: 682
I don't like the I/O errors that showed up. Could the /dev/sdc hard drive be going bad?
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Trying to understand LVM. arashi256 Linux - Newbie 4 10-20-2008 01:17 AM
LVM and No Space Left On Device llin Linux - Software 4 07-29-2008 01:04 AM
LVM error: File Descriptor left open kapil.hazarika Linux - Software 1 06-18-2007 08:03 PM
No space left on device even though it has free space? enine Linux - General 8 05-30-2007 04:22 PM
"no space left on device" - But df shows free space! monita Linux - General 7 03-30-2004 01:14 PM

LinuxQuestions.org > Forums > Enterprise Linux Forums > Linux - Enterprise

All times are GMT -5. The time now is 07:49 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration