Date: Fri, 9 Dec 2016 13:23:34 +0000 From: Steven Hartland <killing@multiplay.co.uk> To: freebsd-stable@freebsd.org Subject: Re: vfs.zfs.vdev.bio_delete_disable - crash while changing on the fly Message-ID: <2fea8732-5980-40e5-f57e-935862145397@multiplay.co.uk> In-Reply-To: <584AADFC.8090700@norma.perm.ru> References: <584AADFC.8090700@norma.perm.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Obviously this shouldn't happen but would need a stack trace to identify the cause. If you want to disable TRIM on ZFS you should really use: vfs.zfs.trim.enabled=0 On 09/12/2016 13:13, Eugene M. Zheganin wrote: > Hi. > > Recently I've encountered the issue with "slow TRIM" and Sandisk SSDs, > so I was told to try to disable TRIM and see what happens (thanks a lot > by the way, that did it). But changing the > vfs.zfs.vdev.bio_delete_disable on the fly can lead to the system crash > with the probability of 50%. Is it just me or is this already known ? If > it's known, why isn't this oid in a read-only list ? > > Thanks. > > P.S. My box tried to dump a core, but after a reboot savecore got > nothing, so you just have to believe me. ;) > > Eugene. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2fea8732-5980-40e5-f57e-935862145397>