• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

SSD's on Linux OS

Carlosinfl

Loves the juice
Joined
Sep 25, 2002
Messages
6,633
It seems SSD's have been around for a minute now and are relatively inexpensive so I picked a pair of Samsung EVO 840's for my machine. My question is what special parameters are required to make sure I'm getting top performance / longevity from my drives when using Ext4 Linux partition table on a 3.4+ kernel? I know Linux sub-section is available but I wanted to ask here as the question centers around how to configure hardware (SSD) for a specific OS (Linux). I am omitting my distribution since I think it shouldn't matter if I use Debian, Arch, RHEL, or any other of the millions of flavors.

Did you guys have to enable TRIM or RELATIME for EXT4 partitions? Did you notice any issues compared to using the same drives w/ another OS? Did you bench mark drive performance on Linux compared to lets say Windows 7 Professional?

Thanks for any info!
 
If you're using an SSD go with BTRFS for a filesystem. It's the only one that supports trim at the moment. Ext4 should work fine on your SSD, but you won't have trim. Also check here for benchmarks
http://www.phoronix.com/
 
If you're using an SSD go with BTRFS for a filesystem. It's the only one that supports trim at the moment. Ext4 should work fine on your SSD, but you won't have trim. Also check here for benchmarks
http://www.phoronix.com/

False. Depends on what kernel you're running.See the above Arch Wiki article for clarification.
 
Ah, interesting. Scratch that statement then. I'd still go with btrfs personally, but I just like btrfs :)
 
Discard and noatime (or relatime) is all I use. It's been pretty much set-and-forget ever since.
 
I have used my Intel G1 80GB SSD for over 4 years of uptime on my linux based htpc (mythtv). At first I used ext4 disabling file and folder update tracking. However for the last ~2 years I have run btrfs + weekly snapshots. I currently have I have 94% life left in the drive after 36969 power on hours.

Code:
jmd0 ~ # smartctl --all /dev/sdb
smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.11.6-gentoo-jmd0] (local build)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Intel X18-M/X25-M G1 SSDs
Device Model:     INTEL SSDSA2MH080G1GC
Serial Number:    CVEM848601V3080DGN
LU WWN Device Id: 5 001517 95878760b
Firmware Version: 045C8820
User Capacity:    80,026,361,856 bytes [80.0 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA/ATAPI-7 T13/1532D revision 1
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Sat Oct 26 19:58:52 2013 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== 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:      (  32) The self-test routine was interrupted
         by the host with a hard or soft reset.
Total time to complete Offline
data collection:   (    1) seconds.
Offline data collection
capabilities:     (0x75) SMART execute Offline immediate.
         No Auto Offline data collection support.
         Abort Offline collection upon new
         command.
         No Offline surface scan supported.
         Self-test supported.
         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:    (   5) minutes.
Conveyance self-test routine
recommended polling time:    (   1) minutes.

SMART Attributes Data Structure revision number: 5
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  3 Spin_Up_Time            0x0000   100   000   000    Old_age   Offline      -       0
  4 Start_Stop_Count        0x0000   100   000   000    Old_age   Offline      -       0
  5 Reallocated_Sector_Ct   0x0002   100   100   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0002   100   100   000    Old_age   Always       -       36969
 12 Power_Cycle_Count       0x0002   100   100   000    Old_age   Always       -       453
192 Unsafe_Shutdown_Count   0x0002   100   100   000    Old_age   Always       -       282
232 Available_Reservd_Space 0x0003   100   100   010    Pre-fail  Always       -       0
233 Media_Wearout_Indicator 0x0002   094   094   000    Old_age   Always       -       0
225 Host_Writes_32MiB       0x0000   199   199   000    Old_age   Offline      -       216847
226 Intel_Internal          0x0002   255   000   000    Old_age   Always       -       4294967295
227 Intel_Internal          0x0002   000   000   000    Old_age   Always       -       281474976710655
228 Intel_Internal          0x0002   000   000   000    Old_age   Always       -       4294967295
 
Back
Top