All of lore.kernel.org
 help / color / mirror / Atom feed
* [linux-lvm] Some questions on "Mirrors cannot be resized while active yet"
@ 2007-08-13 14:36 Simone Gotti
  2007-08-13 15:29 ` Jonathan Brassow
  0 siblings, 1 reply; 3+ messages in thread
From: Simone Gotti @ 2007-08-13 14:36 UTC (permalink / raw)
  To: linux-lvm

[-- Attachment #1: Type: text/plain, Size: 606 bytes --]

Hi all,

lvresize gives the message "Mirrors cannot be resized while active yet."
when trying to resize an active lv.

Simple tests using directly dmsetup let me resize a mirror on the fly
without problems (maybe I'm missing some problematic corner cases). With
a core log everything was resynced every time while with disk log only
the extended part was resynced. 

So, is there only missing code in lvm2 (curious to know if I should be
able to write the missing part) or also the kernel parts (dm-raid1,
dm-log and future dm-clog) needs some more code?

Thanks!

Bye!
-- 
Simone Gotti

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

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

* Re: [linux-lvm] Some questions on "Mirrors cannot be resized while active yet"
  2007-08-13 14:36 [linux-lvm] Some questions on "Mirrors cannot be resized while active yet" Simone Gotti
@ 2007-08-13 15:29 ` Jonathan Brassow
  2007-08-13 18:10   ` Jun'ichi Nomura
  0 siblings, 1 reply; 3+ messages in thread
From: Jonathan Brassow @ 2007-08-13 15:29 UTC (permalink / raw)
  To: LVM general discussion and development

I don't remember all the reasons, but I *think* two of them were:
1) 186304 - potential to spoil redundancy
2) cluster mirroring needed ability to hold to identical logs for a  
short period

Both of these issues have been resolved, so it may be a simple matter  
of turning it on...

  brassow

On Aug 13, 2007, at 9:36 AM, Simone Gotti wrote:

> Hi all,
>
> lvresize gives the message "Mirrors cannot be resized while active  
> yet."
> when trying to resize an active lv.
>
> Simple tests using directly dmsetup let me resize a mirror on the fly
> without problems (maybe I'm missing some problematic corner cases).  
> With
> a core log everything was resynced every time while with disk log only
> the extended part was resynced.
>
> So, is there only missing code in lvm2 (curious to know if I should be
> able to write the missing part) or also the kernel parts (dm-raid1,
> dm-log and future dm-clog) needs some more code?
>
> Thanks!
>
> Bye!
> -- 
> Simone Gotti
> _______________________________________________
> 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/

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

* Re: [linux-lvm] Some questions on "Mirrors cannot be resized while active yet"
  2007-08-13 15:29 ` Jonathan Brassow
@ 2007-08-13 18:10   ` Jun'ichi Nomura
  0 siblings, 0 replies; 3+ messages in thread
From: Jun'ichi Nomura @ 2007-08-13 18:10 UTC (permalink / raw)
  To: LVM general discussion and development

Jonathan Brassow wrote:
> I don't remember all the reasons, but I *think* two of them were:
> 1) 186304 - potential to spoil redundancy
> 2) cluster mirroring needed ability to hold to identical logs for a
> short period

Maybe not a reason why it's disabled, but I think kernel code
needs to change to allow LVM mirror resizing.

LVM2 uses 'noflush' option for suspending mirror maps.

OTOH, currently you need full (flushing) suspend to resize device.
http://lkml.org/lkml/2007/1/19/136

Thanks,
-- 
Jun'ichi Nomura, NEC Corporation of America

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

end of thread, other threads:[~2007-08-13 18:10 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-08-13 14:36 [linux-lvm] Some questions on "Mirrors cannot be resized while active yet" Simone Gotti
2007-08-13 15:29 ` Jonathan Brassow
2007-08-13 18:10   ` Jun'ichi Nomura

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.