Date: Wed, 23 Sep 2015 17:32:03 -0400 From: Ryan Stone <rysto32@gmail.com> To: Tim Gustafson <tjg@ucsc.edu> Cc: Michael Fuckner <michael@fuckner.net>, "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: Switching from MFI to MRSAS Message-ID: <CAFMmRNwMv6ZAWhyBiSwufh1cCxxBYz5aOt4s1_0_MvOR8JZrMA@mail.gmail.com> In-Reply-To: <CAPyBAS5TyBYjOp6wRSkpOy35m%2BcQVLn3MNFS3=y2wWYtpjobQw@mail.gmail.com> References: <CAPyBAS4-oRjrybxu81nPO1Xb0WPdYzJRoEZ3t8zjNUrxFsiZpw@mail.gmail.com> <56023C15.7080007@fuckner.net> <CAPyBAS6p_=Ld6yiis00L3GxCFgq7JwUXkvg=mzni3ZHHEC1Z3Q@mail.gmail.com> <5602D9E8.2090903@fuckner.net> <CAPyBAS5TyBYjOp6wRSkpOy35m%2BcQVLn3MNFS3=y2wWYtpjobQw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 23, 2015 at 12:59 PM, Tim Gustafson <tjg@ucsc.edu> wrote: > 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... > The mrsas driver is interesting. Your RAID volumes show up as da0, da1, etc, but they really shouldn't. I'm doubtful that TRIM will work here because the drives are not truly directly attached, even though the mrsas driver is misleading the kernel into thinking that they are. You can always give a try, though.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNwMv6ZAWhyBiSwufh1cCxxBYz5aOt4s1_0_MvOR8JZrMA>