<---- template headericclude ----->
Fstab. Data=ordered for SSD or m.2 nvme drives
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 8 of 8
  1. #1
    Join Date
    Jun 2005
    Location
    Montreal, Québec, Canada
    Posts
    9,105
    Mentioned
    23 Post(s)
    Tagged
    0 Thread(s)

    Fstab. Data=ordered for SSD or m.2 nvme drives

    Some distributions, during their installation process, after the defaults parameter add the captioned expression.
    Eg.

    UUID=xxxxx /home/myhome ext4 \ defaults,data=ordered 0 2

    Is it advised to use data=ordered when fstrim exists and can be scheduled to run?
    Leslie in Montreal

    Interesting web sites list
    http://forums.fedoraforum.org/showth...40#post1697840
    We get too soon old, and too late smart!

  2. #2
    Join Date
    Mar 2006
    Posts
    1,803
    Mentioned
    21 Post(s)
    Tagged
    0 Thread(s)

    Re: Fstab. Data=ordered for SSD or m.2 nvme drives

    I use these options
    defaults,discard,noatime,data=writeback
    except I exclude "data=writeback" for the boot or root partition depending on which boot is installed on.
    jbkt23
    Thinkpads Depends on era T23 - X2xx
    AMD & Intel Boxes

  3. #3
    Join Date
    Jun 2005
    Location
    Montreal, Québec, Canada
    Posts
    9,105
    Mentioned
    23 Post(s)
    Tagged
    0 Thread(s)

    Re: Fstab. Data=ordered for SSD or m.2 nvme drives

    The research I completed from many sources definitely recommends not using discard.
    They also recommend replacing noatime. With relatime.
    The first avoidance is for extending the life of the SSD or M.2 drive. The second, for SSDs and other, for performance.

    I did substantial research and followed the advice I discovered.

    Now, I did wonder about data=ordered as that is what SUSE Tumbleweed installer adds to SSD devices when not formatted as xfs formatted partitions.
    Last edited by lsatenstein; 15th September 2019 at 08:13 PM.
    Leslie in Montreal

    Interesting web sites list
    http://forums.fedoraforum.org/showth...40#post1697840
    We get too soon old, and too late smart!

  4. #4
    Join Date
    Jun 2004
    Location
    Maryland, US
    Posts
    11,404
    Mentioned
    87 Post(s)
    Tagged
    0 Thread(s)

    Re: Fstab. Data=ordered for SSD or m.2 nvme drives

    There's no such mount option as "relative", it's spelled "relatime"

    see "man mount"


    relatime
    Update inode access times relative to modify or change time. Access time is only
    updated if the previous access time was earlier than the current modify or change
    time. (Similar to noatime, but it doesn't break mutt or other applications that need
    to know if a file has been read since the last time it was modified.)

    Since Linux 2.6.30, the kernel defaults to the behavior provided by this option
    (unless noatime was specified), and the strictatime option is required to obtain tra‐
    ditional semantics. In addition, since Linux 2.6.30, the file's last access time is
    always updated if it is more than 1 day old.

    norelatime
    Do not use the relatime feature. See also the strictatime mount option.

  5. #5
    Join Date
    Jun 2005
    Location
    Montreal, Québec, Canada
    Posts
    9,105
    Mentioned
    23 Post(s)
    Tagged
    0 Thread(s)

    Re: Fstab. Data=ordered for SSD or m.2 nvme drives

    Quote Originally Posted by marko
    There's no such mount option as "relative", it's spelled "relatime"

    see "man mount"
    Marco
    My android cellphone seems to change words after I proof read my post and I hit send. I happen to be visiting my grandchild and put the laptop aside,. I will edit and correct Android's damage ��
    Leslie in Montreal

    Interesting web sites list
    http://forums.fedoraforum.org/showth...40#post1697840
    We get too soon old, and too late smart!

  6. #6
    Join Date
    Mar 2006
    Posts
    1,803
    Mentioned
    21 Post(s)
    Tagged
    0 Thread(s)

    Re: Fstab. Data=ordered for SSD or m.2 nvme drives

    Leslie,

    My options are based on Stevea's guide on this forum from 5 years ago. My SSD's that are on 24/7 are about that old otherwise they are on laptops that are on a couple hours a day.
    According to the ext man page "data=ordered" is the default mode for ext3 and ext4 file systems, so why is Suse adding this to the fstab options? The other option besides writeback is "journal", I don't have an opinion on which to use but there is very little discussion on these in regards to SSD's. L. Torvalds thinks using "date=writeback" is absurd. So I guess I'm on the wrong side of the knowledgeable curve.
    jbkt23
    Thinkpads Depends on era T23 - X2xx
    AMD & Intel Boxes

  7. #7
    Join Date
    Jun 2005
    Location
    Montreal, Québec, Canada
    Posts
    9,105
    Mentioned
    23 Post(s)
    Tagged
    0 Thread(s)

    Re: Fstab. Data=ordered for SSD or m.2 nvme drives

    Hi jbk. I googled fstab data=ordered, and the fallout from the search was an article about the negative impact of using discard. One article stated that it was deprecated.

    I wrote my own fstrim timer function. Currently I have it set up for 21 days.
    The problem with using the fstimer system service has to do with unmounted drives. Trim only works with mounted partitions. Some of my partitions are only mounted on need.
    Leslie in Montreal

    Interesting web sites list
    http://forums.fedoraforum.org/showth...40#post1697840
    We get too soon old, and too late smart!

  8. #8
    Join Date
    Mar 2006
    Posts
    1,803
    Mentioned
    21 Post(s)
    Tagged
    0 Thread(s)

    Re: Fstab. Data=ordered for SSD or m.2 nvme drives

    Leslie,

    Seems we have gotten off topic, my fault, but still and interesting discussion. There seems to be very little discussion on data=ordered. You are right there is a bit of discussion "to discard" or "not to discard" that is the question. By enabling the discard option I'm sacrificing some performance by forcing a trim on erase of data. But, to get the benefit of trimming w/o using discard I have to write a script because trimming is not automated by the device controller, but is a function of a file system call. That is due to the fact that whole file system trimming can't be done when IO operations are occurring. It is further complicated by the fact that certain disk controllers, will not allow trimming if a certain quantity of blocks can be freed. So for now I'm going to leave the discard option enabled and take a slight performance hit. Per "man ext4" on my F29 system discard has yet to be deprecated, or maybe it was "man mount".

    A link to a discussion on discard: https://patrick-nagel.net/blog/archives/337
    Last edited by jbkt23; 17th September 2019 at 03:42 AM.
    jbkt23
    Thinkpads Depends on era T23 - X2xx
    AMD & Intel Boxes

Similar Threads

  1. [Solution]Is there an hddtemp fork that reads NVMe drives?
    By dd_wizard in forum Guides & Solutions (Not For Questions)
    Replies: 17
    Last Post: 30th January 2022, 07:41 PM
  2. Issue installing F29 Silverblue on mix of NVME & physical drives?
    By joncr in forum Installation, Upgrades and Live Media
    Replies: 2
    Last Post: 6th December 2018, 01:17 PM
  3. iostat svctm and %busy numbers are wrong for NVME drives
    By bobx001 in forum Servers & Networking
    Replies: 2
    Last Post: 25th June 2018, 05:57 PM
  4. Turning off ordered data mode
    By vacuumpower in forum Security and Privacy
    Replies: 7
    Last Post: 9th December 2009, 11:23 PM
  5. FC5 DVD drives not in fstab
    By Qwagmire in forum Hardware
    Replies: 10
    Last Post: 8th April 2006, 07:21 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
[[template footer(Guest)]]