From: "Diaz Rodriguez, Eduardo" <ediaz@pk25.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] pvmove hangs
Date: Thu, 28 Apr 2005 13:13:09 +0200 [thread overview]
Message-ID: <20050428110649.M93697@pk25.com> (raw)
In-Reply-To: <4270B992.50805@nextra.ro>
The / partition is diferent.
I am sure that your made the same but your import your vgs in other machine
and you moveit and you don't have problems.
the / patition has the modules, and many info that the systen can't move
becasue are in use (I suppose)....
Where you have the partions boot files?
lrwxrwxrwx 1 root root 28 Apr 13 21:50 vmlinuz ->
boot/vmlinuz-2.4.30.20050413
lrwxrwxrwx 1 root root 26 Apr 12 20:20 vmlinuz.old ->
boot/vmlinuz-2.4.30.050412
/dev/hda2 5763648 4796612 674252 88% /
I have kernel files in / :-D, yes I isn't the best way ....
:-|, I think that can be a good question for the developers :-)....
On Thu, 28 Apr 2005 13:23:14 +0300, Gergely Imre wrote
> the main question is, why it keeps hanging when i want to move "/" ?
> it doesn't even begin to move the PEs. i tried to move some other
> live partitions while writing on them, and it worked.
>
> Diaz Rodriguez, Eduardo wrote:
> > too much dificult for me, only have one idea, update lvm to last version and
> > check changelog for some updates about pvmove.
> >
> > If you solve the problem, please sumarice.
> >
> > Good Luck!
> >
> > On Wed, 27 Apr 2005 16:04:20 +0300, Gergely Imre wrote
> >
> >>let me 'restart' this thread. i ran into another problem. or it's
> >>the same?
>
> _______________________________________________
> 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/
=======================================================================================
En tus apuros y afanes, acude a los refranes.
=======================================================================================
next prev parent reply other threads:[~2005-04-28 11:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 13:04 [linux-lvm] pvmove hangs Gergely Imre
2005-04-28 9:46 ` Diaz Rodriguez, Eduardo
2005-04-28 10:23 ` Gergely Imre
2005-04-28 11:13 ` Diaz Rodriguez, Eduardo [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-17 19:26 Allen, Jack
2010-08-17 22:12 ` Thomas Hager
2010-08-17 23:09 ` Allen, Jack
2005-04-26 9:19 Gergely Imre
2005-04-26 13:30 ` Diaz Rodriguez, Eduardo
2005-04-27 5:46 ` Gergely Imre
2003-08-16 5:21 Jan Niehusmann
2003-08-16 10:48 ` Jan Niehusmann
2003-08-16 13:57 ` Alasdair G Kergon
2003-08-17 11:11 ` Jan Niehusmann
2003-08-17 11:34 ` Alasdair G Kergon
2003-08-17 11:41 ` Jan Niehusmann
2003-08-17 12:00 ` Alasdair G Kergon
[not found] ` <20030817114638.GA1839@gondor.com>
2003-08-17 12:42 ` Alasdair G Kergon
2003-08-17 13:27 ` Jan Niehusmann
2003-08-17 13:50 ` Alasdair G Kergon
2003-08-17 13:55 ` Alasdair G Kergon
2003-08-18 12:58 ` Alasdair G Kergon
2003-08-18 13:21 ` Jan Niehusmann
2003-08-18 17:55 ` Jan Niehusmann
2003-08-19 17:52 ` Jan Niehusmann
2003-08-17 18:15 ` Jan Niehusmann
2003-08-18 6:46 ` Alasdair G Kergon
2003-08-18 7:07 ` Jan Niehusmann
2003-08-18 9:13 ` Alasdair G Kergon
2003-08-18 9:30 ` Jan Niehusmann
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=20050428110649.M93697@pk25.com \
--to=ediaz@pk25.com \
--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