Dietmar Maurer wrote:
Also, on _loaded_ systems, I noticed creating/removing logical volumes
can take really long (several minutes); where allocating a file of a
given size would just take a fraction of that.
Allocating a file takes much longer, unless you use a 'sparse' file.
If you mean "a
> Also, on _loaded_ systems, I noticed creating/removing logical volumes
> can take really long (several minutes); where allocating a file of a
> given size would just take a fraction of that.
Allocating a file takes much longer, unless you use a 'sparse' file.
- Dietmar
--
To unsubscribe from
Chris Webb wrote:
Javier Guerra writes:
i'd just want to add my '+1 votes' on both getting rid of JVM
dependency and using block devices (usually LVM) instead of ext3/btrfs
If the chunks into which the virtual drives are split are quite small (say
the 64MB used by Hadoop), LVM may be a less
On Fri, Oct 23, 2009 at 8:10 PM, Alexander Graf wrote:
>
> On 23.10.2009, at 12:41, MORITA Kazutaka wrote:
>
> On Fri, Oct 23, 2009 at 12:30 AM, Avi Kivity wrote:
>
> How is load balancing implemented? Can you move an image transparently
>
> while a guest is running? Will an image be moved clos
On Fri, Oct 23, 2009 at 9:58 AM, Chris Webb wrote:
> If the chunks into which the virtual drives are split are quite small (say
> the 64MB used by Hadoop), LVM may be a less appropriate choice. It doesn't
> support very large numbers of very small logical volumes very well.
absolutely. the 'nice
Javier Guerra writes:
> i'd just want to add my '+1 votes' on both getting rid of JVM
> dependency and using block devices (usually LVM) instead of ext3/btrfs
If the chunks into which the virtual drives are split are quite small (say
the 64MB used by Hadoop), LVM may be a less appropriate choice
