Re: [zfs-discuss] [cryptography] rolling hashes, EDC/ECC vs MAC/MIC, etc.

2011-05-22 Thread Eugen Leitl
- Forwarded message from Nico Williams n...@cryptonector.com - From: Nico Williams n...@cryptonector.com Date: Sat, 21 May 2011 16:22:27 -0500 To: Crypto discussion list cryptogra...@randombit.net Subject: Re: [cryptography] rolling hashes, EDC/ECC vs MAC/MIC, etc. Reply-To: Crypto

Re: [zfs-discuss] [cryptography] rolling hashes, EDC/ECC vs MAC/MIC, etc.

2011-05-22 Thread Richard Elling
On May 21, 2011, at 11:56 AM, Eugen Leitl eu...@leitl.org wrote: - Forwarded message from Zooko O'Whielacronx zo...@zooko.com - From: Zooko O'Whielacronx zo...@zooko.com Date: Sat, 21 May 2011 12:50:19 -0600 To: Crypto discussion list cryptogra...@randombit.net Subject: Re:

[zfs-discuss] iSCSI pool timeouts during high latency moments

2011-05-22 Thread Jim Klimov
Hi all, As I wrote before, I have a dpcool implemented as an iSCSI device stored in a volume of my physical pool. When there are many operations, such as attempts to destroy a dataset (which leads to many small IOs in my config), the iSCSI device is 100% busy for hours, latencies can grow to

Re: [zfs-discuss] iSCSI pool timeouts during high latency moments

2011-05-22 Thread Richard Elling
comment below... On May 22, 2011, at 8:31 AM, Jim Klimov wrote: Hi all, As I wrote before, I have a dpcool implemented as an iSCSI device stored in a volume of my physical pool. When there are many operations, such as attempts to destroy a dataset (which leads to many small IOs in my

Re: [zfs-discuss] iSCSI pool timeouts during high latency moments

2011-05-22 Thread Jim Klimov
2011-05-22 20:39, Richard Elling wrote: This means that the target closed the connection because there was already a task in progress. Likely this was the retry after the timeout. By default, these timeouts are quite long, so by now performance is already terrible. I'm not sure if you

Re: [zfs-discuss] [cryptography] rolling hashes, EDC/ECC vs MAC/MIC, etc.

2011-05-22 Thread Nico Williams
On Sun, May 22, 2011 at 10:20 AM, Richard Elling richard.ell...@gmail.com wrote: ZFS already tracks the blocks that have been written, and the time that they were written. So we already know when something was writtem, though that does not answer the question of whether the data was changed. I

Re: [zfs-discuss] [cryptography] rolling hashes, EDC/ECC vs MAC/MIC, etc.

2011-05-22 Thread Nico Williams
On Sun, May 22, 2011 at 1:52 PM, Nico Williams n...@cryptonector.com wrote: [...] Or perhaps you'll argue that no one should ever need bi-di replication, that if one finds oneself wanting that then one has taken a wrong turn somewhere. You could also grant the premise and argue instead that

Re: [zfs-discuss] [cryptography] rolling hashes, EDC/ECC vs MAC/MIC, etc.

2011-05-22 Thread Edward Ned Harvey
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss- boun...@opensolaris.org] On Behalf Of Eugen Leitl This would enable applications—without needing any further in-filesystem code—to perform a Merkle Tree sync, which would range from noticeably more efficient to dramatically more

Re: [zfs-discuss] [cryptography] rolling hashes, EDC/ECC vs MAC/MIC, etc.

2011-05-22 Thread Richard Elling
On May 22, 2011, at 11:52 AM, Nico Williams n...@cryptonector.com wrote: On Sun, May 22, 2011 at 10:20 AM, Richard Elling richard.ell...@gmail.com wrote: ZFS already tracks the blocks that have been written, and the time that they were written. So we already know when something was writtem,