From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] SCSI/LVM problems after power outage
Date: Wed, 9 May 2001 21:26:29 +0000 [thread overview]
Message-ID: <20010509212629.A8512@sistina.com> (raw)
In-Reply-To: <20010509201416.A20867@mercury.mercury.multiweb.nl>; from dave@xs4all.nl on Wed, May 09, 2001 at 08:14:16PM +0200
On Wed, May 09, 2001 at 08:14:16PM +0200, Dave Wapstra wrote:
> On 09 May, 2001 at 09:35:10 +0000, Heinz J. Mauelshagen <Mauelshagen@sistina.com> wrote:
> >
> > On Tue, May 08, 2001 at 02:05:16PM -0700, Day, Evan wrote:
> > > It looks like device 2 is having issues:
> > >
> > > SCSI disk error : host 2 channel 0 id 2 lun 0 return code = 18000002
> > >
>
> Ok. Sounds reasonable ;) It seems /dev/sdc is giving troubles.
>
> > In case the PEs on the flaky device are still readable:
> > extending your VG and using pvmove is the way to go.
> >
> > Steps needed (crossing your fingers that the flaky drive can still stand this):
> >
> > - install or use an additional drive of at least the size of the flaky one
> > - pvcreate that drive
> > - vgextend the VG by it
> > - pvmove /dev/FlakyDrive
> > - wait until pvmove is done
> > - vgreduce VG /dev/FlakyDrive
>
> I'm trying to backup the data that is still available (backup was a
> thing that was still in progress... :) )
>
> pvmove is not really happy with the current situation.
I don't understand you here.
Did you try the above steps and something failed?
>
> Can I just do "vgreduce ftp /dev/sdc" after I finished rescueing most of the data?
>
Sure.
In case you've got a backup, you could remove or reduce LVs so that *no*
PEs are allocated on /dev/sdc.
You can check with "pvdisplay -v /dev/sdc" which LV(s) have PEs allocated
on that PV and run lvremove/lvreduce in order to free that PV.
Once pvdisplay tells you that no PEs are allocated (Allocated PE 0) you
can run "vgreduce VGName /dev/sdc".
> > You should have your LVs offline in case you have an older version than
> > LVM 0.9.1 Beta 7, because they had a pvmove related bug which could cause
> > oopses when you moved PEs in use.
> >
> > BTW: you need to configure MD (RAID 1 or 5) or use hardware raid subsystems
> > to avoid suffering from such flaky disk problems.
>
> I haven't looked at RAID yet. The striping option of LVM is not really
> an option, since I cannot add any disks to the volume.
That's true today.
There's a tiny item on the TODO list to enhance this ;-)
>
> -Dave
>
> --
> Dave Wapstra
> dave@xs4all.nl
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-05-09 21:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 21:05 [linux-lvm] SCSI/LVM problems after power outage Day, Evan
2001-05-09 9:35 ` Heinz J. Mauelshagen
2001-05-09 18:14 ` Dave Wapstra
2001-05-09 21:26 ` Heinz J. Mauelshagen [this message]
2001-05-10 20:30 ` Dave Wapstra
2001-05-11 12:54 ` Heinz J. Mauelshagen
2001-05-11 8:03 ` Steven Lembark
2001-05-11 8:37 ` Adrian Phillips
2001-05-11 14:05 ` Terje Kvernes
2001-05-11 14:25 ` Terje Kvernes
2001-05-11 14:48 ` Adrian Phillips
2001-05-11 15:56 ` Luca Berra
2001-05-11 8:00 ` Steven Lembark
-- strict thread matches above, loose matches on Subject: below --
2001-05-08 16:33 Dave Wapstra
2001-05-08 16:59 ` Hugo Lombard
2001-05-08 18:16 ` Bart-Jan Vrielink
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=20010509212629.A8512@sistina.com \
--to=mauelshagen@sistina.com \
--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