From: Alasdair G Kergon <agk@redhat.com>
To: mingz@ele.uri.edu
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Re: VG vg1 metadata writing failed
Date: Mon, 6 Jun 2005 22:21:11 +0100 [thread overview]
Message-ID: <20050606212110.GV15809@agk.surrey.redhat.com> (raw)
In-Reply-To: <1118091844.5509.79.camel@localhost.localdomain>
On Mon, Jun 06, 2005 at 05:04:04PM -0400, Ming Zhang wrote:
> this is reproducible on another box.
There is currently a 64k hard-coded limit on metadata size.
Some of the lvm2 tool algorithms also get quite slow when
there are lots of entities.
Keep an eye on the CVS code - there was an allocation speed-up
added recently, and the 64k limit should be disappearing very
soon too.
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2005-06-06 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 19:48 [linux-lvm] VG vg1 metadata writing failed Ming Zhang
2005-06-06 19:53 ` [linux-lvm] " Ming Zhang
2005-06-06 21:04 ` Ming Zhang
2005-06-06 21:21 ` Alasdair G Kergon [this message]
2005-06-06 21:27 ` Ming Zhang
2005-06-07 14:51 ` Alasdair G Kergon
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=20050606212110.GV15809@agk.surrey.redhat.com \
--to=agk@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=mingz@ele.uri.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).