Re: [linux-lvm] pvmove and filesystem - un/mount?

[Marian Csontos]

On 07/08/2016 11:03 AM, lejeczek wrote:



On 07/07/16 19:10, Jarkko Oranen wrote:



On 07/07/16 19:01, lejeczek wrote:

hi users,

must be an easy one - what should be(is allowed to do) filesystem
doing while there is a pvmove(failed hard disk) taking place in
underlying LV?

many thanks,


Hi,

pvmove is generally transparent to the layers above, so you can
continue using the system as usual while a pvmove is in progress.
While I have never seen pvmove actually fail (My desktop encountered a
power failure mid-operation once, and it just continued as if nothing
had happened after rebooting), with a failing hard disk, I would avoid
any additional IO while the operation is in progress.



ok, thanks
maybe a bit more tricky, would now downsizing a FS be one thing OK to
do(probably also fsck) ? while pvmove is working?
furthermore, would lvreduce be OK to take pvmote out of a LV ?

I have a bit of puzzle type of situation here to deal with - started
pvmove but seems that HDD is rather in a bad condition for after two
days pvmove is barely at 4%.
Should I let it finish - or - abort pvmove and try fsck; fsreduce;
lvreduce..
hmmm..


Use ddrescue. pvmove is not intended for data rescuing from failing disks.

ddrescue is using different strategy to quickly read whatever it can, 
quickly skipping over any failing regions, attempting to recover those 
on later iterations.


-- Martian







--
Jarkko

___
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


___
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


___
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Re: [linux-lvm] Copying a raw disk image to LVM2

[Марк Коренберг]

If you write from disk image to virtual LVM device, you will never
overwrite LVM metadata. The most convenient way to copy VM image is using
qemu-img, since it may not copy unallocated places of VM image, leaving it
uninitialized in LVM, which is significantly faster.

2016-07-08 20:52 GMT+05:00 Brian McCullough :

>
> I have been hunting for some time over the past couple of days, and find
> several documentss that talk about converting from an LVM2 volume to a
> raw disk image for Xen, but nothing about the reverse.
>
> I have a VHD disk file that I would like to put on to an LVM2 volume,
> like my other DomU guests.
>
> I can see using dd, but am concerned about overwriting the LVM2 header.
>
>
> Does anybody have any suggestions?
>
>
> Thanks,
> Brian
>
>
> ___
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>



-- 
Segmentation fault
___
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Re: [linux-lvm] Copying a raw disk image to LVM2

[Brian McCullough]

On Sat, Jul 09, 2016 at 10:33:51PM +0500,  ?? wrote:
> One note: `sync` does not syncs written data, since it affects only
> data, written through filesystem. You should use `dd 
> conv=fdatasync` instead.

Thank you both.

This is essentially the answer that I got from the Xen group, as well,
so I went ahead and tried it.  No problems.


Brian


___
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Re: [linux-lvm] Copying a raw disk image to LVM2

[Xen]

emmanuel segura schreef op 11-07-2016 0:02:


the lvm metadata is stored in the begining of the physical volume, the
logical volume is simple block device, so using dd you don't overwrite
any lvm header.


I must say I did experience something weird when copying a LUKS 
partition (encrypted).


Apparently LUKS stores information about the device it is on (or was 
one) because I coudln't get it to re-adjust to a larger volume.


cryptsetup resize is supposed to resize to the size of the underlying 
block device.


I had to recreate my LUKS container before it would recognise the new 
size.


E.g. I copied from 2GB volume to 3GB volume using dd.

LUKS kept thinking it was still on a 2GB volume.

So resize didn't work and I could manually resize it to 3GB but 
automatic resize would resize it back to 2GB.


___
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/