Of course performances are much better when exporting an entire disk than using a file. The obvious reason is that with a file, I/Os need to go through the entire filesystem layer and this can be very slow.
With ZFS, an alternative is to a use a ZFS volume instead of a file on a ZFS filesystem. That way you will have better performance (because you skip the filesystem layer) and still have the benefit of ZFS (snapshot, clone...). You can create a ZFS volume with the "zfs create -V" option and you just have to specify the size of the volume you want (and that's much faster than a mkfile), for example: # zfs create -V 10G tank/myvolume Then export the volume as a virtual disk: # ldm add-vdsdev /dev/zvol/dsk/tank/myvolume myvolume at primary-vds0 Note that you need to use Solaris 10 Update 5 or patch 127127-11 so that the ZFS volume is exported as a full disk. Rgds, alex. syed wrote: > Hi, > > I am trying to migrate few applications from legacy servers on to a t2000 > with 4 logical > domains connected to a SAN ,I was wondering if anyone experienced > performace issues > while using disk image which resides inside a zfs pool and is exported as a > vdisk vs > exporting the entire disk as vdisk.Any info would be much appreciated. > > > Thanks > > Regards > -- > This message was posted from opensolaris.org > _______________________________________________ > ldoms-discuss mailing list > ldoms-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
