Messages in this thread | | | Subject | Re: Linux v2.5.42 | From | "Ben Rafanello" <> | Date | Mon, 14 Oct 2002 12:37:04 -0500 |
| |
On Sun, 13 Oct 2002, Rik van Riel wrote:
>All you need is: > >1) a kernel level driver that can map devices, ie. a device mapper > >2) user space tools that can parse the volume metadata and tell the > kernel how to map each chunk at initialisation or mount time
This works well for the simple cases where the volume metadata is static. However, it does not handle cases where the volume metadata must be updated dynamically, the most obvious cases being striping with parity, mirroring (esp. the more advanced forms/features such as smart resync, partial mirrors, remote mirroring, etc), snapshots, and bad block relocation.
Regards,
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/
| |