Re: [zfs-discuss] clones bound too tightly to its origin

2008-01-08 Thread eric kustarz
This should work just fine with latest bits (Nevada 77 and later) via: http://bugs.opensolaris.org/view_bug.do?bug_id=6425096 Its backport is currently targeted for an early build of s10u6. eric On Jan 8, 2008, at 7:13 AM, Andreas Koppenhoefer wrote: > [I apologise for reposting this... but no

[zfs-discuss] ZFS on OS X port now on macosforge

2008-01-08 Thread Noël Dellofano
Hey everyone, This is just a quick announcement to say that the ZFS on OS X port is now posted for your viewing fun at: http://zfs.macosforge.org/ The page is also linked off of the ZFS Open Solaris page under "ZFS Ports": http://opensolaris.org/os/community/zfs/porting/ This page holds the

Re: [zfs-discuss] Intent logs vs Journaling

2008-01-08 Thread Bill Moloney
> But is seems that when we're talking about full block > writes (such as > sequential file writes) ZFS could do a bit better. > > And as long as there is bandwidth left to the disk > and the controllers, it > is difficult to argue that the work is redundant. If > it's free in that > sense, it

[zfs-discuss] clones bound too tightly to its origin

2008-01-08 Thread Andreas Koppenhoefer
[I apologise for reposting this... but no one replied to my post from Dec, 4th.] Hallo all, while experimenting with "zfs send" and "zfs receive" mixed with cloning on receiver side I found the following... On server A there is a zpool with snapshots created on regular basis via cron. Server B

Re: [zfs-discuss] Intent logs vs Journaling

2008-01-08 Thread Casper . Dik
>consolidating these writes in host cache eliminates some redundant disk >writing, resulting in more productive bandwidth ... providing some ability to >tune the consolidation time window and/or the accumulated cache size may >seem like a reasonable thing to do, but I think that it's typically a

Re: [zfs-discuss] Intent logs vs Journaling

2008-01-08 Thread Bill Moloney
> I have a question that is related to this topic: Why > is there only a (tunable) 5 second threshold and not > also an additional threshold for the buffer size > (e.g. 50MB)? > > Sometimes I see my system writing huge amounts of > data to a zfs, but the disks staying idle for 5 > seconds, althoug

Re: [zfs-discuss] Intent logs vs Journaling

2008-01-08 Thread Thomas Maier-Komor
> > the ZIL is always there in host memory, even when no > synchronous writes > are being done, since the POSIX fsync() call could be > made on an open > write channel at any time, requiring all to-date > writes on that channel > to be committed to persistent store before it returns > to the appl

Re: [zfs-discuss] Does block allocation for small writes work over iSCSI?

2008-01-08 Thread Andre Wenas
Although it looks like possible, but very complex architecture. If you can wait, please explore pNFS: http://opensolaris.org/os/project/nfsv41/ What is pNFS? * The pNFS protocol allows us to separate a NFS file system's data and metadata paths. With a separate data path we are free to