* [linux-lvm] Disk space reporting inconsistencies
@ 2006-01-18 11:31 Chris bolton
2006-01-19 7:55 ` Chris bolton
2006-01-19 19:50 ` [linux-lvm] Disk space reporting inconsistencies - lvm half baked Jed Donnelley
0 siblings, 2 replies; 6+ messages in thread
From: Chris bolton @ 2006-01-18 11:31 UTC (permalink / raw)
To: linux-lvm
Hi,
just added a new PV to my VG but to me there seems to be an
inconsistency between what lvm says is the disk space and what df says.
pvscan
PV /dev/sda2 VG VolGroup00 lvm2 [68.38 GB / 0 free]
PV /dev/sdb VG VolGroup00 lvm2 [68.50 GB / 0 free]
PV /dev/hdc2 VG VolGroup00 lvm2 [37.12 GB / 0 free]
PV /dev/hdb1 VG VolGroup00 lvm2 [37.22 GB / 0 free]
PV /dev/hdd1 VG VolGroup00 lvm2 [37.22 GB / 0 free]
PV /dev/hde1 VG VolGroup00 lvm2 [37.25 GB / 0 free]
Total: 6 [285.69 GB] / in use: 6 [285.69 GB] / in no VG: 0 [0 ]
df -h
/dev/mapper/VolGroup00-LogVol00 265G 227G 28G 90% /
I tried resizing the filesystem but it just says this..
ext2online /dev/VolGroup00/LogVol00
ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b
ext2online: ext2_ioctl: No space left on device
ext2online: unable to resize /dev/mapper/VolGroup00-LogVol00
Am I missing something obvious here? or have I ballsed it up along the way?
Cheers,
Chris.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [linux-lvm] Disk space reporting inconsistencies 2006-01-18 11:31 [linux-lvm] Disk space reporting inconsistencies Chris bolton @ 2006-01-19 7:55 ` Chris bolton 2006-01-19 20:00 ` Matt P 2006-03-10 20:26 ` cbolton 2006-01-19 19:50 ` [linux-lvm] Disk space reporting inconsistencies - lvm half baked Jed Donnelley 1 sibling, 2 replies; 6+ messages in thread From: Chris bolton @ 2006-01-19 7:55 UTC (permalink / raw) To: LVM general discussion and development nevermind got it sussed, lvm is using 10^9 for a gigabyte while df is using 1024^3 well it would appear that way anyway. > Hi, > > just added a new PV to my VG but to me there seems to be an > inconsistency between what lvm says is the disk space and what df says. > > pvscan > PV /dev/sda2 VG VolGroup00 lvm2 [68.38 GB / 0 free] > PV /dev/sdb VG VolGroup00 lvm2 [68.50 GB / 0 free] > PV /dev/hdc2 VG VolGroup00 lvm2 [37.12 GB / 0 free] > PV /dev/hdb1 VG VolGroup00 lvm2 [37.22 GB / 0 free] > PV /dev/hdd1 VG VolGroup00 lvm2 [37.22 GB / 0 free] > PV /dev/hde1 VG VolGroup00 lvm2 [37.25 GB / 0 free] > Total: 6 [285.69 GB] / in use: 6 [285.69 GB] / in no VG: 0 [0 ] > > df -h > /dev/mapper/VolGroup00-LogVol00 265G 227G 28G 90% / > > I tried resizing the filesystem but it just says this.. > > ext2online /dev/VolGroup00/LogVol00 > ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b > ext2online: ext2_ioctl: No space left on device > > ext2online: unable to resize /dev/mapper/VolGroup00-LogVol00 > > Am I missing something obvious here? or have I ballsed it up along the > way? > > Cheers, > Chris. > > _______________________________________________ > linux-lvm mailing list > linux-lvm@redhat.com > https://www.redhat.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [linux-lvm] Disk space reporting inconsistencies 2006-01-19 7:55 ` Chris bolton @ 2006-01-19 20:00 ` Matt P 2006-03-10 20:26 ` cbolton 1 sibling, 0 replies; 6+ messages in thread From: Matt P @ 2006-01-19 20:00 UTC (permalink / raw) To: LVM general discussion and development Actually df is telling you the space available within the Filesystem while pvscan is telling you the space available on the logical volume. Try df -H and see if it matches your pvscan, the capital "H" tells df to use powers of 1000 instead of 1024. On 1/19/06, Chris bolton <cbolton@rarr.org.uk> wrote: > nevermind got it sussed, lvm is using 10^9 for a gigabyte while df is > using 1024^3 > > well it would appear that way anyway. > > Hi, > > > > just added a new PV to my VG but to me there seems to be an > > inconsistency between what lvm says is the disk space and what df says. > > > > pvscan > > PV /dev/sda2 VG VolGroup00 lvm2 [68.38 GB / 0 free] > > PV /dev/sdb VG VolGroup00 lvm2 [68.50 GB / 0 free] > > PV /dev/hdc2 VG VolGroup00 lvm2 [37.12 GB / 0 free] > > PV /dev/hdb1 VG VolGroup00 lvm2 [37.22 GB / 0 free] > > PV /dev/hdd1 VG VolGroup00 lvm2 [37.22 GB / 0 free] > > PV /dev/hde1 VG VolGroup00 lvm2 [37.25 GB / 0 free] > > Total: 6 [285.69 GB] / in use: 6 [285.69 GB] / in no VG: 0 [0 ] > > > > df -h > > /dev/mapper/VolGroup00-LogVol00 265G 227G 28G 90% / > > > > I tried resizing the filesystem but it just says this.. > > > > ext2online /dev/VolGroup00/LogVol00 > > ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b > > ext2online: ext2_ioctl: No space left on device > > > > ext2online: unable to resize /dev/mapper/VolGroup00-LogVol00 > > > > Am I missing something obvious here? or have I ballsed it up along the > > way? > > > > Cheers, > > Chris. > > > > _______________________________________________ > > linux-lvm mailing list > > linux-lvm@redhat.com > > https://www.redhat.com/mailman/listinfo/linux-lvm > > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ > > _______________________________________________ > linux-lvm mailing list > linux-lvm@redhat.com > https://www.redhat.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [linux-lvm] Disk space reporting inconsistencies 2006-01-19 7:55 ` Chris bolton 2006-01-19 20:00 ` Matt P @ 2006-03-10 20:26 ` cbolton [not found] ` <6c3e3c670603101323s6ccb11f2kfeea93718cfd162a@mail.gmail.com> 1 sibling, 1 reply; 6+ messages in thread From: cbolton @ 2006-03-10 20:26 UTC (permalink / raw) To: LVM general discussion and development Repling to my own mail here but its on subject. Just added a new drive to the machine, added it to the volume group, moved everything from /dev/hde1 to /dev/hda, removed hde1 from the VG and removed in physicaly from the machine. Great everything went fine, only the new drive is 60gigs so in moving its only used 40gigs. Not a problem I thought, I'll just extend the logical volume, so I did lvextend and extended it by 20gigs. This seemed to work as well.. PV /dev/sda2 VG VolGroup00 lvm2 [68.38 GB / 0 free] PV /dev/sdb VG VolGroup00 lvm2 [68.50 GB / 0 free] PV /dev/hdc2 VG VolGroup00 lvm2 [37.12 GB / 0 free] PV /dev/hdb1 VG VolGroup00 lvm2 [37.22 GB / 0 free] PV /dev/hdd1 VG VolGroup00 lvm2 [37.22 GB / 0 free] PV /dev/hda VG VolGroup00 lvm2 [57.25 GB / 0 free] Total: 6 [305.69 GB] / in use: 6 [305.69 GB] / in no VG: 0 [0 ] but df -h says... Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol00 265G 248G 6.8G 98% / /dev/sda1 99M 73M 22M 78% /boot /dev/shm 252M 0 252M 0% /dev/shm I thought I'd need to extend the file system so i did ext2online /dev/VolGroup00/LogVol00 but its says... ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b ext2online: ext2_ioctl: No space left on device ext2online: unable to resize /dev/mapper/VolGroup00-LogVol00 Any ideas? I'm plain out. Cheers, Chris On Thu, January 19, 2006 7:55 am, Chris bolton wrote: > nevermind got it sussed, lvm is using 10^9 for a gigabyte while df is > using 1024^3 > > well it would appear that way anyway. >> Hi, >> >> >> just added a new PV to my VG but to me there seems to be an >> inconsistency between what lvm says is the disk space and what df says. >> >> >> pvscan PV /dev/sda2 VG VolGroup00 lvm2 [68.38 GB / 0 free] >> PV /dev/sdb VG VolGroup00 lvm2 [68.50 GB / 0 free] >> PV /dev/hdc2 VG VolGroup00 lvm2 [37.12 GB / 0 free] >> PV /dev/hdb1 VG VolGroup00 lvm2 [37.22 GB / 0 free] >> PV /dev/hdd1 VG VolGroup00 lvm2 [37.22 GB / 0 free] >> PV /dev/hde1 VG VolGroup00 lvm2 [37.25 GB / 0 free] >> Total: 6 [285.69 GB] / in use: 6 [285.69 GB] / in no VG: 0 [0 ] >> >> >> df -h /dev/mapper/VolGroup00-LogVol00 265G 227G 28G 90% / >> >> >> I tried resizing the filesystem but it just says this.. >> >> >> ext2online /dev/VolGroup00/LogVol00 ext2online v1.1.18 - 2001/03/18 for >> EXT2FS 0.5b >> ext2online: ext2_ioctl: No space left on device >> >> >> ext2online: unable to resize /dev/mapper/VolGroup00-LogVol00 >> >> >> Am I missing something obvious here? or have I ballsed it up along the >> way? >> >> Cheers, >> Chris. >> >> >> _______________________________________________ >> linux-lvm mailing list linux-lvm@redhat.com >> https://www.redhat.com/mailman/listinfo/linux-lvm >> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ > > _______________________________________________ > linux-lvm mailing list linux-lvm@redhat.com > https://www.redhat.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ > ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <6c3e3c670603101323s6ccb11f2kfeea93718cfd162a@mail.gmail.com>]
* Re: [linux-lvm] Disk space reporting inconsistencies [not found] ` <6c3e3c670603101323s6ccb11f2kfeea93718cfd162a@mail.gmail.com> @ 2006-03-10 21:45 ` cbolton 0 siblings, 0 replies; 6+ messages in thread From: cbolton @ 2006-03-10 21:45 UTC (permalink / raw) To: linux-lvm hmm yeah, but this machine doesnt have space for a cdrom to be attached nor a floppy drive so how could I resize offline? would there be away? On Fri, March 10, 2006 9:23 pm, Chad Rebuck wrote: > I am just trying to fix my own problems here so don't expect what I > say will fix your troubles...but try running ext2online with -d and -v to > get more information. > > have you looked at resize2fs? > > http://www.2robots.com/static/man/index.php/resize2fs > > > On 3/10/06, cbolton@rarr.org.uk <cbolton@rarr.org.uk> wrote: > >> Repling to my own mail here but its on subject. >> >> >> Just added a new drive to the machine, added it to the volume group, >> moved everything from /dev/hde1 to /dev/hda, removed hde1 from the VG >> and removed in physicaly from the machine. >> >> Great everything went fine, only the new drive is 60gigs so in moving >> its only used 40gigs. Not a problem I thought, I'll just extend the >> logical volume, so I did lvextend and extended it by 20gigs. >> >> This seemed to work as well.. >> >> >> PV /dev/sda2 VG VolGroup00 lvm2 [68.38 GB / 0 free] >> PV /dev/sdb VG VolGroup00 lvm2 [68.50 GB / 0 free] >> PV /dev/hdc2 VG VolGroup00 lvm2 [37.12 GB / 0 free] >> PV /dev/hdb1 VG VolGroup00 lvm2 [37.22 GB / 0 free] >> PV /dev/hdd1 VG VolGroup00 lvm2 [37.22 GB / 0 free] >> PV /dev/hda VG VolGroup00 lvm2 [57.25 GB / 0 free] >> Total: 6 [305.69 GB] / in use: 6 [305.69 GB] / in no VG: 0 [0 ] >> >> >> but df -h says... >> >> Filesystem Size Used Avail Use% Mounted on >> /dev/mapper/VolGroup00-LogVol00 >> 265G 248G 6.8G 98% / >> /dev/sda1 99M 73M 22M 78% /boot >> /dev/shm 252M 0 252M 0% /dev/shm >> >> >> I thought I'd need to extend the file system so i did ext2online >> /dev/VolGroup00/LogVol00 but its says... >> >> >> ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b ext2online: ext2_ioctl: >> No space left on device >> >> >> ext2online: unable to resize /dev/mapper/VolGroup00-LogVol00 >> >> >> >> Any ideas? I'm plain out. >> >> >> Cheers, >> Chris >> >> >> On Thu, January 19, 2006 7:55 am, Chris bolton wrote: >> >>> nevermind got it sussed, lvm is using 10^9 for a gigabyte while df is >>> using 1024^3 >>> >>> well it would appear that way anyway. >>>> Hi, >>>> >>>> >>>> >>>> just added a new PV to my VG but to me there seems to be an >>>> inconsistency between what lvm says is the disk space and what df >>>> says. >>>> >>>> >>>> pvscan PV /dev/sda2 VG VolGroup00 lvm2 [68.38 GB / 0 free] PV >>>> /dev/sdb VG VolGroup00 lvm2 [68.50 GB / 0 free] >>>> PV /dev/hdc2 VG VolGroup00 lvm2 [37.12 GB / 0 free] >>>> PV /dev/hdb1 VG VolGroup00 lvm2 [37.22 GB / 0 free] >>>> PV /dev/hdd1 VG VolGroup00 lvm2 [37.22 GB / 0 free] >>>> PV /dev/hde1 VG VolGroup00 lvm2 [37.25 GB / 0 free] >>>> Total: 6 [285.69 GB] / in use: 6 [285.69 GB] / in no VG: 0 [0 ] >>>> >>>> >>>> >>>> df -h /dev/mapper/VolGroup00-LogVol00 265G 227G 28G 90% / >>>> >>>> >>>> I tried resizing the filesystem but it just says this.. >>>> >>>> >>>> >>>> ext2online /dev/VolGroup00/LogVol00 ext2online v1.1.18 - >>>> 2001/03/18 for >>>> EXT2FS 0.5b >>>> ext2online: ext2_ioctl: No space left on device >>>> >>>> >>>> >>>> ext2online: unable to resize /dev/mapper/VolGroup00-LogVol00 >>>> >>>> >>>> >>>> Am I missing something obvious here? or have I ballsed it up along >>>> the way? >>>> >>>> Cheers, >>>> Chris. >>>> >>>> >>>> >>>> _______________________________________________ >>>> linux-lvm mailing list linux-lvm@redhat.com >>>> https://www.redhat.com/mailman/listinfo/linux-lvm >>>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ >>> >>> _______________________________________________ >>> linux-lvm mailing list linux-lvm@redhat.com >>> https://www.redhat.com/mailman/listinfo/linux-lvm >>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ >>> >> >> >> _______________________________________________ >> linux-lvm mailing list linux-lvm@redhat.com >> https://www.redhat.com/mailman/listinfo/linux-lvm >> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ >> > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [linux-lvm] Disk space reporting inconsistencies - lvm half baked 2006-01-18 11:31 [linux-lvm] Disk space reporting inconsistencies Chris bolton 2006-01-19 7:55 ` Chris bolton @ 2006-01-19 19:50 ` Jed Donnelley 1 sibling, 0 replies; 6+ messages in thread From: Jed Donnelley @ 2006-01-19 19:50 UTC (permalink / raw) To: LVM general discussion and development; +Cc: rhn-users At 03:31 AM 1/18/2006, Chris bolton wrote: >Hi, > >just added a new PV to my VG but to me there seems to be an >inconsistency between what lvm says is the disk space and what df says. > >pvscan > PV /dev/sda2 VG VolGroup00 lvm2 [68.38 GB / 0 free] > PV /dev/sdb VG VolGroup00 lvm2 [68.50 GB / 0 free] > PV /dev/hdc2 VG VolGroup00 lvm2 [37.12 GB / 0 free] > PV /dev/hdb1 VG VolGroup00 lvm2 [37.22 GB / 0 free] > PV /dev/hdd1 VG VolGroup00 lvm2 [37.22 GB / 0 free] > PV /dev/hde1 VG VolGroup00 lvm2 [37.25 GB / 0 free] > Total: 6 [285.69 GB] / in use: 6 [285.69 GB] / in no VG: 0 [0 ] > >df -h >/dev/mapper/VolGroup00-LogVol00 265G 227G 28G 90% / > >I tried resizing the filesystem but it just says this.. > >ext2online /dev/VolGroup00/LogVol00 > ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b > ext2online: ext2_ioctl: No space left on device > >ext2online: unable to resize /dev/mapper/VolGroup00-LogVol00 > >Am I missing something obvious here? or have I ballsed it up along the way? > >Cheers, >Chris. Chris, I believe the above is an example similar to the second of the two situations that I ran into when I came to the conclusion that LVM was "half baked" and not (yet?) suitable for production use on server systems (below). I repeat my message below for your information and in case there might have been any changes that might allow recovery from the problems I ran into. I will be interested to see if you find any way to recover from the problem you ran into: ________________________________________________________ Date: Wed, 12 Oct 2005 18:30:18 -0700 To: linux-lvm@redhat.com, rhn-users@redhat.com From: Jed Donnelley <jed@nersc.gov> Subject: Linux LVM - half baked? Redhat LVM users, Since I mentioned a minor bug in Redhat/LVM (9/28 LVM(2) bug in RH ES 4.1 /etc/rc.d/sysinit.rc, RAID-1+0) I've done quite a number of additional installs using LVM. I've now had my second system that got into an essentially unrecoverable state. That's enough for me and LVM. I very much like the facilities that LVM provides, but if I'm going to lose production file systems with it - well, I will have to wait. Below are descriptions of the two problems I've run into. I have run linux rescue from a CD for both systems. The difficulty of course is that since the problem seems to be in the LVM layer, there are no file systems to work on (e.g. with fsck). Perhaps there are some tools that I'm not yet familiar with to recover logical volumes in some way? These are test/development systems, but if anybody has any thoughts on how to recover their file systems (e.g. to get more confidence in LVM) I'd be quite interested to hear them - just for the experience and perhaps to regain some confidence in LVM. Thanks! <I've since recycled the disks from these systems and the problems might now be difficult to recreate, though if there are suggestions on how to recover from them that seem workable I'd be willing to give it a try> In one system after doing nothing more than an up2date on a x86_64 system and rebooting I see: ... 4 logical volume(s) in volume group "VolGroup00" now active ERROR: failed in exec of defaults ERROR: failed in exec of ext3 mount: error 2 mounting none switchroot: mount failed: 23 ERROR: ext3 exited abnormally! (pid 284) ... <three more similar to the above> kernel panic - not syncing: Attempted to kill init! When I look at the above disks (this is a 6 disk system, one RAID-1 pair for /boot - not LVM - and a 4 disk RAID-10 system for /data) the partitions all look fine. I'm not sure what else to look for. ______________________ In the other system (an x86 system) I had a disk failure in a software RAID-1 file system for the system file system (/boot /). I replaced the disk and resynced it apparently successfully. However, after a short time that replacement disk apparently failed (wouldn't spin up on boot). I removed the second disk and restarted the system. Here is how that went: ... Your System appears to have shut down uncleanly fsck.ext3 -a /dev/VolGroup00/LogVol02 contains a file system with errors, check forced /dev/VolGroup00/LogVol02 Inodes that were part of a corrupted orphan linked list found. /dev/VolGroup00/LogVol02 UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY (i.e. without -a or -p options) [FAILED] *** An error occurred during the file system check. *** Dropping you to a shell; The system will reboot when you leave the shell. Give root password for maintenance (or type Control-D to continue) --------------------- All stuff very familiar to those who've worked on corrupted file systems. However, in this case if I type Control-D or enter the root password the system goes through a sequence like: unmounting ... automatic reboot and reboots. This starts the problem all over again. As with the first system above if I use a rescue disk there is no file system to run fsck on. At this point, despite the value I see in LVM, I plan to back off on production deployment. I'd be interested to hear the experiences of others. _____________________________________________________________________ I did back off LVM. We don't use LVM on any of our many (50+, though not so many Linux) production server systems. We use RAID on all those systems. I still don't trust LVM for production use. I'd be quite interested to hear any defense of LVM for application to production servers. In my current opinion anybody using LVM for production servers over RAID (at least for the /boot and / partitions) is walking on shaky ground. I'd be quite interested to be shown to be wrong in that opinion. --Jed http://www.webstart.com/jed/ ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-03-10 21:45 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-01-18 11:31 [linux-lvm] Disk space reporting inconsistencies Chris bolton
2006-01-19 7:55 ` Chris bolton
2006-01-19 20:00 ` Matt P
2006-03-10 20:26 ` cbolton
[not found] ` <6c3e3c670603101323s6ccb11f2kfeea93718cfd162a@mail.gmail.com>
2006-03-10 21:45 ` cbolton
2006-01-19 19:50 ` [linux-lvm] Disk space reporting inconsistencies - lvm half baked Jed Donnelley
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.