Dear Andriy, FreeBSD community, Thank you for your suggestion, so we will turn off the L2ARC and will report if the issue persist or not. For now the test server rebooted with L2ARC turned off and there's no allocations done in l2arc_feed_thread according to dtrace hook you provided.
Let's imagine the situation, we found l2arc_feed_thread allocations is the cause, what shall our next step ? The feedback from us will be here within few days (can't reproduce faster) > on 06/01/2014 13:14 Vladimir Sharun said the following: > > Dear Andriy and FreeBSD community, > > > > I got the few minutes run for this dtrace hook; here's the output for 15 > > minutes run: > > > > http://pastebin.com/pKm9kLwa > > > > Does it explain something ? > > The following makes me suspect a problem with L2ARC compression code. > > zfs.ko`l2arc_feed_thread+0x7d9 > kernel`fork_exit+0x9a > kernel`0xffffffff8069ad6e > 95131 > > I am not sure if the buffers are leaked somehow or if they are actually in > use. > It's one of the very few places where data buffers are allocated without > charging ARC. In all other places it's quite easy to match allocations and > deallocations. But in L2ARC it is not obvious that all buffers get freed or > when that happens. _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"