After a quick look through the device mapper code, it appears that
device mapper knows nothing of the metadata format of the
volumes/partitions/etc. that it is mapping. This will work well for
cases where the metadata for the volume/volume group does not have to be
updated at runtime. However, it appears that device mapper needs a
kernel module to handle those cases where the volume metadata must
be updated during runtime (cases such as RAID 5, Mirroring -
particularly the fancier forms with features like smart resync
and hot spot mirroring, bad block relocation, etc.). Thus, to
support AIX (or any other enterprise level volume manager since
they all tend to have similar features) would require more than
"just a little bit of userland code", it would require a significant
amount of kernel code as well.
>There is a little tool called dmsetup:
>
>http://people.sistina.com/~thornber/dmsetup_8.html
>
>that is essentially a very simple volume manager. But it does give
>you full access to all the facilities of device-mapper. eg, I just
Thanks for the link! I'll give it a try.
Ben Rafanello
EVMS Team Lead
IBM Linux Technology Center
(512) 838-4762
benr@us.ibm.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/