From: "Lars Michael Jogbäck" <lm@swip.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Problems(?) with pvresize
Date: Mon, 02 Jul 2007 09:34:58 +0200 [thread overview]
Message-ID: <4688AAA2.6070807@swip.net> (raw)
In-Reply-To: <4688A90B.8080507@vdberg.org>
Richard van den Berg wrote:
> Lars Michael Jogb�ck wrote:
>
>> I've got a hardware-raid5 that I've extended (/dev/sdk), and after
>> extending it, I get the kernel to recognize the new size.
>> But pvresize is still using the old size. I'm pretty convinced that a
>> reboot will solve this issue for me, but isn't there a way of solving
>> this without rebooting?
>>
>
> I used "partprobe" that comes with parted, and it worked well for me
>
Thanks, but I've tried that and it didn't work either. pvresize still
thinks it's the old size.
Best Regards,
/LM
prev parent reply other threads:[~2007-07-02 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 7:12 [linux-lvm] Problems(?) with pvresize Lars Michael Jogbäck
2007-07-02 7:28 ` Richard van den Berg
2007-07-02 7:34 ` Lars Michael Jogbäck [this message]
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=4688AAA2.6070807@swip.net \
--to=lm@swip.net \
--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).