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 mounting the same FS by several
different machines? Is there a way around this?
Mike
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 filesystem as read/write while the
> others would mount it read-only. For my application, all files are
> written once then only ever read or deleted.
I know this doesn't work for UFS. I'm fairly certain this won't work for
ZFS for many of the same reasons. (Writes in any hosts buffer cache,
inflight transactions, metadata updates, etc.) Why not use NFS?
The reason why it wouldn't work is because of the system caching
reads. The FS assumes that it knows everything that is going into/out
of the file system but this is not true in a parallel file system.
What you will find is that while you can mount the UFS (ZFS should
prevent mounting but that's another story), any updates on previously
read files will not be visible.
I agree that you should look at NFS.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
