edillmann

Hi, I just take a look on some servers we manage, and I get the same error on each off these, zdb -mM rpool return with space map refcount mismatch:...

@sempervictus running zdb -mc on one of these pools give me the following result : ``` ...... leaked space: vdev 0, offset 0x17dff41600, size 62464 leaked space: vdev 0, offset...

@kernelOfTruth I confirm to have the same behaviour with master, I also run zdb -e mc on an fresh created and exported pool with the same results : ``` leaked...

@sempervictus @kernelOfTruth did you use #2129 in your patch stack ? I just remove it and it seem's to cleanup things.

@behlendorf I did the test on the same idle pool **zdb #2129 -mc rpool** Metaslabs: vdev 0 metaslabs 174 offset spacemap free --------------- ------------------- --------------- ------------- metaslab 0 offset 0...

Hi, I have the same problem, did you get any success on this ? Regards, Eric

@pjd Hi, is there still any activity on this, as this feature would be a great enhancement to openzfs ? Many thanks, Eric

Hi `go version 1.10` / no docker `grayproxy -in udp://0.0.0.0:12201 -out tcp://10.0.10.27:12201 -dataDir=/var/tmp` without any message flowing through give high cpu `grayproxy -in udp://0.0.0.0:12201 -out tcp://10.0.10.27:12201` does not show this...