LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 06-17-2019, 09:57 PM   #1
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, others
Posts: 5,800
Blog Entries: 1

Rep: Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066
discard vs. fstrim.timer with multiboot SSD


The search services don't seem able to connect multi-boot or multiboot with fstrim in any single thread. Has anyone here considered whether discard or timer makes more sense with a bunch of OSes on single SSD systems that get booted to random OSes for random lengths of time? If timer, what period(s) make sense? Discard seems to make more sense to me, but I only just today gave it any thought, while I've been using SSDs for about a year. It took me over 6 months to even face the issue of trimming. Everything I have now is using the defaults, whatever they may be on a mix of Debians and derivatives, Mageia and Fedora, but mostly openSUSE. Most of what I have are upgrades, few fresh installs since migrating off rotating rust, so no instances of fstabs with discard in the options column. Most root filesystems here are on EXT4, none on BTRFS. MBRs here are a mix of legacy and GPT.

Thoughts?
 
Old 06-18-2019, 04:32 PM   #2
wpeckham
LQ Guru
 
Registered: Apr 2010
Location: Continental USA
Distribution: Debian, Ubuntu, RedHat, DSL, Puppy, CentOS, Knoppix, Mint-DE, Sparky, VSIDO, tinycore, Q4OS,Manjaro
Posts: 5,598

Rep: Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691
Mount options only take effect in and during the running of the OS in which they are defined. Multiboot does not make them either more or less valid. Perhaps your purpose would be better served if you refine your question. I am not sure that I understand your objective.
 
Old 06-19-2019, 01:09 AM   #3
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, others
Posts: 5,800

Original Poster
Blog Entries: 1

Rep: Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066
I thought the objective was clear enough: to acquire any available information helpful in choosing among among discard options for numerous filesystems per SSD, all of which get wildly irregular use:
  1. manual discard
  2. automatic discard via fstab
  3. automatic discard via systemd, and if so, what timer setting to use
How the SSD handles sector allocation under the covers, or whether it matters WRT discard methods, so far has been unclear to me.

Last edited by mrmazda; 06-19-2019 at 01:16 AM.
 
Old 06-19-2019, 05:38 AM   #4
wpeckham
LQ Guru
 
Registered: Apr 2010
Location: Continental USA
Distribution: Debian, Ubuntu, RedHat, DSL, Puppy, CentOS, Knoppix, Mint-DE, Sparky, VSIDO, tinycore, Q4OS,Manjaro
Posts: 5,598

Rep: Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691
Fair enough, but my point was that the answers do not depend upon having a single OS, or a multiboot setup.

This is only my opinion based upon my experiences, so YMMV.
I find continuous trim (fstab) a bit of a performance hit. Since a big part of the reason for using it in the first place involves performance that would seem to make that particular automation less than optimal.

A scheduled process seems more optimal for this. A completely manual process may work for you, but only if you are somewhat religious in your routine (as I am). For a laptop or desktop workstation that boots at least weekly and automated on-boot process (systemd can be set that way) seems perfect.

You should consider your work profile in making this decision. How many blocks you write to disk in a day MIGHT make a big difference.

Last edited by wpeckham; 06-19-2019 at 05:40 AM.
 
  


Reply

Tags
filesystem, fstrim, multiboot, partition, timer



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
RHEL 7.6 & OpenSUSE 15: Using TRIM/fstrim - How to extend the life of SSD and prevent SSD from eventually slowing down anthony000 Linux - Newbie 6 06-03-2019 06:26 PM
SSD free space, SSD interrupted fstrim atelszewski Linux - Hardware 2 09-20-2017 06:52 AM
[SOLVED] Running fstrim manually on a swap partition - can it be done? flokofcgulls Slackware 3 05-31-2013 11:58 AM
LXer: JFS File-System Can Now Handle SSD TRIM Discard LXer Syndicated Linux News 4 10-04-2012 06:23 PM
TRIM/discard not working any more for ext4 partition on SSD revinary Linux - Hardware 0 11-15-2011 09:19 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 08:30 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration