On 2017-04-28 17:42, Andriy Gapon wrote:
On 28/04/2017 14:56, Michael Jung wrote:
I have mad the requested change..
< size, NULL, NULL, ZIO_TYPE_FREE, ZIO_PRIORITY_NOW,
BP_GET_PSIZE(bp), NULL, NULL, ZIO_TYPE_FREE,
Yes, that's the change that I had in mind.
I was a little bit confused by the order of the original and modified
As to the pool size:
[root@bsd11 /usr/home/mikej]# zpool list
NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH
tank 199G 143G 55.9G - 85% 71% 1.00x ONLINE -
I should have also mentioned that besides poudriere running a build,
removing old logs - There was some 43G of old logs files that were in
of being removed.
So, given that the panic was in the freeing path, you were probably low
pool space back when those log files were created. I mean that the
are typically created when a pool is very fragmented.
I will hammer the box with and report back first of the week whether
re-occurs or not.
Please also try removing those old files again too.
Running zpool scrub afterwards could be a good idea too.
Thank you again!
I am happy to report that the system no longer panics. As requested I
the remaining logs (34G worth) and punished the file system as hard as I
A scrub of the pool completed without error
Will the change be committed or do I need to open a PR?
Please let me know if I can supply additional information or if there
further tests you would like me to perform.
Thanks again for you prompt reply and apparent solution.
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"