All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Removing PV with disk errors from VG
Date: Tue Mar 12 07:35:03 2002	[thread overview]
Message-ID: <20020312143404.B18690@sistina.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0203111559500.10883-100000@pzat.meep.org>; from oolon@ankh.org on Mon, Mar 11, 2002 at 04:22:56PM +0000

On Mon, Mar 11, 2002 at 04:22:56PM +0000, James Hawtin wrote:
> 
> 
> On Mon, 11 Mar 2002, Heinz J . Mauelshagen wrote:
> 
> >
> > well that's a bug in 1.0.3 which will be fixed in 1.0.4.
> > If you wnat to try it at your own risk, check out LVM1 CVS and
> > try "pvmove -i" again.
> >
> > 1.0.4 will hopefully be released this week :)
> >
> > Regards,
> > Heinz    -- The LVM Guy --
> >
> >
> 
> Hmmm, I had a problem with pv move over the weekend as well.. I was
> replacing a hard disk for more space. and when I tried pvmove it worked
> for 2 small partitions, but for a larger data area it failed to move
> (because of a read error). Interestingly I had not got any error messages
> in dmsg about bad seeks.
> 
> Not knowing about pvmove -i I feel back to my old system for using tar in
> a pipe to move data, not quick not pretty but it works ;-)
> 
> So fortunately it looks like it was a virgin sector.
> 
> My question is.... This pvmove bug does it make "read error" problems in
> which  case the disk might be ok, or does it just not handle read errors
> gracefully?

It displays "read errors" because the bug lead to llseek errors which
where handed backup to an internal read function call.

Regards,
Heinz    -- The LVM Guy --

> 
> Yes I was using 1.0.3.
> 
> The Disk was an 46G IBM (From the ICL (newer glass platter C**p)) so I am
> willing to beleive it was a disk problem (I have space on the shelf so
> it can sit with its friends) it which case I will not use the disk agian.
> 
> I already lost 2 IBM disks from the older range and have another one
> which when I have the money I will be swapping out... Agh! I hate IBM. Yup
> i know I can RMA it, but whats the point if the new one might have
> problems too, my data is worth more than that.
> 
> Does make for fun at computer fairs though,
> 
> Me:   I need a new harddisk...
> Them: IBM make the best ones.
> (The specs are great and are dead fast)
> Me:   IBM disks live fast and die fast, what do you have in a non IBM
>       disk.
> 
> PS anyone else know of other brands I should avoid buying?
> 
> James
> 
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2002-03-12  7:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-08  9:42 [linux-lvm] Removing PV with disk errors from VG kalle
2002-03-08 10:54 ` Denie Andriessen
2002-03-11  9:35 ` Heinz J . Mauelshagen
2002-03-11 10:26   ` James Hawtin
2002-03-12  7:35     ` Heinz J . Mauelshagen [this message]
2002-03-11 11:03   ` kalle
2002-03-12 17:15   ` Chris Harwell
2002-03-13  5:06     ` Heinz J . Mauelshagen
2002-03-13 11:19       ` Chris Harwell
2002-03-13 13:37         ` Chris Harwell

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=20020312143404.B18690@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 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.