Disabling Journaling on new SSD

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
Post Reply
second.exodous
Level 1
Level 1
Posts: 31
Joined: Sun Nov 07, 2010 3:27 pm

Disabling Journaling on new SSD

Post by second.exodous » Wed May 08, 2019 10:37 am

I just got a new SSD and made new EXT4 partitions for / and /home and want to disable journaling. My main drive is sda and the new one is sdd(not ssd, confusing)

Anyway, I run this command:

Code: Select all

tune2fs -O ^has_journal /dev/sdd
and get this:

Code: Select all

tune2fs 1.44.1 (24-Mar-2018)
tune2fs: Permission denied while trying to open /dev/sdd
Couldn't find valid filesystem superblock.
Am I doing anything wrong? I've never disabled journaling before. I probably should have done it on the SSD I'm running on right now.

Thanx,
Stan

User avatar
WharfRat
Level 21
Level 21
Posts: 12934
Joined: Thu Apr 07, 2011 8:15 pm

Re: Disabling Journaling on new SSD

Post by WharfRat » Wed May 08, 2019 10:57 am

I wouldn't recommend disabling the journal, but first of all you have a permission problem so sudo would be needed and secondly the filesystem is on a partition - not /dev/sdd.
ImageImage

second.exodous
Level 1
Level 1
Posts: 31
Joined: Sun Nov 07, 2010 3:27 pm

Re: Disabling Journaling on new SSD

Post by second.exodous » Wed May 08, 2019 11:10 am

I read a SSD doesn't need journaling and it should be disabled, it just wears out the read/write life of the SSD.

So I'll use sudo but what should exactly should I write?

gm10
Level 17
Level 17
Posts: 7412
Joined: Thu Jun 21, 2018 5:11 pm

Re: Disabling Journaling on new SSD

Post by gm10 » Wed May 08, 2019 11:12 am

