From: Michael Marxmeier <mike@msede.com>
To: linux-lvm@msede.com
Subject: Re: [linux-lvm] balance functionality
Date: Tue, 09 May 2000 18:42:41 +0200 [thread overview]
Message-ID: <39184001.EE90C818@msede.com> (raw)
Forwarded message from Matthew O'Keefe (okeefe@borg.umn.edu) ...
-------- Original Message --------
From: "Matthew O'Keefe" <okeefe@borg.umn.edu>
Date: Tue, 9 May 2000 07:37:09 -0500
Subject: Re: [linux-lvm] balance functionality
Message-ID: <20000509073709.A96956@styx.>
References: <20000505230812.A449@HAL.HAL>
In-Reply-To: <20000505230812.A449@HAL.HAL>
On Fri, May 05, 2000 at 11:08:12PM -0400, Jean-Francois Landry wrote:
> Greetings,
>
> I was wondering if the current LVM implementation supports functionality similar
> to the Digi^H^H^H^HCompaq Tru64 Unix "balance" utility. This utility rearranges
> data across volumes ( I think this maps to PV's in the Linux LVM) so that files
> are scattered evenly in a concatenated volume. Anyone willing to comment on
> that? Sorry if this has been covered but I was unable to find anything in the
> mailing lists archives.
Hi,
I don't think so. Since the volume manager only knows about blocks,
not files, it cannot make decisions about how blocks for a particular
file should be distributed. RAID-0 striping can help in general with
this
problem. Our Linux cluster file system (GFS -- see
www.globalfilesystem.org)
has a balancer, but it is out-of-date, as the balancer has not kept up
with our latest code updates. We plan to include this functionality
in the
future.
Matt O'Keefe
>
> Cheers,
> Jean-Francois Landry
> --
> I'm famous. Ain't taht a bitch!
> Thelonious Sphere Monk
> --
next reply other threads:[~2000-05-09 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-09 16:42 Michael Marxmeier [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-05-06 3:08 [linux-lvm] balance functionality Jean-Francois Landry
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=39184001.EE90C818@msede.com \
--to=mike@msede.com \
--cc=linux-lvm@msede.com \
--cc=okeefe@borg.umn.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