Chris Csanady writes:
On 6/26/06, Neil Perrin [EMAIL PROTECTED] wrote:
Robert Milkowski wrote On 06/25/06 04:12,:
Hello Neil,
Saturday, June 24, 2006, 3:46:34 PM, you wrote:
NP Chris,
NP The data will be written twice on ZFS using NFS. This is because NFS
Robert Milkowski wrote On 06/27/06 03:00,:
Hello Chris,
Tuesday, June 27, 2006, 1:07:31 AM, you wrote:
CC On 6/26/06, Neil Perrin [EMAIL PROTECTED] wrote:
Robert Milkowski wrote On 06/25/06 04:12,:
Hello Neil,
Saturday, June 24, 2006, 3:46:34 PM, you wrote:
NP Chris,
NP The data will
Robert Milkowski wrote On 06/25/06 04:12,:
Hello Neil,
Saturday, June 24, 2006, 3:46:34 PM, you wrote:
NP Chris,
NP The data will be written twice on ZFS using NFS. This is because NFS
NP on closing the file internally uses fsync to cause the writes to be
NP committed. This causes the ZIL
Chris,
The data will be written twice on ZFS using NFS. This is because NFS
on closing the file internally uses fsync to cause the writes to be
committed. This causes the ZIL to immediately write the data to the intent log.
Later the data is also written committed as part of the pools
While dd'ing to an nfs filesystem, half of the bandwidth is unaccounted
for. What dd reports amounts to almost exactly half of what zpool iostat
or iostat show; even after accounting for the overhead of the two mirrored
vdevs. Would anyone care to guess where it may be going?
(This is measured
