Thomas Nau writes:
 > Dear all.
 > I've setup the following scenario:
 > 
 > Galaxy 4200 running OpenSolaris build 59 as iSCSI target; remaining 
 > diskspace of the two internal drives with a total of 90GB is used as zpool 
 > for the two 32GB volumes "exported" via iSCSI
 > 
 > The initiator is an up to date Solaris 10 11/06 x86 box using the above 
 > mentioned volumes as disks for a local zpool.
 > 
 > I've now started rsync to copy about 1GB of data in several thousand 
 > files. During the operation I took the network interface on the iSCSI 
 > target down which resulted in no more disk IO on that server. On the other 
 > hand, the client happily dumps data into the ZFS cache actually completely 
 > finishing all of the copy operation.
 > 
 > Now the big question: we plan to use that kind of setup for email or other 
 > important services so what happens if the client crashes while the network 
 > is down? Does it mean that all the data in the cache is gone forever?
 > 
 > If so, is this a transport independent problem which can also happen if 
 > ZFS used Fibre Channel attached drives instead of iSCSI devices?
 > 

I assume the rsync is not issuing fsyncs (and it's files are 
not opened O_DSYNC). If so,  rsync just works against the
filesystem cache and does not commit the data to disk.

You might want to run sync(1M) after a successful rsync.

A larger  rsync would presumably have blocked. It's just
that the amount of data you needs to rsync fitted in a couple of
transaction groups.

-r



 > Thanks for your help
 > Thomas
 > 
 > -----------------------------------------------------------------
 > GPG fingerprint: B1 EE D2 39 2C 82 26 DA  A5 4D E0 50 35 75 9E ED
 > _______________________________________________
 > zfs-discuss mailing list
 > zfs-discuss@opensolaris.org
 > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to