linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Rochelle Lakey <RLakey@Connex.com>
To: 'Andy Cowling' <andy@redeye.com>, linux-lvm@msede.com
Cc: Dan Garcia <dan@redeye.com>
Subject: RE: [linux-lvm] lvdisplay disagrees with df for resized LV
Date: Wed, 11 Oct 2000 08:38:50 -0700	[thread overview]
Message-ID: <B14BF8753E65D211ABCA00104B301EF5015BAF4E@cairn-gorm.cragtech.com> (raw)

Hello Andy,

My guess would be that you have to resize the filesystem as well.
Hope that helps.

Rochelle Lakey

-----Original Message-----
From: Andy Cowling [mailto:andy@redeye.com]
Sent: Wednesday, October 11, 2000 5:26 AM
To: linux-lvm@msede.com
Cc: Dan Garcia
Subject: [linux-lvm] lvdisplay disagrees with df for resized LV


I'm just starting out using LVM under SuSE 7.0. I created a logical
volume which was initially 30Gb but I then resized it to 90Gb (using
lvresize) spanning 3 physical volumes each of 30Gb.

Now, lvdisplay/vgdisplay shows the LV/VG size as 90Gb, but df still
lists the file system as 30Gb.

How can I get df to recognise the addtional space ?

Thanks in advance
-- 
Andy Cowling
Red Eye International
http://www.redeye.com/

root@lynx:/opt/oracle > df -h /lv01
Filesystem            Size  Used Avail Use% Mounted on
/dev/vg01/lv01         30G   17G   13G  58% /lv01

root@lynx:/opt/oracle > lvdisplay  /dev/vg01/lv01
--- Logical volume ---
LV Name               /dev/vg01/lv01
VG Name               vg01
LV Write Access       read/write
LV Status             available
LV #                  1
# open                1
LV Size               90 GB
Current LE            23040
Allocated LE          23040
Allocation            next free
Read ahead sectors    128
Block device          58:0

root@lynx:/opt/oracle > vgdisplay  vg01          
--- Volume group ---
VG Name               vg01
VG Access             read/write
VG Status             available/resizable
VG #                  0
MAX LV                256
Cur LV                1
Open LV               1
MAX LV Size           255.99 GB
Max PV                256
Cur PV                3
Act PV                3
VG Size               90.01 GB
PE Size               4 MB
Total PE              23043
Alloc PE / Size       23040 / 90 GB
Free  PE / Size       3 / 12 MB

root@lynx:/opt/oracle > pvdisplay /dev/sdc5
--- Physical volume ---
PV Name               /dev/sdc5
VG Name               vg01
PV Size               30.01 GB / NOT usable 1.85 MB [LVM: 260 KB]
PV#                   3
PV Status             available
Allocatable           yes
Cur LV                1
PE Size (KByte)       4096
Total PE              7681
Free PE               3
Allocated PE          7678


root@lynx:/opt/oracle > pvdisplay /dev/sdd5
--- Physical volume ---
PV Name               /dev/sdd5
VG Name               vg01
PV Size               30.01 GB / NOT usable 1.85 MB [LVM: 260 KB]
PV#                   2
PV Status             available
Allocatable           yes (but full)
Cur LV                1
PE Size (KByte)       4096
Total PE              7681
Free PE               0
Allocated PE          7681


root@lynx:/opt/oracle > pvdisplay /dev/sde5
--- Physical volume ---
PV Name               /dev/sde5
VG Name               vg01
PV Size               30.01 GB / NOT usable 1.85 MB [LVM: 260 KB]
PV#                   1
PV Status             available
Allocatable           yes (but full)
Cur LV                1
PE Size (KByte)       4096
Total PE              7681
Free PE               0
Allocated PE          7681

             reply	other threads:[~2000-10-11 15:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-11 15:38 Rochelle Lakey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-11-27 16:17 [linux-lvm] lvdisplay disagrees with df for resized LV Holger Grothe
2000-10-11 12:25 Andy Cowling
2000-10-11 13:45 ` Eric M. Hopper
2000-10-11 16:28   ` Andy Cowling
2000-10-11 17:20     ` Eric M. Hopper
2000-10-11 17:57     ` Charles Duffy
2000-10-11 18:26     ` Brian Poole
2000-10-12 16:41   ` Andreas Dilger
2000-10-11 14:12 ` Les Hazelton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B14BF8753E65D211ABCA00104B301EF5015BAF4E@cairn-gorm.cragtech.com \
    --to=rlakey@connex.com \
    --cc=andy@redeye.com \
    --cc=dan@redeye.com \
    --cc=linux-lvm@msede.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).