[Bug 229745] ahcich: CAM status: Command timeout

2020-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745 --- Comment #47 from sec --- (In reply to Warner Losh from comment #46) Hi, >From my expierence: 1) I didn't have this issue until I've updated to 11.2 IIRC (that was almost one year ago) 2) First I replaced my drives to new ones - issue w

[Bug 245619] BROKEN NFS SERVER OR MIDDLEWARE after resume

2020-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245619 Bug ID: 245619 Summary: BROKEN NFS SERVER OR MIDDLEWARE after resume Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severit

[Bug 245619] BROKEN NFS SERVER OR MIDDLEWARE after resume

2020-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245619 --- Comment #1 from Conrad Meyer --- The message indicates you got a GETATTR response for a file you didn't request. In this case the NFS request was for "inode" 0x4, but you got back a GETATTR response for 0x2. There are some NFS WAN cac

[Bug 245619] BROKEN NFS SERVER OR MIDDLEWARE after resume

2020-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245619 --- Comment #2 from Conrad Meyer --- (In this instance, it's obviously not a middleware issue, but it might be a client or server bug.) -- You are receiving this mail because: You are the assignee for the bug.

[Bug 245619] BROKEN NFS SERVER OR MIDDLEWARE after resume

2020-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245619 --- Comment #3 from Edward Tomasz Napierala --- I suspect (a shot in the dark) is that it might be related to NFS reconnecting to the server - it only happens immediately after a long (think - over the night) suspend, so any TCP connection

[Bug 245625] close_range(2) is not audited; closefrom(2) was

2020-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245625 Bug ID: 245625 Summary: close_range(2) is not audited; closefrom(2) was Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Seve

[Bug 245625] close_range(2) is not audited; closefrom(2) was

2020-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245625 Kyle Evans changed: What|Removed |Added CC||lw...@freebsd.org Assignee|

[Bug 245627] jail rc script stops jails not defined in jail.conf

2020-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245627 Bug ID: 245627 Summary: jail rc script stops jails not defined in jail.conf Product: Base System Version: 12.1-RELEASE Hardware: Any OS: Any Status: New

[Bug 245627] jail rc script stops jails not defined in jail.conf

2020-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245627 Kyle Evans changed: What|Removed |Added Assignee|b...@freebsd.org|j...@freebsd.org CC|