All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ragnar Kjørstad" <lvm@ragnark.vestdata.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Procedure to pvmove PE's on bad media?
Date: Wed Dec 26 11:54:01 2001	[thread overview]
Message-ID: <20011226185659.A22039@vestdata.no> (raw)
In-Reply-To: <1009367389020268@caramail.com>; from o.di-sciullo@caramail.com on Wed, Dec 26, 2001 at 12:49:49PM +0000

On Wed, Dec 26, 2001 at 12:49:49PM +0000, Octavio Di Sciullo wrote:
> 	I've tried to apply to pvmove (from lvm 0.9.1b7) the patch
> issued on this thread :
> http://lists.sistina.com/pipermail/linux-lvm/2001-September/008767.html
> , but unfortunately, it doesnt work :/. With this "forced"
> pvmove, i get an endless read loop :
> 
> "read:-1 to_read:512
> read:-1 to_read:512
> read:-1 to_read:512
> read:-1 to_read:512"
> ..... (i let it run for about 4h and the output never
> changed, nor as the drive never ceased to produce scary
> noises)
> 
> 	Now i dont really know if this the proper behavior of the
> patched pvmove in case it REALLY doesnt manage to read the
> data (i thought this was what the patch was for), or if i
> have a compatibility problem with my 0.9 lvm installed and
> the 0.9.1b7 patched pvmove.... I tried (a bit) to upgrade to
> 0.9.1b7 but i get dependency conflicts.


Did you run it as root?
(isn't -1==EPERM, meaning you have no permission?)

The proper output (I think) should be:
read:-5 to_read:512
and with 4MB extent-size you should have 8192 such messages pr bad
extent (max).



-- 
Ragnar Kjørstad
Big Storage

      reply	other threads:[~2001-12-26 11:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-26  5:47 [linux-lvm] Procedure to pvmove PE's on bad media? Octavio Di Sciullo
2001-12-26 11:54 ` Ragnar Kjørstad [this message]

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=20011226185659.A22039@vestdata.no \
    --to=lvm@ragnark.vestdata.no \
    --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.