Date: Mon, 18 Oct 2021 12:28:59 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: "freebsd-questions@freebsd.org" <questions@freebsd.org> Subject: Re: tunefs(8) changes don't stick Message-ID: <CAN6yY1vYzVfUm%2BsKwa1vcG4B-ZwQFKAqEv3w2vHfUvfurWU96A@mail.gmail.com> In-Reply-To: <CAN6yY1so_ztpy0v%2BxRuzHX_WXC22AAD=CCXZ6M35%2BYGurGTcSg@mail.gmail.com> References: <CAN6yY1so_ztpy0v%2BxRuzHX_WXC22AAD=CCXZ6M35%2BYGurGTcSg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
A small update. As soon as I make the vilum R/W, it reverts to both the old trim and volume name values. I am assuming that I want TRIM enabled on an SSD volume. I do get a message when enabling TRIM of "issue TRIM command". Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Mon, Oct 18, 2021 at 11:13 AM Kevin Oberman <rkoberman@gmail.com> wrote: > I have a UFS file system on a GPT formatted SSD. I assume that trim is a > desirable flag, but, even though I have tried to set it and it appears set > after the 'tunefs -t', after my next boot it reverts to disabled. > Similarly, changing the volume name (tunefs -L name) also reverts to its > old value. > > Any idea what could cause this? Should I consider the -A option? The > warning on that is quite strong, but for those changes, I don't see an > issue with it. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vYzVfUm%2BsKwa1vcG4B-ZwQFKAqEv3w2vHfUvfurWU96A>