hints for a "virtual disk" implementation
hints for a "virtual disk" implementation
- Subject: hints for a "virtual disk" implementation
- From: "Valentin Slavov" <email@hidden>
- Date: Thu, 21 Feb 2008 15:47:37 +0200
Hello
I need to develop a virtual block device which will be used for
testing filesystem operations with files larger than 16TB or so.
Obviously all this space should be virtual (in a sparse image sense),
however there should be some kind of backing store to hold the
filesystem meta data. Since meta data is written at different places
in the volume (hfs+ keeps a backup at the end of the device and so on,
a backing store for certain "ranges" should be used. The backing
stores should be configurable (I was thinking of providing bsd names
and searching the I/O Kit registry for IOMedia objects, and attaching
them to my driver). Another solution would be to implement the driver
as a filter scheme but this is inflexible since backing store cannot
be configured easily.
Although the first solution seems more appropriate, I need to
implement a whole driver stack for virtual devices (like the apple
disk image drivers), but unfortunately I can't find sufficient
documentation for this task. I'd like to know if there are more
appropriate solutions and other hints that might be useful.
Thanks in advance
V.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden