Date: Wed, 23 Sep 2015 09:59:54 -0700 From: Tim Gustafson <tjg@ucsc.edu> To: Michael Fuckner <michael@fuckner.net> Cc: freebsd-fs@freebsd.org Subject: Re: Switching from MFI to MRSAS Message-ID: <CAPyBAS5TyBYjOp6wRSkpOy35m%2BcQVLn3MNFS3=y2wWYtpjobQw@mail.gmail.com> In-Reply-To: <5602D9E8.2090903@fuckner.net> References: <CAPyBAS4-oRjrybxu81nPO1Xb0WPdYzJRoEZ3t8zjNUrxFsiZpw@mail.gmail.com> <56023C15.7080007@fuckner.net> <CAPyBAS6p_=Ld6yiis00L3GxCFgq7JwUXkvg=mzni3ZHHEC1Z3Q@mail.gmail.com> <5602D9E8.2090903@fuckner.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> OK, haven't done this before, perhaps this works, but... you are replacing a > raid driver with another raid driver, so probably TRIM will not work either. The mrsas driver man page says that it reports the disks as "da0", "da1" and so on, and the man pages about TRIM support all say that it works with "ada" and "da" drives. So, I was hoping that the change in driver technology would enable the TRIM command to work. I suppose I could update device.hints and loader.conf as describe, reboot, and if the system doesn't come back up, just boot off a thumb drive and re-edit those files back to their defaults... -- Tim Gustafson tjg@ucsc.edu 831-459-5354 Baskin Engineering, Room 313A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyBAS5TyBYjOp6wRSkpOy35m%2BcQVLn3MNFS3=y2wWYtpjobQw>