[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: x-blockdev-reopen & block-dirty-bitmaps
From: |
Kevin Wolf |
Subject: |
Re: x-blockdev-reopen & block-dirty-bitmaps |
Date: |
Tue, 18 Feb 2020 16:45:42 +0100 |
User-agent: |
Mutt/1.12.1 (2019-06-15) |
Am 18.02.2020 um 16:35 hat Peter Krempa geschrieben:
> > This sounds like a case that blockdev-snapshot might be able to solve:
> > After the offline copy has completed, you blockdev-add the whole backing
> > chain for the target and then use blockdev-snapshot to add the active
> > layer (that had 'backing': null) to it.
>
> Interresting idea! I'll give it a try. If you think that at least trying
> blockdev-reopen in this case might be of some value I might want to give
> it a try since I have some of the framework prepared now.
Anything that tests blockdev-reopen in new cases has some value. :-)
Kevin
- x-blockdev-reopen & block-dirty-bitmaps, John Snow, 2020/02/14
- Re: x-blockdev-reopen & block-dirty-bitmaps, Kevin Wolf, 2020/02/14
- Re: x-blockdev-reopen & block-dirty-bitmaps, John Snow, 2020/02/14
- Re: x-blockdev-reopen & block-dirty-bitmaps, Kevin Wolf, 2020/02/17
- Re: x-blockdev-reopen & block-dirty-bitmaps, John Snow, 2020/02/17
- Re: x-blockdev-reopen & block-dirty-bitmaps, Peter Krempa, 2020/02/18
- Re: x-blockdev-reopen & block-dirty-bitmaps, Kevin Wolf, 2020/02/18
- Re: x-blockdev-reopen & block-dirty-bitmaps, Peter Krempa, 2020/02/18
- Re: x-blockdev-reopen & block-dirty-bitmaps,
Kevin Wolf <=
Re: x-blockdev-reopen & block-dirty-bitmaps, Alberto Garcia, 2020/02/17