Date: Fri, 12 Feb 2021 09:00:27 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 253158] Panic: snapacct_ufs2: bad block - Non-suJ mksnap_ffs(8) crash Message-ID: <bug-253158-3630-vMeSDf7ZMu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-253158-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-253158-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253158 --- Comment #9 from Harald Schmalzbauer <bugzilla.freebsd@omnilan.de> --- Thank you very much for further analysis and fix. Unfortunately, this seems to introduce a new problem: /sbin/mksnap_ffs /.snap/.test2 /usr/sbin/fstyp /.snap/.test2 Repdiducable panic: Fatal trap 12: page fault while in kernel mode current process: fstyp #7 ... uiomove_fromphys+ #8 ... vn_io_fault_uiomove+ #9 ... ffs_read+ #10 ... VOP_READ_APV+ #11 ... vn_read+ #12 ... vn_io_doio+ #13 ... vn_io_fault1+ #14 ... vn_io_fault+ #15 ... dofileread+ #16 ... sys_read+ #17 ... amd64_syscall+ Unfortunately I can't test on debug environment currently, the crash happens with produtcion deployment tests without serial console, su just trinscribe= d a stacktrace snippet. Thanks, -harry --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-253158-3630-vMeSDf7ZMu>