On 2019-07-02 07:50, [email protected] wrote: > ZFS's feature set is pretty much enough for my use case, why should I > reinvent those? > It's strange to hear on a file system forum that "you should write your > own file system". :) > > From ZFS viewpoint the only difference here is that I have as much > zpools as disks. Otherwise it's used as a normal file system. > *openzfs <https://openzfs.topicbox.com/latest>* / openzfs-developer / > see discussions <https://openzfs.topicbox.com/groups/developer> + > participants <https://openzfs.topicbox.com/groups/developer/members> + > delivery options > <https://openzfs.topicbox.com/groups/developer/subscription> Permalink > <https://openzfs.topicbox.com/groups/developer/T10533b84f9e1cfc5-M79379c52c02c0b2267f29ced> >
The best way to debug this might be to run this between each import:
vmstat -z | tail +3 | awk -F '[:,] *' 'BEGIN { total=0; cache=0; used=0
} {u = $2 * $4; c = $2 * $5; t = u + c; cache += c; used += u; total +=
t; name=$1; gsub(" ", "_", name); print t, name, u, c} END { print
total, "TOTAL", used, cache } ' | sort -n | perl -a -p -e 'while (($j,
$_) = each(@F)) { 1 while s/^(-?\d+)(\d{3})/$1,$2/; print $_, " "} print
"\n"' | column -t
And now which values are growing. This breaks down each UMA cache and
how much slack it contains.
--
Allan Jude
signature.asc
Description: OpenPGP digital signature
This is a multi-part message in MIME format... ------------=_1562279682-930255-1--
