From: CaT <cat@zip.com.au>
To: Heinz Mauelshagen <mauelshagen@redhat.com>
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com
Subject: Re: 2.6.16.20/dm: can't create more then one snapshot of an lv
Date: Tue, 20 Jun 2006 22:17:10 +1000 [thread overview]
Message-ID: <20060620121710.GA2059@zip.com.au> (raw)
In-Reply-To: <20060620115545.GB4566@redhat.com>
On Tue, Jun 20, 2006 at 01:55:45PM +0200, Heinz Mauelshagen wrote:
> On Tue, Jun 20, 2006 at 09:46:13PM +1000, CaT wrote:
> > On Tue, Jun 20, 2006 at 12:02:09PM +0200, Heinz Mauelshagen wrote:
> > > How many snapshots active at once ?
> >
> > 1. I can start more then 1 premade snapshots just fine and use them
> > but the moment I add another one a freeze occurs.
>
> Well, that's fairly few ;)
Yes. I thought so too. :)
> > > I guess this is a kcopyd scalability issue which needs addressing.
> >
> > Well in the end I'm hoping to get at least 7. Hopefully that's not
> > insane. :)
>
> No, I was assuming, you were trying to activate plenty.
Not yet. Though as I said I plan to max out at 7 or so.
> FYI: the snapshot code in 2.6.17-rc has received a fair amount of fixes
> which might help this vs. 2.6.16.20.
I tried 2.6.17 and I get the same issue. Any other kernel you want me to
try? I can reboot this box at will at the moment and test.
--
"To the extent that we overreact, we proffer the terrorists the
greatest tribute."
- High Court Judge Michael Kirby
next prev parent reply other threads:[~2006-06-20 12:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 2:00 2.6.16.20/dm: can't create more then one snapshot of an lv CaT
2006-06-20 0:54 ` CaT
2006-06-20 10:02 ` Heinz Mauelshagen
2006-06-20 10:02 ` Heinz Mauelshagen
2006-06-20 11:46 ` CaT
2006-06-20 11:55 ` Heinz Mauelshagen
2006-06-20 11:55 ` Heinz Mauelshagen
2006-06-20 12:17 ` CaT [this message]
2006-06-20 14:20 ` Alasdair G Kergon
2006-06-20 14:20 ` Alasdair G Kergon
2006-06-27 2:55 ` CaT
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060620121710.GA2059@zip.com.au \
--to=cat@zip.com.au \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mauelshagen@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.