Hi, How is read and write usage determined regarding the read and write thresholds defined in the ALU container in the client config? Is there a way I can see what percentage the disks are currently at? Also, are there settings/criteria for determining which AFR disk is used for primary reads and writes? Currently, I can see some margin of failover between two AFR disks in a ALU configuration but often I have to restart the client due to transport disconnect errors. Here is my client config: volume client1 type protocol/client option transport-type tcp/client option remote-host 10.10.48.2 option remote-subvolume brick end-volume volume client2 type protocol/client option transport-type tcp/client option remote-host 10.10.48.3 option remote-subvolume brick end-volume volume client3 type protocol/client option transport-type tcp/client option remote-host 10.10.48.4 option remote-subvolume brick end-volume volume client4 type protocol/client option transport-type tcp/client option remote-host 10.10.48.5 option remote-subvolume brick end-volume volume afr1 type cluster/afr subvolumes client1 client3 option replicate *:2 end-volume volume afr2 type cluster/afr subvolumes client2 client4 option replicate *:2 end-volume volume unify type cluster/unify subvolumes afr1 afr2 option scheduler alu option alu.limits.min-free-disk 30GB option alu.limits.max-open-files 10000 option alu.order disk-usage:read-usage:write-usage:open-files-usage:disk-speed-usage option alu.disk-usage.entry-threshold 2GB option alu.disk-usage.exit-threshold 64MB option alu.open-files-usage.entry-threshold 1024 option alu.open-files-usage.exit-threshold 32 option alu.read-usage.entry-threshold 10% option alu.open-files-usage.exit-threshold 32 option alu.read-usage.entry-threshold 10% option alu.read-usage.exit-threshold 4% option alu.write-usage.entry-threshold 10% option alu.write-usage.exit-threshold 4% option alu.stat-refresh.interval 10sec # option alu.stat-refresh.num-file-create 10 option readdir-force-success on end-volume volume writebehind type performance/write-behind option aggregate-size 131072 subvolumes unify end-volume volume readahead type performance/read-ahead option page-size 65536 option page-count 16 subvolumes writebehind end-volume Thanks, Majied Najjar