Not to be a ninny, but a one-write/many read is pretty much the design
scenario for using CacheFS in conjunction with NFS on the client side.
That is, assuming that only one client is doing the writing. If all your
clients are doing writing (just maybe not to the same file), then you
DON'T hav
On Jan 14, 2007, at 21:37, Wee Yeh Tan wrote:
On 1/15/07, Torrey McMahon <[EMAIL PROTECTED]> wrote:
Mike Papper wrote:
>
> The alternative I am considering is to have a single filesystem
> available to many clients using a SAN (iSCSI in this case). However
> only one client would mount the ZFS
On Sun, Jan 14, 2007 at 07:06:20PM -0800, Mike Papper wrote:
> Thanks for the feedback, it seems caching is the main concern and if I
> always only write any given file once (then perhaps do a flush and a
> close after the write to empty the cache) and from then only ever read
> the file, will t
Thanks for the feedback, it seems caching is the main concern and if I
always only write any given file once (then perhaps do a flush and a
close after the write to empty the cache) and from then only ever read
the file, will the scheme I had in mind work?
Also, will ZFS really prevent my moun
On 1/15/07, Torrey McMahon <[EMAIL PROTECTED]> wrote:
Mike Papper wrote:
>
> The alternative I am considering is to have a single filesystem
> available to many clients using a SAN (iSCSI in this case). However
> only one client would mount the ZFS filesystem as read/write while the
> others woul
Mike Papper wrote:
The alternative I am considering is to have a single filesystem
available to many clients using a SAN (iSCSI in this case). However
only one client would mount the ZFS filesystem as read/write while the
others would mount it read-only. For my application, all files are
wri
Hi, I am considering using ZFS so that multiple clients can "share" the
same filesystem. I know that ZFS does not support a distributed filesystem.
The alternative I am considering is to have a single filesystem
available to many clients using a SAN (iSCSI in this case). However only
one clien
