On Fri, Sep 07, 2001 at 01:41:22AM +0200, FEJF wrote: > Ragnar Kjørstad, on Donnerstag, 6. September 2001 22:05 wrote: > > On Thu, Sep 06, 2001 at 05:28:04PM +0200, FEJF wrote: > > > hi, > > > i search through the mailing list and found this question few times... > > > and i have also this problem atm and i didn't find a solution, i want to > > > ask if there is one now ? or perhaps will installing of lvm1.0.1-rc2 help > > > (currently using 0.9.1_beta7) ? > > > > > > root@bolm:[/x] # pvmove /dev/hdh1 > > > pvmove -- moving physical extents in active volume group "vg01" > > > pvmove -- WARNING: if you lose power during the move you may need to > > > restore your LVM metadata from backup! > > > pvmove -- do you want to continue? [y/n] y > > > pvmove -- ERROR reading input physical volume "/dev/hdh1" (still 65536 > > > bytes to read) > > > > > > pvmove -- ERROR "pv_move_pe(): read input PV" pv_move_pe > > > > > > pvmove -- ERROR "pv_move_pe(): read input PV" moving physical extents > > > > This could be because of a disk-error. Do you have io-errors in > > /var/log/messages? > > there are no io-errors... but as the hd makes really scary noise when pvmove > tries to move the remaining bytes. so i think the hd is damaged. > but all i want is to remove the damaged hd. > but pvreduce says i have to use pvmove to get rid of the remaining data and > pvmove gives the errors... > so i can't remove it :/ - is there a way to get rid of the hd without > destroying the rest of the data ? sth. like pvreduce --force ? > > > If so, you will have to modify pvmove to not give up after read-errors. > > how can i do this ? i'm not a coder but if someone has too much time... ;) > > > Maybe a '--ignore-read-errors' option should be added? > > if there's no other way to get rid of the damaged hd... that would be also a > way to solve my problem. > btw: could there be a problem with using reiserfs on the lvm ? Well, assuming your disk has a flaw, the only way to work around your problem is patching pv_move_pe() in order to ignore read errors (this takes place around line 520 in LVM 1.0) which will cause a copy of the data to some other device with probably flaky data in it. In case you've got some filesystem data in there, fsck will complain accordingly and some file or metadata of the filesystem will be gone which will cause more or less filesystem data loss. > > mfg, Florian E.J. Fruth > > ps: at the moment i try a "dd if=/dev/hdh1 of=/dev/null" to see if it also > complains about errors... > > -- > Backups are usefull. Most often when you don't have one ;) > > _______________________________________________ > 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 -- 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 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
