Hi Pascal, On Wed, 2014-05-14 at 12:42 +0200, pviltard@xxxxxxx wrote: > Hello, > > I managed to make communicate a solaris 10 x86 with the Fedora 20 targetcli with the fiber channel. > > I changed the card Pci Express Fiber Channel on Solaris and especially to configure Switch SanBox on 2-16. > > > I have problems of performances: format a disk solaris is very very slow. > > Have you tools for diagnostic? > > I also fetch of the side ZFS (Zil and L2Arc). > > I shall test only with an iblock disk To see the difference. > Note that by default, FILEIO backends will set the O_DSYNC flag (instead of buffered writes), to ensure data integrity in the face of target power failures. It's possible to set 'buffered=true' during the creation of a FILEIO backstore, and enable using the buffer cache to store writes, so that WRITEs are ACKed once they hit RAM, and flushed in the background or explicitly by a FUA WRITE / SYNCHRONIZE_CACHE command from the initiator. Note this can significantly increase performance, but during a power failure there is no way to guarantee that WRITEs that have not been flushed to persistent storage won't be lost. See the FILEIO section at: http://www.linux-iscsi.org/wiki/Target#Backstores Another option is to use bcache in writeback mode along with an SSD to absorb WRITEs for the backend device, and then export the struct block_device using IBLOCK. This will ensure that all WRITEs hit the SSD before being ACKed back to the initiator, and withstand a target power failure. --nab -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
