Date: Mon, 09 Mar 2020 00:36:03 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 244685] gjournal kernel panic with vfs.write_behind=0 Message-ID: <bug-244685-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244685 Bug ID: 244685 Summary: gjournal kernel panic with vfs.write_behind=3D0 Product: Base System Version: 12.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: spy@spy.zp.ua Trying to copy huge file to gjournaled filesystem causes reboot just after a few seconds, if vfs.write_behind=3D0, and works fine with vfs.write_behind= =3D1 Tested in such conditions under 12.1-RELEASE and 11.3-RELEASE: #/dev/gpt/ada0-data - 200Gb on SATA disk #/dev/gpt/nvd0-log - 1Gb on NVME disk gjournal label -vh /dev/gpt/ada0-data /dev/gpt/nvd0-log mount -o "async,atime=3Doff" /dev/gpt/ada0-data.journal /dst mount -o "async,atime=3Doff" /dev/gpt/nvd0-data /src dd if=3D/dev/random of=3D/src/60gb bs=3D1m count=3D60000 sysctl vfs.write_behind=3D0 cp /src/60gb /dst/ I didn't test it neither with slow /src device, nor with fast /dst device. With bigger log device, we can get panic later, and with huge enough log de= vice (I tried 30Gb), it can work fine without reboots. --=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-244685-227>