Ok, let me clarify a bit. I mis-spoke, when I spoke of memory I meant ramdisk (fs). This is basically what I was actually visualizing in my head:
1) Boot cdrom into a Linux instance. 2) Mount a read-write filesystem into memory (this is why I asked the size issue, obviously coping the whole cdrom to memory wouldn't be practical) 3) Create a snapshot (I'm am really new to lvm, so I'm still learning what all this means), which would be a small reference table of some sort, plus 32k blocks of changed data. 4)This would then allow "changes" to the cdrom while running in that session until the ram disk filled up? Correct? 5) If a file is created then deleted in an environment like this will the space it was using in the snapshot fs be released?
This is not really an application for LVM snapshots at all. Snapshots would continue to use more and more memory if those files are created and removed, unless the underlying filesystem is very intelligent about space allocation (which the iso9660 filesystem is very likely not).
This is really an application for a "union" mount. This could also be done with a "bind" mount, if the files that need changing can be isolated to a small number of directories. If they are spread all over the filesystem, or their locations are not known ahead of time, a "union" mount would do what you need, overlaying a tmpfs ram-based filesystem on top of the CD-ROM filesystem.
_______________________________________________ linux-lvm mailing list linux-lvm@sistina.com http://lists.sistina.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
