Re: tunefs(8) changes don't stick
- Reply: Graham Perrin : "Re: tunefs(8) changes don't stick"
- In reply to: Graham Perrin : "Re: tunefs(8) changes don't stick"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 18 Oct 2021 19:30:27 UTC
On Mon, Oct 18, 2021 at 11:44 AM Graham Perrin <grahamperrin@gmail.com> wrote: > On 18/10/2021 19:13, Kevin Oberman 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 > > > What's the overview? > > tunefs -p … > # tunefs -p /dev/nvd0p3 tunefs: POSIX.1e ACLs: (-a) disabled tunefs: NFSv4 ACLs: (-N) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled tunefs: soft update journaling: (-j) disabled tunefs: gjournal: (-J) disabled tunefs: trim: (-t) disabled tunefs: maximum blocks per file in a cylinder group: (-e) 4096 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: space to hold for metadata blocks: (-k) 6400 tunefs: optimization preference: (-o) time tunefs: volume label: (-L) FreeBSD -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683