From: "Andreé Åström" <andree.astrom@home.se>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Trouble with pvmove
Date: Mon May 5 10:29:02 2003 [thread overview]
Message-ID: <001801c3131b$2acd7ae0$0100a8c0@andre6xtbp6uza> (raw)
In-Reply-To: 20030503114458.GB541@guldukat
----- Original Message -----
From: "Nils Juergens" <nils@muon.de>
To: <linux-lvm@sistina.com>
Sent: Saturday, May 03, 2003 1:44 PM
Subject: Re: [linux-lvm] Trouble with pvmove
> On Thu, 01.05.03, Andre� �str�m <andree.astrom@home.se> wrote:
>
> > In one of my volume groups a disk have gone bad.
> > I extended the volumegroup with another disk to be able to pvmove it.
>
> Is the disk already producing read errors or are you using a SMART monitor
> that tells you it is bad?
Both, uncorrectable errors in dmesg, and smartctl reports it as failing.
>
> >
> > pvmove -i -v /dev/hdh
> >
> > It went fine until,
> > pvmove -- /dev/hdh [PE 259 [archive [LE 259]] -> /dev/hdj [PE 259]
> > [260/1831]
> >
> > The machine got total dead. The whole volumegroup consists of 1.1TB so i
> > couldn't backup it all up beforehand.
>
> Which version of LVM are you using? IIRC there has been trouble with
pvmove
> and lockups before, so try to upgrade to newest version.
We were using 1.0.4, so updated to 1.0.7 today. No luck tough. Computer
locks up completly at
certain PE's.
Any clues how i can recover any data from it ? As it complains now, of
missing inodes when i mount it and try to accesss it.
So i cant really do anything. I guess those was moved from the broken
harddisk to the new one, but never got updated
because the computer locked up.
Regards,
Adain
next prev parent reply other threads:[~2003-05-05 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 14:07 [linux-lvm] Trouble with pvmove Andreé Åström
2003-05-03 5:42 ` Nils Juergens
2003-05-05 10:29 ` Andreé Åström [this message]
2003-05-05 10:51 ` Nils Juergens
2003-05-05 11:07 ` Anders Widman
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='001801c3131b$2acd7ae0$0100a8c0@andre6xtbp6uza' \
--to=andree.astrom@home.se \
--cc=linux-lvm@sistina.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