Date: Sat, 19 Jun 2021 10:39:18 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: =?UTF-8?B?W0J1ZyAyNTY3MTJdIFVGUzoga2VybmVsIHBhbmljOiBmZnNfYmxr?= =?UTF-8?B?ZnJlZV9jZzogZnJlZWluZyBmcmVlIGZyYWcg4oCTIGluIHJlc3BvbnNlIHRv?= =?UTF-8?B?IHBrZy1kZWxldGUoOCkgc29vbiBhZnRlciBsb2dpbg==?= Message-ID: <bug-256712-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256712 Bug ID: 256712 Summary: UFS: kernel panic: ffs_blkfree_cg: freeing free frag = =E2=80=93 in response to pkg-delete(8) soon after login Product: Base System Version: 13.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: grahamperrin@gmail.com I began with a fresh installation of FreeBSD 13.0 to UFS, then (in a nutshe= ll):=20 1. single user mode 2. tunefs -n disable 3. ee /etc/fstab 4. ee /etc/sysctl.conf 5. shutdown -r now 5. an update to the OS 6. shutdown -r now 7. /etc/pkg/FreeBSD.conf set to latest 8. tests for file system resilience.=20 ---- # Device Mountpoint FStype Options Dump Pass# /dev/ada0s1a / ufs rw,sync 1 1 /dev/ada0s1b none swap sw 0 0 ---- kern.filedelay=3D10 kern.dirdelay=3D9 kern.metadelay=3D8 hw.acpi.power_button_state=3D"NONE" ---- Tests typically involved pressing and holding the power button whilst installing packages:=20 * specifically, timing the press for interruption to occur=20 during or immediately after extraction of devel/gdb =E2=80=93 most, if not all, results were OK. Dozens of tests yesterday and = this morning.=20 ---- For just one test, after-effects were remarkable:=20 pkg: sqlite error while executing INSERT INTO files (path, sha256, package_= id) VALUES (?1, ?2, ?3) in file pkgdb.c:1825: database disk image is malformed <https://forums.freebsd.org/threads/80925/>; =E2=80=93 the broken local.sqli= te was no surprise, given the nature of the tests and honestly, I'm not certain that = the breakage was a _direct_ consequence. I mention this incident solely as a po= int of reference; unless advised otherwise, I'll treat it as negligible.=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D For a next round, this morning (with the file system reportedly clean) I _enabled_ soft updates then tested in much the same way =E2=80=93 observing= automated file system checks and repairs at startup time.=20 Shortly after a login, I ran:=20 pkg delete -fy python38 gdb The system crashed. I awaited completion of the dump, suppressed automatic reboot and took a photograph of the backtrace.=20 The round of testing that led to this situation was very brief =E2=80=93 ma= ybe only two or three tests (interruptions) =E2=80=93 so I hope to make things reproduci= ble with not too much difficulty. --=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-256712-227>