zfs groups writes together into transaction groups; the physical writes
to disk are generally initiated by kernel threads (which appear in
dtrace as threads of the "sched" process). Changing the attribution is
not going to be simple as a single physical write to the pool may
contain data and metad
Did you disable 'atime' updates for your filesystem? Otherwise the file
access times need to be periodically updated and this would happen may
every 15-30 seconds.
Not disabled. But 20MB worth of metadata updates while the system
practically does nothing? Only real things happening is a video
pl
On Wed, 4 Nov 2009, Mario Goebbels wrote:
Did you disable 'atime' updates for your filesystem? Otherwise the file
access times need to be periodically updated and this would happen may
every 15-30 seconds.
Not disabled. But 20MB worth of metadata updates while the system practically
does noth
I've been noticing regular writing activity to my data pool while the
system's relatively idle, just a little read IO. Turns out the
system's writing up to 20MB of data to the pool every 15-30 seconds.
Using iotop from the DTrace Toolkit, apparently the process
responsible is sched. What's going o
On Wed, 4 Nov 2009, Mario Goebbels wrote:
I've been noticing regular writing activity to my data pool while
the system's relatively idle, just a little read IO. Turns out the
system's writing up to 20MB of data to the pool every 15-30 seconds.
Using iotop from the DTrace Toolkit, apparently th
I've been noticing regular writing activity to my data pool while the system's
relatively idle, just a little read IO. Turns out the system's writing up to
20MB of data to the pool every 15-30 seconds. Using iotop from the DTrace
Toolkit, apparently the process responsible is sched. What's going
