Linux LVM users
 help / color / mirror / Atom feed
From: FEJF <fejf@gmx.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] pv_move_pe() error again :/
Date: Mon, 10 Sep 2001 01:51:37 +0200	[thread overview]
Message-ID: <E15gELn-0004OG-00@hermes.sistina.com> (raw)
In-Reply-To: <20010910001643.A19424@vestdata.no>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ragnar Kj�rstad, on Montag, 10. September 2001 00:16 wrote:
> OK, this is the patch.

thx, for your help, but meanwhile i got one from Holger Grothe.
sorry, but i haven't had time to post it earlier. i do it now because it has 
some advantages...

tools/lib/pv_move.c:

replace:
            fprintf ( stderr, "%s -- ERROR reading input "
                     "physical volume \"%s\" (still %d bytes to read)\n       
                      cmd, vg->pv[src_pv_index]->pv_name, size);
            pe_unlock ( vg->vg_name);
            ret = -LVM_EPV_MOVE_PE_READ_IN;
            goto pv_move_pe_end;
with:
           fprintf ( stderr, "read: %ld, to_read %ld\n", red, to_read);
           memset(buffer,170,to_read);
           red=to_read;

with 170 u can chosse with which chars the bad block should be replaced with. 
(you can search filez for them later if u want - and have enough time ;)

tools/pvmove.c:

replace:
	int buffer_size = 64*1024;
with:   
	int buffer_size = 512;

this is an advantage to your patch, because pvmove then copys only 512 
byte-blocks and if there's only one block damaged u don't loose 64kb data. 
this has one disadvantage: it's SLOW... and slower than that ;)
so change the source and do a static compiling:
./configure --enable-static_link ; make
u can then use the normal pvmove to move your partitions and if there is an 
error u can use the (patched) tools/pvmove program for bad-block moving.
worked find for me and i saw that only one 512 byte block was damaged.
fejf

ps: i used lvm 0.9.1b7 but it should look and work similar with other 
versions but i think a diff is not the best for it ;)
- -- 
Backups are usefull. Most often when you don't have one ;)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7nACM7Xtp66ctWuIRAgg7AKCBCVB/SPRCLjP9i5oHuf6vgx1u9wCeOmzP
ky+sZgdG6iVcPrN9Ufgl5L8=
=Mfig
-----END PGP SIGNATURE-----

  reply	other threads:[~2001-09-09 23:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-06 15:28 [linux-lvm] pv_move_pe() error again :/ FEJF
2001-09-06 20:05 ` Ragnar Kjørstad
2001-09-06 23:41   ` FEJF
2001-09-07  9:43     ` Ragnar Kjørstad
2001-09-07 11:36       ` FEJF
2001-09-09 22:16         ` Ragnar Kjørstad
2001-09-09 23:51           ` FEJF [this message]
2001-09-10  8:39             ` Ragnar Kjørstad
2001-09-10 11:27               ` Heinz J . Mauelshagen
2001-09-10 11:45                 ` FEJF
2001-09-10 13:43                   ` Heinz J . Mauelshagen
2001-09-10 13:49                     ` FEJF
2001-09-10 15:38                 ` Ragnar Kjørstad
2001-09-10 16:13                   ` FEJF
2001-09-11 14:31                   ` Heinz J . Mauelshagen
2001-09-11 17:26                     ` Ragnar Kjørstad
2001-09-10 11:53               ` FEJF
2001-09-07 10:46     ` Heinz J . Mauelshagen
2001-09-07 11:45       ` FEJF

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=E15gELn-0004OG-00@hermes.sistina.com \
    --to=fejf@gmx.de \
    --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