Re: [zfs-discuss] ZFS: unreliable for professional usage?

spot for This pool was not unmounted cleanly due to a hardware fault and data has been lost. The name of timestamp line contains the date which can be recovered to. Use the command # zfs reframbulocate this that -t timestamp to revert to timestamp --dave -- David Collier-Brown

Re: [zfs-discuss] Does your device honor write barriers?

, much less Infinite) c-b -- David Collier-Brown| Always do right. This will gratify Sun Microsystems, Toronto | some people and astonish the rest dav...@sun.com | -- Mark Twain cell: (647) 833-9377, bridge: (877) 385-4099 code: 506 9191

Re: [zfs-discuss] ZFS core contributor nominations

://mail.opensolaris.org/mailman/listinfo/zfs-discuss -- David Collier-Brown| Always do right. This will gratify Sun Microsystems, Toronto | some people and astonish the rest dav...@sun.com | -- Mark Twain cell: (647) 833-9377, bridge: (877) 385-4099

Re: [zfs-discuss] Why is st_size of a zfs directory equal to the

folks find it on? --dave (an external consultant, these days) c-b -- David Collier-Brown| Always do right. This will gratify Sun Microsystems, Toronto | some people and astonish the rest dav...@sun.com | -- Mark Twain cell: (647) 833-9377

Re: [zfs-discuss] Tuning for a file server, disabling data cache (almost)

also had to narrow a stripe for the particular load being discussed... --dave -- David Collier-Brown| Always do right. This will gratify Sun Microsystems, Toronto | some people and astonish the rest [EMAIL PROTECTED] | -- Mark Twain cell: (647

[zfs-discuss] Sidebar re ABI stability (was Segmentation fault / core dump)

, back when I was an employee. --dave (who's a contractor) c-b -- David Collier-Brown| Always do right. This will gratify Sun Microsystems, Toronto | some people and astonish the rest [EMAIL PROTECTED] | -- Mark Twain cell: (647) 833-9377

Re: [zfs-discuss] Sidebar to ZFS Availability discussion

Collier-Brown| Always do right. This will gratify Sun Microsystems, Toronto | some people and astonish the rest [EMAIL PROTECTED] | -- Mark Twain cell: (647) 833-9377, bridge: (877) 385-4099 code: 506 9191

[zfs-discuss] Sidebar to ZFS Availability discussion

(at home) c-b -- David Collier-Brown| Always do right. This will gratify Sun Microsystems, Toronto | some people and astonish the rest [EMAIL PROTECTED] | -- Mark Twain cell: (647) 833-9377, bridge: (877) 385-4099 code: 506 9191

Re: [zfs-discuss] Supermicro AOC-SAT2-MV8 hang when drive removed

/ ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss -- David Collier-Brown| Always do right. This will gratify Sun Microsystems, Toronto

Re: [zfs-discuss] [zfs-code] Peak every 4-5 second

://milek.blogspot.com ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss -- David Collier-Brown| Always do

Re: [zfs-discuss] [zfs-code] Peak every 4-5 second

. *** ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss -- David Collier-Brown| Always do right. This will gratify Sun Microsystems, Toronto | some people and astonish the rest [EMAIL

Re: [zfs-discuss] OT: Formatting Problem of ZFS Adm Guide (pdf)

important consideration IMO. :-) This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss -- David Collier-Brown| Always do

Re: [zfs-discuss] ZFS deduplication

as the checksum algorithm would be much more interesting. I'm going to try that now and see how it compares with fletcher2 for a small contrived test. -- David Collier-Brown| Always do right. This will gratify Sun Microsystems, Toronto | some people and astonish the rest

[zfs-discuss] Some basic questions about getting the best performance for database usage

. --dave -- David Collier-Brown| Always do right. This will gratify Sun Microsystems, Toronto | some people and astonish the rest [EMAIL PROTECTED] | -- Mark Twain (905) 943-1983, cell: (647) 833-9377, (800) 555-9786 x56583 bridge: (877) 385-4099

Re: [zfs-discuss] Some basic questions about getting the best performance for database usage

David Collier-Brown wrote: ZFS copy-on-write results in tables' contents being spread across the full width of their stripe, which is arguably a good thing for transaction processing performance (or at least can be), but makes sequential table-scan speed degrade. If you're doing

Re: [zfs-discuss] Issue with simultaneous IO to lots of ZFS pools

, I'm also volunteering to help provide it: I'm not a storage or ZFS guy, but I am an author, and will happily help my Smarter Colleagues[tm] to write it up. -- David Collier-Brown| Always do right. This will gratify Sun Microsystems, Toronto | some people and astonish the rest

Re: [zfs-discuss] Issue with simultaneous IO to lots of ZFS pools

workload without cutting into performance. --dave -- David Collier-Brown| Always do right. This will gratify Sun Microsystems, Toronto | some people and astonish the rest [EMAIL PROTECTED] | -- Mark Twain (905) 943-1983, cell: (647) 833-9377, (800

Re: [zfs-discuss] How many ZFS pools is it sensible to use on a single server?

We've discussed this in considerable detail, but the original question remains unanswered: if an organization *must* use multiple pools, is there an upper bound to avoid or a rate of degradation to be considered? --dave -- David Collier-Brown| Always do right. This will gratify