Re: Kernel Panic of 10.2-RELEASE

Hello, Take a look at this commit: https://github.com/freebsd/freebsd/commit/d99ba5c It might be the issue you're encountering. With kind regards, Daniel On 18 July 2017 18:33:02 CEST, "Stéphane Dupille via freebsd-stable" wrote: >Hello, > >My server is

Re: intel 10gbe nic bug in 10.3 - no carrier

Daniel On 01/24/2017 06:57 PM, Eric Joyner wrote: > On Tue, Jan 10, 2017 at 2:38 AM Daniel Genis <daniel.ge...@gmx.de> wrote: > >> Hello everyone, >> >> we're trying to tackle a rare bug that is very hard to debug. >> >> Our 10.3-RELEASE servers can pan

intel 10gbe nic bug in 10.3 - no carrier

Hello everyone, we're trying to tackle a rare bug that is very hard to debug. Our 10.3-RELEASE servers can panic boot and subsequently can come up without network (2x - no carrier). We've seen this on 10.3-RELEASE-p0 we have never seen this before. root@storage ~ # pciconf -lv | grep -B3

Any chance that r299900 can be merged to releng-10.3 from stable-10 ?

Hello everyone! I'm wondering is there any chance for r299900 (git commit hash d99ba5cdb) to be merged to releng-10.3 ? That error can cause our BSD fileservers to enter a panic and reboot. We're running that exact commit hash on a few servers, and it's been running good for us! We would

Re: zfs recv causes nfs server to throw NFSERR_IO i/o errors

Thank you, that probably is what the doctor ordered! My quick testing shows that it's very likely fixed. Kudos! :-) On 08/05/2016 04:11 PM, Alan Somers wrote: > On Fri, Aug 5, 2016 at 7:22 AM, Daniel Genis <daniel.ge...@gmx.de> wrote: >> Hi everyone, >> >> we've

zfs recv causes nfs server to throw NFSERR_IO i/o errors

Hi everyone, we've been tracing an issue where snapshot replication is causing interruptions for the NFS serivce. The problem is as follows: Every time a zfs recv finishes, there is a chance for the NFS server to return an NFSERR_IO for a GETATTR call. This shows up as input/output errors on

Continuously increasing L2ARC header size

Dear FreeBSD community, We're facing a somewhat odd issue, perhaps similar to what is discussed here: https://forums.freebsd.org/threads/l2arc-degraded.47540/ The issue is that the L2ARC header seems to grow without limit, similar to a memory leak, pressuring more and more memory over time out

Re: Continuously increasing L2ARC header size

of the workload and the time of installation. The mail fileservers were installed much later in comparison. I just wanted to add this, as it maybe very relevant. With kind regards, Daniel On 08/11/2015 04:42 PM, Daniel Genis wrote: Dear FreeBSD community, We're facing a somewhat odd issue

Re: can the l2arc memory leak fix be pulled into 10.1-RELEASE ?

and will update. Appreciate the good product, and the prompt help! With kind regards, Daniel On 06/24/2015 06:38 PM, Mark Felder wrote: On Mon, Jun 22, 2015, at 09:10, Daniel Genis wrote: Hello Everyone, we're currently running 10.1-RELEASE, but are encountering the l2arc memory leak which

can the l2arc memory leak fix be pulled into 10.1-RELEASE ?

Hello Everyone, we're currently running 10.1-RELEASE, but are encountering the l2arc memory leak which got resolved in 10.1-STABLE r274172, maybe we need r275609 also (as discussed here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197164). We are kind of new to FreeBSD, so we're wondering