Back into work today and this seems to work fine, although I'm not going to do it on production kit for both risk and performance reasons (will be used in development platforms though). In reality I'm using 4 & 12GB files rather than the 100MB one in my previous example.
The ZFS way is a nice way to do this, except I'd need to keep a set of blank images around and local disk space is of a premium on a mirrored blade :-( ** Second thoughts I could probably use a compressed volume for this, but I'm not sure if the clone would give me another compressed filesystem, take a while to uncompress or just simply work. ** In my current setup each LDom is getting it's own ZFS filesystem for it's boot disk and uses a shared ZFS filesystem for swap. That way I can stop an LDom, create a snapshot and roll forwards/back at a later stage as needed. Many Thanks Again, -Steve > > I don't think there's any issue with that. Just > don't forget that you may > ot be able to access all 100m of your disk if your > filesystem gets full > before you have effectively allocated blocks of your > file. > > Another way to save time is to use ZFS: create a > blank file (allocated) > on a ZFS filesystem and clone that filesystem each > time you want a new > disk. > > alex. -- This message was posted from opensolaris.org
