From: Sebastian <sebastian@alice-it.net>
To: linux-lvm@redhat.com
Subject: [Fwd: [linux-lvm] EMERGENCY: killing pvmove]
Date: Mon, 19 Sep 2005 14:44:31 +0200 [thread overview]
Message-ID: <432EB2AF.9050500@alice-it.net> (raw)
And, more important, what is worse: to put the sane data on an insane pv
using pvmove, or
to kill the pvmove command leaving a few unreadable sectors?
I'm prefering version #2 at the moment, I will apply it shortly before
the new pv will be used.
-------- Original Message --------
After that -- everything went ok, even resizing the ext3 partition -- I
got Input/Output errors while writing to the newly resized partition
(writing to the extended part of the partition). As realising this, I
put all the data off this partition, deleted it and was then trying to
remove the Raid subsystem with pvmove. While doing "pvmove /dev/sdg" I
just got an "segmentation fault".
How to stop it? Is a SIGTERM or SIGKILL allowed? Pleas help, I'm running
out of time!
next reply other threads:[~2005-09-19 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 12:44 Sebastian [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-19 12:41 [Fwd: [linux-lvm] EMERGENCY: killing pvmove] Sebastian
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=432EB2AF.9050500@alice-it.net \
--to=sebastian@alice-it.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 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.