second.exodous wrote:
Wed May 08, 2019 11:10 am
I read a SSD doesn't need journaling
Nothing needs journaling but if you crash in the middle of a write operation (and yes, even SSDs aren't fast enough to complete all operations instantly) then you'll be happy you had the journal. I'll echo WharfRat, not recommended to disable that.

User avatar
Pjotr
Level 21
Level 21
Posts: 12590
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: Disabling Journaling on new SSD

Post by Pjotr » Wed May 08, 2019 12:00 pm

As said: don't disable journaling.

If you wish to reduce the write actions on your SSD in other ways, this is how:
https://easylinuxtipsproject.blogspot.com/p/ssd.html
Tip: 10 things to do after installing Linux Mint 19.1 Tessa
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.

jchelpau
Level 3
Level 3
Posts: 100
Joined: Mon Mar 25, 2019 11:19 pm
Location: Australia
Contact:

Re: Disabling Journaling on new SSD

Post by jchelpau » Wed May 08, 2019 9:16 pm

There's not much reason to worry about write limits on modern SSDs.

User avatar
smurphos
Level 11
Level 11
Posts: 3716
Joined: Fri Sep 05, 2014 12:18 am
Location: Britisher
Contact:

Re: Disabling Journaling on new SSD

Post by smurphos » Thu May 09, 2019 2:11 am

jchelpau wrote:
Wed May 08, 2019 9:16 pm
Theres not much reason to worry about write limits on modern SSDs.
+1

My SSD was installed in September 18 - it's management utility confirms that in its 1034 hours of uptime to date I've written 1.74 TB of data, which represents 2% of it's rated write life-span.

Albeit 'rated life-spans' obviously need to be taken with a pinch of salt by my reckoning even if I ran it 24/7 with the same average write rate for that period I've got 6 years before it hits it's rated write life-span.

If I carry on using it in my current usage pattern - (up-time circa 20% of real-time) I've got roughly 30 years of the rated lifespan to go. I'll probably die before my SSD does... :roll: :mrgreen:
For custom Nemo actions, useful scripts for the Cinnamon desktop, and Cinnamox themes visit my Github pages.

rene
Level 10
Level 10
Posts: 3301
Joined: Sun Mar 27, 2016 6:58 pm

Re: Disabling Journaling on new SSD

Post by rene » Thu May 09, 2019 5:56 am

smurphos wrote:
Thu May 09, 2019 2:11 am
My SSD was installed in September 18 - it's management utility confirms that in its 1034 hours of uptime to date I've written 1.74 TB of data, which represents 2% of it's rated write life-span.
Moreover, said rated lifespan is on modern SSDs much too conservative. It's fairly dependent on what size SSD but in the case of a 250G one, say, you're under 1% of practical lifespan at worst, probably under 0,25% of eventual "really, really dead" lifespan at best --- and if it's larger than 250G we even have to divide those numbers down due to wear-leveling having lots more blocks to spread writes over.

I.e., https://techreport.com/review/27909/the ... e-all-dead. Also note that's an article from 2015. Admittedly growing levels in MLC may negatively affect things again -- but at the same time aforementioned growth in size offsets effects again in the consumer context. That is, it's really about time to stop worrying about longevity of modern SSDs; without mechanical wear (well, some controllers get quite hot....) it'll in fact be quickly better than for HDD.

User avatar
thx-1138
Level 7
Level 7
Posts: 1803
Joined: Fri Mar 10, 2017 12:15 pm
Location: Athens, Greece

Re: Disabling Journaling on new SSD

Post by thx-1138 » Thu May 09, 2019 6:56 am

smurphos wrote:
Thu May 09, 2019 2:11 am
...................................
If I carry on using it in my current usage pattern - (up-time circa 20% of real-time) I've got roughly 30 years of the rated lifespan to go.
...thank you for posting this, as the 'paranoia' on the net in regards to ssd disks falling out somehow by...writing lots of data is truly unbelievable.
Also a very simplistic & rudimentary way, say in case no management utility exists for a certain ssd model...
sudo tune2fs -l /dev/sda2 | grep Lifetime
Divide per total months, multiply x 12...a relatively decent estimation of the per year average writes that someone does.
Here it's about 2.8Tb per year, meaning...exactly as you said.
Ie. unless say someone runs a heavy database or has turned his/her machine into a dedicated 24/7 torrent seedbox...
smurphos wrote:
Thu May 09, 2019 2:11 am
...................................
...I'll probably die before my SSD does... :roll: :mrgreen:
...brrrr - i surely hope we'll still be around :P
However, somehow the very opposite also comes to mind - not 30, but...merely 10-15 yrs ago: say back in 2004-2005 or so,
just how much widespread SSDs were / accessible to the wide masses? (let alone even mentioning technologies like NVME...)
Ie. by...2034-2035, what the usual / common daily storage will be in contrast...assuming we will also still live then as well... :lol:

rene
Level 10
Level 10
Posts: 3301
Joined: Sun Mar 27, 2016 6:58 pm

Re: Disabling Journaling on new SSD

Post by rene » Thu May 09, 2019 8:14 am

thx-1138 wrote:
Thu May 09, 2019 6:56 am
Also a very simplistic & rudimentary way, say in case no management utility exists for a certain ssd model [ ... ]
Also note sudo smartctl -a /dev/sda. I.e., for a Samsumg 840 EVO here:

Code: Select all

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-48-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
[ ... ]
Sector Size:      512 bytes logical/physical
[ ... ]
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
[ ... ]
  9 Power_On_Hours          0x0032   098   098   000    Old_age   Always       -       9010
[ ... ]
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       18677239533
Multiply latter by sector size for byte count.

Pippin
Level 4
Level 4
Posts: 229
Joined: Wed Dec 13, 2017 11:14 am
Location: NL/DE/TH

Re: Disabling Journaling on new SSD

Post by Pippin » Thu May 09, 2019 8:40 am

Although difficult to predict, hardware failure, as in chips/resistors/capacitors/etc. or solder joints, going bad !
So one can calculate until..... if physical components fail, it's dead.
"I'm not in this world to live up your expectations, neither are you here to live up to mine.”
F.P. & P.T.

rene
Level 10
Level 10
Posts: 3301
Joined: Sun Mar 27, 2016 6:58 pm

Re: Disabling Journaling on new SSD

Post by rene » Thu May 09, 2019 8:43 am

Hence the temperature remark indeed, but otherwise there's not a lot to fail on an SSD -- certainly compared to an HDD.

User avatar
thx-1138
Level 7
Level 7
Posts: 1803
Joined: Fri Mar 10, 2017 12:15 pm
Location: Athens, Greece

Re: Disabling Journaling on new SSD

Post by thx-1138 » Thu May 09, 2019 12:45 pm

rene wrote:
Thu May 09, 2019 8:14 am
Multiply latter by sector size for byte count.
...excellent tip rene - thanks :)

