From: Per Mellander <per.m@mmtab.se>
To: xfs@oss.sgi.com
Subject: xfs_growfs after lvextend don't increase mounted size.
Date: Wed, 01 Nov 2006 23:36:59 +0100 [thread overview]
Message-ID: <4549218B.2020807@mmtab.se> (raw)
Hi!
I've got a 6.5TB xfs filesystem on a LVM2 volume. I wanted to increase
the size of the fs so I added another ~10TB to the volume. Every step
taken was successfull, (ie no errors) but the filesystem size remained
unchanged even after the xfs_growfs.
What I did was the following:
I extended the lvm using pvcreate, vgextend and finally lvextend. pvscan
gives:
PV /dev/sda1 VG vg01 lvm2 [1.59 TB / 0 free]
PV /dev/sdb1 VG vg01 lvm2 [1.59 TB / 0 free]
PV /dev/sdc1 VG vg01 lvm2 [1.59 TB / 0 free]
PV /dev/sdd1 VG vg01 lvm2 [1.59 TB / 0 free]
PV /dev/sde1 VG vg01 lvm2 [2.00 TB / 0 free]
PV /dev/sdf1 VG vg01 lvm2 [2.00 TB / 0 free]
PV /dev/sdg1 VG vg01 lvm2 [2.00 TB / 0 free]
PV /dev/sdh1 VG vg01 lvm2 [2.00 TB / 0 free]
PV /dev/sdi1 VG vg01 lvm2 [1.55 TB / 0 free]
Total: 9 [15.91 TB] / in use: 9 [15.91 TB] / in no VG: 0 [0 ]
and lvdisplay:
--- Logical volume ---
LV Name /dev/vg01/lv01
VG Name vg01
LV UUID rDSEQ3-DdhV-oLci-nNYT-dMdX-cppA-7v1r3e
LV Write Access read/write
LV Status available
# open 1
LV Size 15.91 TB
Current LE 4169996
Segments 9
Allocation inherit
Read ahead sectors 0
Block device 253:0
After xfs_growfs /vol1 ( mounted fs ) df -h gives:
/dev/mapper/vg01-lv01
6.4T 6.4T 36G 100% /vol1
The fs remains in previous size!!
# cat /sys/block/dm-0/size
34160607232
which is equal to 15.91 TB
Have I missed something when I extended the volume / growed the xfs fs?
The system running xfs is a Fedora Core 4, 2.6.15-1.1831_FC4smp,
lvm2-2.01.08-2.1, xfsprogs-2.6.13-4
Per
_________________________________
This email has been ClamScanned !
www.clamav.net
next reply other threads:[~2006-11-01 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 22:36 Per Mellander [this message]
2006-11-01 23:59 ` xfs_growfs after lvextend don't increase mounted size Shailendra Tripathi
2006-11-02 3:42 ` David Chinner
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=4549218B.2020807@mmtab.se \
--to=per.m@mmtab.se \
--cc=xfs@oss.sgi.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 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.