If a write call attempted to write X bytes of data, and if writecall writes
only x ( hwere x X) bytes, then we call that write as short write.
-Masthan
Torrey McMahon [EMAIL PROTECTED] wrote:
Robert Milkowski wrote:
Hello dudekula,
Thursday, February 15, 2007, 11:08:26 AM, you
Hi,
I just deploy the ZFS on an SAN attach disk array and it's working fine.
How do i get dual pathing advantage of the disk ( like DMP in Veritas).
Can someone point to correct doc and setup.
Thanks in Advance.
Rgds
Vikash Gupta
This message posted from opensolaris.org
http://docs.sun.com/source/819-0139/index.html
On 2/17/07, Vikash Gupta [EMAIL PROTECTED] wrote:
Hi,
I just deploy the ZFS on an SAN attach disk array and it's working fine.
How do i get dual pathing advantage of the disk ( like DMP in Veritas).
Can someone point to correct doc and setup.
Is there a best practice guide for using zfs as a basic rackable small
storage solution?
I'm considering zfs with a 2U 12 disk Xeon based server system vs
something like a second hand FAS250.
Target enviroment is mixature of Xen or VI hosts via iSCSI and nfs/cifs.
Being able to take snapshots
Hi Nicholas,
ZFS itself is very stable and very effective as fast FS in our
experience. If you browse the archives of the list you'll see that NFS
performance is pretty acceptable, with some performance/RAM quirks
around small files:
http://www.opensolaris.org/jive/message.jspa?threadID=19858
Hi Folks
I believe that the word would have gone around already, Google engineers have
published a paper on disk reliability. It might supplement the ZFS FMA
integration and well - all the numerous debates on spares etc etc over here.
To quote /.
The Google engineers just published a paper on
I'm using ZFS on both EMC and Pillar arrays with PowerPath and MPxIO,
respectively. Both work fine - the only caveat is to drop your sd_queue to
around 20 or so, otherwise you can run into an ugly display of bus resets.
This message posted from opensolaris.org