md419
Level 2
Level 2
Posts: 84
Joined: Thu Sep 22, 2011 2:34 pm

Re: Disabling Journaling on new SSD

Post by md419 » Sat May 11, 2019 9:52 am

As others above have pointed out, disabling journaling is unnecessary.

I have an older Samsung SSD that I'm sure will outlive the life of the laptop it's currently in ...

Code: Select all

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.18.0-18-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Samsung based SSDs
Device Model:     Samsung SSD 850 EVO 500GB
Serial Number:    (removed intentionally)
LU WWN Device Id: 5 002538 d409be9ba
Firmware Version: EMT02B6Q
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4c
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat May 11 09:37:38 2019 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, NOT FROZEN [SEC1]

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x53) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 265) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  5 Reallocated_Sector_Ct   PO--CK   100   100   010    -    0
  9 Power_On_Hours          -O--CK   098   098   000    -    7370
 12 Power_Cycle_Count       -O--CK   097   097   000    -    2239
177 Wear_Leveling_Count     PO--C-   099   099   000    -    9
179 Used_Rsvd_Blk_Cnt_Tot   PO--C-   100   100   010    -    0
181 Program_Fail_Cnt_Total  -O--CK   100   100   010    -    0
182 Erase_Fail_Count_Total  -O--CK   100   100   010    -    0
183 Runtime_Bad_Block       PO--C-   100   100   010    -    0
187 Uncorrectable_Error_Cnt -O--CK   100   100   000    -    0
190 Airflow_Temperature_Cel -O--CK   070   051   000    -    30
195 ECC_Error_Rate          -O-RC-   200   200   000    -    0
199 CRC_Error_Count         -OSRCK   100   100   000    -    0
235 POR_Recovery_Count      -O--C-   099   099   000    -    66
241 Total_LBAs_Written      -O--CK   099   099   000    -    11769826101
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      1  Comprehensive SMART error log
0x03       GPL     R/O      1  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  SATA NCQ Queued Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x13       GPL     R/O      1  SATA NCQ Send and Receive log
0x30       GPL,SL  R/O      9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa1           SL  VS      16  Device vendor specific log
0xa5           SL  VS      16  Device vendor specific log
0xce           SL  VS      16  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      7370         -
# 2  Short offline       Completed without error       00%      5657         -
# 3  Short offline       Completed without error       00%      4558         -
# 4  Extended offline    Aborted by host               90%      4558         -
# 5  Short offline       Completed without error       00%      2848         -
# 6  Short offline       Completed without error       00%       282         -
# 7  Extended offline    Aborted by host               90%       282         -
# 8  Short offline       Completed without error       00%         0         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
  255        0    65535  Read_scanning was never started
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version:                  3
SCT Version (vendor specific):       256 (0x0100)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    26 Celsius
Power Cycle Min/Max Temperature:     20/26 Celsius
Lifetime    Min/Max Temperature:     17/45 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        10 minutes
Min/Max recommended Temperature:      0/70 Celsius
Min/Max Temperature Limit:            0/70 Celsius
Temperature History Size (Index):    128 (55)

