| 1 |
On Sep 19, 2011 10:07 PM, "Alan McKinnon" <alan.mckinnon@×××××.com> wrote: |
| 2 |
> |
| 3 |
> My preference is to get rid of this whole artifical |
| 4 |
> disk/block-device/partition/pv/vg/lv nonsense and have one layer that |
| 5 |
> does it all. I really don't see the point in persisting with keeping |
| 6 |
> knowledge of distinct disks all the way through the stack, all of that |
| 7 |
> should just be abstracted into "storage" that can have rules attached |
| 8 |
> where you specify how you want stuff to behave (like mirroring and |
| 9 |
> striping). |
| 10 |
> |
| 11 |
> As it is, each layer is a very thin wrapper around a physical object |
| 12 |
> and we only lose that distinction when we create lvs. Even though I |
| 13 |
> understand how the whole stack works, it's still hard to visualize (5 |
| 14 |
> layers!) and consumes way too much time explaining it to people. All |
| 15 |
> rather unnecessary. |
| 16 |
> |
| 17 |
> I had high hopes that ZFS would take us to a new place where all that |
| 18 |
> would be possible. |
| 19 |
> |
| 20 |
|
| 21 |
Sounds like you need a SAN Storage solution like NetApp or HDS :-) |
| 22 |
|
| 23 |
Heck, OpenFiler is a surprisingly good solution; it's now being used in |
| 24 |
production in my company's subsidiary. |
| 25 |
|
| 26 |
Rgds, |
Archives