All of lore.kernel.org
 help / color / mirror / Atom feed
* A target for hotswap?
@ 2015-05-04 10:37 Akira Hayakawa
  2015-05-04 16:06 ` Mike Snitzer
  0 siblings, 1 reply; 3+ messages in thread
From: Akira Hayakawa @ 2015-05-04 10:37 UTC (permalink / raw)
  To: device-mapper development

Hi,

Some DM target requires additional device that could be a single point of failure.
Let's consider dm-cache.
dm-cache requires a HDD and a SSD and if SSD is dead, the data is lost.
To protect from this, SSD can be built RAID. But RAID isn't an ideal solution with SSD
because the devices can be dead at the same time. Cost is the another problem of course.

So, let's think about hotswap.
A hotswap device has an active device and multiple ready devices.
The active device is usually used and when the device is ordered to swap by
a ready device it starts to sync the two devices and change the active device
when sync is over. It's not simply dd-ing the devices because I/O isn't suspended and
not all region is necessarily copied.
You can order swapping whenever you like to. For example, swapping every week can be
double the longevity of the cache device.

I don't know how I can do this with DM targets.
Do other part of linux technologies have such functinality? Please teach me if so.

- Akira

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: A target for hotswap?
  2015-05-04 10:37 A target for hotswap? Akira Hayakawa
@ 2015-05-04 16:06 ` Mike Snitzer
  2015-05-06  1:34   ` Akira Hayakawa
  0 siblings, 1 reply; 3+ messages in thread
From: Mike Snitzer @ 2015-05-04 16:06 UTC (permalink / raw)
  To: Akira Hayakawa; +Cc: device-mapper development

On Mon, May 04 2015 at  6:37am -0400,
Akira Hayakawa <ruby.wktk@gmail.com> wrote:

> Hi,
> 
> Some DM target requires additional device that could be a single point of failure.
> Let's consider dm-cache.
> dm-cache requires a HDD and a SSD and if SSD is dead, the data is lost.
> To protect from this, SSD can be built RAID. But RAID isn't an ideal solution with SSD
> because the devices can be dead at the same time. Cost is the another problem of course.
> 
> So, let's think about hotswap.
> A hotswap device has an active device and multiple ready devices.
> The active device is usually used and when the device is ordered to swap by
> a ready device it starts to sync the two devices and change the active device
> when sync is over. It's not simply dd-ing the devices because I/O isn't suspended and
> not all region is necessarily copied.
> You can order swapping whenever you like to. For example, swapping every week can be
> double the longevity of the cache device.
> 
> I don't know how I can do this with DM targets.
> Do other part of linux technologies have such functinality? Please teach me if so.

You could probably use lvm2's pvmove (it uses old dm-mirror target to swap over).

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: A target for hotswap?
  2015-05-04 16:06 ` Mike Snitzer
@ 2015-05-06  1:34   ` Akira Hayakawa
  0 siblings, 0 replies; 3+ messages in thread
From: Akira Hayakawa @ 2015-05-06  1:34 UTC (permalink / raw)
  To: Mike Snitzer; +Cc: device-mapper development

Thanks Mike,

Great.

I just look this picture and start to think pvmove must be what I want.
http://www.redhat.com/magazine/007may05/features/storage/figs/pvmove.jpg

- Akira

On 2015/05/05 1:06, Mike Snitzer wrote:
> On Mon, May 04 2015 at  6:37am -0400,
> Akira Hayakawa <ruby.wktk@gmail.com> wrote:
> 
>> Hi,
>>
>> Some DM target requires additional device that could be a single point of failure.
>> Let's consider dm-cache.
>> dm-cache requires a HDD and a SSD and if SSD is dead, the data is lost.
>> To protect from this, SSD can be built RAID. But RAID isn't an ideal solution with SSD
>> because the devices can be dead at the same time. Cost is the another problem of course.
>>
>> So, let's think about hotswap.
>> A hotswap device has an active device and multiple ready devices.
>> The active device is usually used and when the device is ordered to swap by
>> a ready device it starts to sync the two devices and change the active device
>> when sync is over. It's not simply dd-ing the devices because I/O isn't suspended and
>> not all region is necessarily copied.
>> You can order swapping whenever you like to. For example, swapping every week can be
>> double the longevity of the cache device.
>>
>> I don't know how I can do this with DM targets.
>> Do other part of linux technologies have such functinality? Please teach me if so.
> 
> You could probably use lvm2's pvmove (it uses old dm-mirror target to swap over).
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-05-06  1:34 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-04 10:37 A target for hotswap? Akira Hayakawa
2015-05-04 16:06 ` Mike Snitzer
2015-05-06  1:34   ` Akira Hayakawa

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.