Date: Wed, 29 Nov 2023 13:18:57 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 275308] EN tracking issue for potential ZFS data corruption Message-ID: <bug-275308-3630-JIH9OeKhnq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275308-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-275308-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=3D275308 tsuroerusu@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tsuroerusu@gmail.com --- Comment #17 from tsuroerusu@gmail.com --- (In reply to Rob Norris from comment #16) > My advice would to users would be (and has been): > - leave vfs.zfs.bclone_enabled=3D0 For paranoid people, like me, at the level of users when setting up new systems, would it be beneficial to do "zpool create ... -o feature@block_cloning=3Ddisabled" ? Does that provide any benefit over the = sysctl you mentioned? Separately (And I apologize if this is not relevant in this bug report), any thoughts as to whether #15533 ( https://github.com/openzfs/zfs/issues/15533= ), which I got hit by on Linux when running on top of LUKS, is in any way applicable on FreeBSD when running ZFS on top of GELI? I ask since OpenZFS commit bd7a02c was, as far as I can see, not Linux specific and I have a few clients with GELI+ZFS setups. I did notice your vdev_disk rewrite is Linux specific, so I was just curious as to what the situation might be for FreeB= SD? --=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-275308-3630-JIH9OeKhnq>