From: Sebastian <sebastian@alice-it.net>
To: linux-lvm@redhat.com
Subject: [linux-lvm] EMERGENCY: killing pvmove
Date: Mon, 19 Sep 2005 13:56:19 +0200 [thread overview]
Message-ID: <432EA763.9020501@alice-it.net> (raw)
Hello List,
I'm in a emergency situation so I haven't had the time to go through all
the threads. I have had a strange problem and through my interaction it
is now more severe as I think, so I have to get advice quickly.
I have several RAID subsets as physical volumes, each 1,4 TB in size,
combine to a volume group of 8,6 TB. This VG is splitted in 6 LV's. One
of the LV I did resize last week, and therefore added one PV of again
1,4TB to the VG, and resized one LV.
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".
As this wouldn't be enough, I restarted the computer putting the new
RAID subsystem on a different scsi controller, as I thought this could
be the problem. Then the pvmove command worked!
But as I realised shortly, I just moved the wrong one, as /dev/sdg is
now another subsystem (the damaged one is now /dev/sde).
Now I have the Problem that my sane part of the data is slowly moving to
the insane disk, which I can't stop! Even ctrl-c does not help...
How to stop it? Is a SIGTERM or SIGKILL allowed? Pleas help, I'm running
out of time!
Thanks a lot!!!!
yours
Sebastian
next reply other threads:[~2005-09-19 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 11:56 Sebastian [this message]
2005-09-19 12:05 ` [linux-lvm] EMERGENCY: killing pvmove Alasdair G Kergon
2005-09-19 12:15 ` 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=432EA763.9020501@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 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).