Index    Estimated Time   Temperature Celsius
  56    2019-05-10 12:20    25  ******
  57    2019-05-10 12:30    26  *******
 ...    ..(  2 skipped).    ..  *******
  60    2019-05-10 13:00    26  *******
  61    2019-05-10 13:10     ?  -
  62    2019-05-10 13:20    26  *******
  63    2019-05-10 13:30    29  **********
  64    2019-05-10 13:40    26  *******
  65    2019-05-10 13:50    27  ********
 ...    ..(  9 skipped).    ..  ********
  75    2019-05-10 15:30    27  ********
  76    2019-05-10 15:40    28  *********
  77    2019-05-10 15:50    28  *********
  78    2019-05-10 16:00    28  *********
  79    2019-05-10 16:10    27  ********
  80    2019-05-10 16:20    27  ********
  81    2019-05-10 16:30    27  ********
  82    2019-05-10 16:40    28  *********
  83    2019-05-10 16:50     ?  -
  84    2019-05-10 17:00    23  ****
  85    2019-05-10 17:10    24  *****
  86    2019-05-10 17:20    26  *******
  87    2019-05-10 17:30    25  ******
  88    2019-05-10 17:40    25  ******
  89    2019-05-10 17:50    24  *****
  90    2019-05-10 18:00    24  *****
  91    2019-05-10 18:10    25  ******
  92    2019-05-10 18:20    26  *******
  93    2019-05-10 18:30    24  *****
  94    2019-05-10 18:40    24  *****
  95    2019-05-10 18:50    24  *****
  96    2019-05-10 19:00    25  ******
  97    2019-05-10 19:10    24  *****
 ...    ..(  4 skipped).    ..  *****
 102    2019-05-10 20:00    24  *****
 103    2019-05-10 20:10    25  ******
 104    2019-05-10 20:20    24  *****
 105    2019-05-10 20:30    25  ******
 106    2019-05-10 20:40    24  *****
 ...    ..(  5 skipped).    ..  *****
 112    2019-05-10 21:40    24  *****
 113    2019-05-10 21:50    25  ******
 114    2019-05-10 22:00    24  *****
 115    2019-05-10 22:10    24  *****
 116    2019-05-10 22:20    25  ******
 117    2019-05-10 22:30    24  *****
 118    2019-05-10 22:40    24  *****
 119    2019-05-10 22:50    24  *****
 120    2019-05-10 23:00    26  *******
 121    2019-05-10 23:10    24  *****
 122    2019-05-10 23:20    24  *****
 123    2019-05-10 23:30    24  *****
 124    2019-05-10 23:40    25  ******
 125    2019-05-10 23:50    25  ******
 126    2019-05-11 00:00    24  *****
 127    2019-05-11 00:10    25  ******
 ...    ..(  2 skipped).    ..  ******
   2    2019-05-11 00:40    25  ******
   3    2019-05-11 00:50    24  *****
   4    2019-05-11 01:00    24  *****
   5    2019-05-11 01:10    24  *****
   6    2019-05-11 01:20    25  ******
 ...    ..(  2 skipped).    ..  ******
   9    2019-05-11 01:50    25  ******
  10    2019-05-11 02:00    26  *******
 ...    ..( 16 skipped).    ..  *******
  27    2019-05-11 04:50    26  *******
  28    2019-05-11 05:00    25  ******
  29    2019-05-11 05:10    26  *******
 ...    ..(  8 skipped).    ..  *******
  38    2019-05-11 06:40    26  *******
  39    2019-05-11 06:50    25  ******
 ...    ..(  6 skipped).    ..  ******
  46    2019-05-11 08:00    25  ******
  47    2019-05-11 08:10     ?  -
  48    2019-05-11 08:20    20  *
  49    2019-05-11 08:30    22  ***
  50    2019-05-11 08:40    23  ****
  51    2019-05-11 08:50    24  *****
  52    2019-05-11 09:00    25  ******
  53    2019-05-11 09:10    25  ******
  54    2019-05-11 09:20    25  ******
  55    2019-05-11 09:30    26  *******

SCT Error Recovery Control:
           Read: Disabled
          Write: Disabled

Device Statistics (GP/SMART Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2         2309  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            4  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0010  2            0  R_ERR response for host-to-device data FIS, non-CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x0013  2            0  R_ERR response for host-to-device non-data FIS, non-CRC 

Post Reply

Return to “Newbie Questions”