Are you write latency troubled, or read latency troubled?

I don't see free space frag as a huge issue, as lightly loaded as the spindles report to be.


 
_________________________________
Jeff Mohler
Tech Yahoo, Storage Architect, Principal
(831)454-6712
YPAC Gold Member
Twitter: @PrincipalYahoo
CorpIM:  Hipchat & Iris



On Friday, March 25, 2016 11:37 AM, josef radinger <cheese@nosuchhost.net> wrote:


hi

i have a metro cluster (rather old) which is currently responding very
slowly. 7-mode 8.1.4

there is only one aggregate per head, filled at around 72% one one head
and 79% on the other head. attached is a statit and sysstat -x 1 
from one head.

i see lots of partial stripes and only several full stripes. i assume
this should mean not enough free space, which should imho not be a
problem at my aggregates.

what is the correct procedure for performing a free space reallocation?
i did:
* stop all volume-reallocates
* disable read_reallocation on all volumes
* raid.lost_write.enable       off
* aggr options aggr0 resyncsnaptime 5
* reallocate start -A -o aggr0
* wait for finish of reallocate
* aggr options aggr0 resyncsnaptime 60
* enable read_reallocation on all volumes
* reenable all volume-level reallocates

my aggregates have options:

aggr options aggr0
root, diskroot, nosnap=off, raidtype=raid_dp, raidsize=20, 
ignore_inconsistent=off, snapmirrored=off, resyncsnaptime=60, 
fs_size_fixed=off, snapshot_autodelete=on, lost_write_protect=on, 
ha_policy=cfo, hybrid_enabled=off, percent_snapshot_space=5%, 
free_space_realloc=off


any advice?
josef


_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters