volume management

Gergely CZUCZY phoemix at harmless.hu
Tue Apr 10 11:37:05 UTC 2007


On Tue, Apr 10, 2007 at 01:08:50PM +0200, Ivan Voras wrote:
> Gergely CZUCZY wrote:
> 
> >1) to increment them, i need a device(disk/slice/label/etc).
> >if i increment a lot, i need a lot of devices.
> 
> Are you concerned about the number of entries in the /dev file system? Why?
> 
> >2) these incrementum-devices (the ones i increment by),
> >have to be made, each of the has to be chopped from the
> >storage pool.
> 
> The whole GEOM tree is your storage pool.
>
> >please also look at the bsdlabel issue i have mentioned.
> >gconcating is the most easy part of that. recursively
> >bsdlabeling is what i have mostly referred to as the
> >real issue. i really don't think this is the way to
> >do it...
> 
> If I understood you correctly, your problem is that you don't want to use entire drives for 
> extending your file systems, but only parts of them, right?
The mot accurate description would be the functionality
of linux's LVM in the scope of volume management, that's why
i had given this subject to this email/topic.

I have a storage pool (the last part of a disk), from which
i want to chop little pieces for services, and i want to be
able to increment these little pieces whenever needed.

Like i have a pool of 100G. i have two services, i allocate
10G and 20G for them. 30G is used. Upon need, i allocate a bit
more first to service1, then it will have 15G of space
available. After this, the other one might need a bit more
space, so i give it a bit more, let's say 8G, and it will
have 28G of space.

It's really what i have described here several times. Having
a storage pool, from which volume management can be done. Dynamic
allication of storage areas from the same pool, and having the
abilit to increase the size of the previously allocated storage
areas when it's needed. It's kinda like what's Linux's LVM's
main feature. And i'm a bit surprised that FreeBSD doesn't
have a similar thing.

I have read the README of gvirstor and looked around in the source
tree of it. It seems like me, that gvirstor is a bit different
then what I need. It allows me to overrun the available physical
space, while i need to be able to increment the storage's availabe
size when it's needed.

Farthermore as I have seen gvirstor only provides one storage area
from a given provider, and what I need is many provided storage areas
from the very same pool.



Bye,

Gergely Czuczy
mailto: gergely.czuczy at harmless.hu

-- 
Weenies test. Geniuses solve problems that arise.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 2121 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-geom/attachments/20070410/81c0db58/attachment.pgp


More information about the freebsd-geom mailing list