From: Peter Daum <gator_ml@yahoo.de>
To: linux-lvm@redhat.com
Subject: [linux-lvm] pvresize after extending RAID array
Date: Mon, 18 Jun 2007 23:16:03 +0200 [thread overview]
Message-ID: <f56smj$275$1@sea.gmane.org> (raw)
I have a physical volume consisting of 1 hardware raid array (/dev/sdb).
Now I added some disks to the raid array, extending its size from 4.5
to ~6 TB. The kernel (Linux 2.6.16.51) now correctly reports the new
device size:
# cat /sys/block/sdb/size
12695042048
From reading the manuals I got the impression, that all that is needed
to be able to use the additional space is "pvresize /dev/sdb".
Unfortunately, it looks like pvresize insists on the old device size:
# pvresize -v -d /dev/sdb
File descriptor 3 left open
Using physical volume(s) on command line
Archiving volume group "raid6_12" metadata (seqno 19).
No change to size of physical volume /dev/sdb.
Resizing volume "/dev/sdb" to 9765416576 sectors.
Updating physical volume "/dev/sdb"
Creating volume group backup "/etc/lvm/backup/raid6_12" (seqno 20).
Physical volume "/dev/sdb" changed
1 physical volume(s) resized / 0 physical volume(s) not resized
Did I miss something? Is there anything to worry about or should I just
go ahead and set the new device size manually:
# pvresize -v -d --setphysicalvolumesize 6347521024k /dev/sdb
File descriptor 3 left open
Using physical volume(s) on command line
Archiving volume group "raid6_12" metadata (seqno 22).
WARNING: /dev/sdb: Overriding real size. You could lose data.
/dev/sdb: Pretending size is 12695042048 not 12695035904 sectors.
No change to size of physical volume /dev/sdb.
Resizing volume "/dev/sdb" to 12695041664 sectors.
Updating physical volume "/dev/sdb"
Creating volume group backup "/etc/lvm/backup/raid6_12" (seqno 23).
Physical volume "/dev/sdb" changed
1 physical volume(s) resized / 0 physical volume(s) not resized
In this case, pvresize comes up with yet another size for the device
(12695035904 sectors) - is this the actual size of the device minus
the space needed for lvm's metadata? Should I manually set to this?
Any comments?
Regards,
Peter Daum
next reply other threads:[~2007-06-18 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 21:16 Peter Daum [this message]
2007-06-19 9:49 ` [linux-lvm] Re: pvresize after extending RAID array Peter Daum
2007-06-19 13:16 ` [linux-lvm] " Alasdair G Kergon
2007-06-19 17:46 ` [linux-lvm] " Peter Daum
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='f56smj$275$1@sea.gmane.org' \
--to=gator_ml@yahoo.de \
--cc=linux-lvm@redhat.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).