[Bug 261886] ZFS pool over iSCSI: not available after reebot

2022-02-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261886

Bug ID: 261886
   Summary: ZFS pool over iSCSI: not available after reebot
   Product: Base System
   Version: 13.0-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: artem.mikhai...@gmail.com

Hi

There is an iscsi share 'test' (TrueNAS). 
There is an iscsi initiator (13-RELEASE)
There is zfs pool 'test' created at 13-RELEASE on iscsi share test'

Pool 'test' does not survie after reboot. It requres to perform 'zpool import
-a' after each reboot

Checked 12.2-RELEASE as initiator. It works ok. Pool suvives after reboot and
listed in 'zpool list'

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 261233] Frequent kernel panics during disk access after upgrading from 12.2-RELEASE-p7 to 12.2-p12 or 12.3 on i386

2022-02-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261233

Yann C.  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED

--- Comment #10 from Yann C.  ---
Updating to the latests 12.3 with the patch included in Bug 261338 fixes the
issue. I'm going to cancel this ticket

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 261889] [PATCH] ucred.9: fix typo

2022-02-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261889

Bug ID: 261889
   Summary: [PATCH] ucred.9: fix typo
   Product: Documentation
   Version: Latest
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: Manual Pages
  Assignee: b...@freebsd.org
  Reporter: johan.jans...@iki.fi
CC: d...@freebsd.org

Created attachment 231757
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=231757&action=edit
patch

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 261889] [PATCH] ucred.9: fix typo

2022-02-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261889

johan.jans...@iki.fi  changed:

   What|Removed |Added

   Severity|Affects Many People |Affects Only Me

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 260406] pfctl: Cannot allocate memory (after a time)

2022-02-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406

Jean-Claude MICHOT  changed:

   What|Removed |Added

 CC||j...@michot.fr

--- Comment #67 from Jean-Claude MICHOT  ---

Same problem here with 'pfctl: Cannot allocate memory.', it's reported by
fail2ban 
(anyway same for blacklistd).

2022-02-09 19:34:30,354 fail2ban.utils  [64280]: ERROR   8021b2730 --
exec: pfctl -a f2b/ssh-pf -t f2b-ssh-pf -T add 45.9.20.25
2022-02-09 19:34:30,354 fail2ban.utils  [64280]: ERROR   8021b2730 --
stderr: 'pfctl: Cannot allocate memory.'
2022-02-09 19:34:30,354 fail2ban.utils  [64280]: ERROR   8021b2730 --
killed with signal 127 (return code: 255)

# freebsd-version -uk
13.0-RELEASE-p4
13.0-RELEASE-p4

"pfctl -T del IP" still usable, but add new rule is impossible until reboot :(


# vmstat -m | grep -E 'pf|Size'
 Type InUse MemUse Requests  Size(s)
pfs_nodes20 8K   20  384
  pfs_vncache 1   128K1
 pfil11 1K   11  64,128
  tcpfunc 1 1K1  64
  pf_temp 0 0K   55  32
  pf_hash 5 11524K5  2048
 pf_ifnet19 7K  171  256,2048
  pf_osfp  1191   123K 3573  64,128
  pf_rule   269   181K  341  128,1024
 pf_table1122K24200  2048

# vmstat -z | grep pf
pf mtags:48,  0,   0,  84,  55,   0,   0,   0
pf tags:104,  0,   0,   0,   0,   0,   0,   0
pf states:  296, 10,  40,2703, 4287549,   0,  
0,2135254
pf state keys:   88,  0,  58,6106, 4592659,   0,  
0,2280096
pf source nodes:136,  1,   0,   0,   0,   0,   0,   0
pf table entry counters: 64,  0,   0,   0, 200,   0,   0,  
0
pf table entries:   160, 20, 152,  48, 488,7420,   0,   0
pf frags:   248,  0,   0,  16,  15,   0,   0,   0
pf frag entries: 40,   5000,   0, 101,  40,   0,   0,   0
pf state scrubs: 40,  0,   0,   0,   0,   0,   0,   0

# sysctl -a | grep net.pf
net.pf.rule_tag_hashsize: 128
net.pf.request_maxcount: 65535
net.pf.source_nodes_hashsize: 32768
net.pf.states_hashsize: 131072

# pfctl -si
Status: Enabled for 93 days 22:56:25  Debug: Urgent

State Table  Total Rate
  current entries  840
  searches  5992674224  738.2/s
  inserts  42883560.5/s
  removals 42875160.5/s
Counters
  match 1169829912  144.1/s
  bad-offset 00.0/s
  fragment   00.0/s
  short  00.0/s
  normalize 870.0/s
  memory 00.0/s
  bad-timestamp  00.0/s
  congestion 00.0/s
  ip-option  20.0/s
  proto-cksum00.0/s
  state-mismatch  12060.0/s
  state-insert   00.0/s
  state-limit00.0/s
  src-limit  00.0/s
  synproxy   00.0/s
  map-failed 00.0/s

# top -b | head -8
last pid: 20669;  load averages:  0.08,  0.11,  0.09  up 93+22:59:55   
18:11:49
160 processes: 1 running, 158 sleeping, 1 zombie
CPU:  0.3% user,  0.0% nice,  0.1% system,  0.0% interrupt, 99.6% idle
Mem: 90M Active, 829M Inact, 506M Laundry, 59G Wired, 2173M Free
ARC: 52G Total, 28G MFU, 22G MRU, 3368K Anon, 281M Header, 1419M Other
 48G Compressed, 61G Uncompressed, 1.27:1 Ratio
Swap: 46G Total, 1939M Used, 44G Free, 4% Inuse

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 261889] [PATCH] ucred.9: fix typo

2022-02-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261889

--- Comment #1 from commit-h...@freebsd.org ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=d4b0fa45dc1531fafb1f3f1a1956056597a4722c

commit d4b0fa45dc1531fafb1f3f1a1956056597a4722c
Author: Johan Jansson 
AuthorDate: 2022-02-11 16:46:37 +
Commit: Konstantin Belousov 
CommitDate: 2022-02-11 18:10:19 +

ucred.9: fix typo

PR: 261889
MFC after:  3 days

 share/man/man9/ucred.9 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 261886] ZFS pool over iSCSI: not available after reebot

2022-02-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261886

Andrew Fyfe  changed:

   What|Removed |Added

 CC||and...@neptune-one.net

--- Comment #1 from Andrew Fyfe  ---
13.0 changed how non-root pools are mounted. You need zfs_enable=YES in rc.conf
for /etc/rc.d/zpool to run, which imports all previously imported non-root
pools at boot.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 261895] drm-kmod: Console screen goes black when loading drm-kmod driver

2022-02-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261895

Bug ID: 261895
   Summary: drm-kmod: Console screen goes black when loading
drm-kmod driver
   Product: Base System
   Version: Unspecified
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: sblachm...@gmail.com

If you are running the sc console on a drm-kmod-supported graphics card and
load the according drm-kmod driver (in my test computer it is the radeonkms
driver), the console screen disappears, goes black.
Not yet tested on i915kms and amdgpu, but I think the behavior might be the
same.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 261895] drm-kmod: Console screen disappears, goes black when loading drm-kmod driver

2022-02-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261895

Stefan B.  changed:

   What|Removed |Added

Summary|drm-kmod: Console screen|drm-kmod: Console screen
   |goes black when loading |disappears, goes black when
   |drm-kmod driver |loading drm-kmod driver
 CC||sblachm...@gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.