On Thu, 3 Nov 2016 00:18, John Andersen wrote:

Thinking of replacing my Drive with a SSD. Probably happen about the time Leap 42.2 comes out.

Any words of wisdom here? I'm thinking I'll do the same drill I normally do, Fresh install, then copy /home a and /data over into similar partition sizes that I have before.

What to look out for? Any problem with a couple xfs/Luks partitions on the SSD? Brands?

Words is (non-)wisdom(tm): Many wearleveling optimisations from the linux side will not (fully) work with encrypted fs or encrypted partitions, e.g. TRIM. Hint 1: Go for a drive with a high TBW / drive-writes count. Hint 2: overprovisioning (leaving free non-partitioned space) helps. Hint 3: Warranty: 10 years cost (extra) money, 5 years is good sense, 3 years is (very) low. It could be that a MLC drive wins out against TLC one. Further Info startpoint: https://en.wikipedia.org/wiki/Flash_memory#Write_endurance https://en.wikipedia.org/wiki/Multi-level_cell https://en.wikipedia.org/wiki/Write_amplification#Over-provisioning Do not go below 240 GB, as the value per money is (much) worse below that. In the enterprise (datacenter) class I've had little to no problem with the Samsung and Intel drives of the last 3 years, but time will tell - as warranty begins to run out on some of them now. Early Intel was uneven. In the professional (desktop/soho-server) class (10 years warranty), well, no drop out on any drives mounted since 2012, but, see above, time will tell, all on warranty still. In the semi-pro (desktop/soho-server) class (5 years warranty), about 5 per 1000 dropout rate before end-of-warranty (time or TBW reached), seams to be spread all over the manufactureres and the products. In the (IMHO) home-use-only class (less than 5 years warranty, less than 60 Drives-writes TBW), it's a very mixed bag, some charges are very good, but the ones before and after could be crap (same manufacturer, same product). *shrugs* You get wat you pay for. 20 bucks more for a drive with 5 years instead of a 3 year warranty is simply good sense and better sleep. About the same as the tires on your car. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wed, Nov 2, 2016 at 7:18 PM, John Andersen wrote:

Thinking of replacing my Drive with a SSD. Probably happen about the time Leap 42.2 comes out.

Any words of wisdom here? I'm thinking I'll do the same drill I normally do, Fresh install, then copy /home a and /data over into similar partition sizes that I have before.

What to look out for? Any problem with a couple xfs/Luks partitions on the SSD? Brands?

Technologies? is a better question. For a lightly loaded PC, most any AHCI SSD will do great. I've mostly been buying Samsung SSDs with a SATA interface. For a state of the art experience that can handle a multi-threaded load like a server can throw at it, you want a NVMe SSD. Those don't have SATA ports, they are made to run at native PCIe speeds. Meaning fast as hell. Here's a year old article about one that was just released back then: http://arstechnica.com/gadgets/2015/10/950-pro-review-samsungs-first-pcie-m-... I have a Asus X.99 Deluxe MB that has a NVMe SSD connector directly on the MB. The SSD plugs into that vertically. (Unlike the picture in the article where the SSD is laying flat.) I have a Samsung PM951 (MZ-VLV1280) 128GB (I bought it to test functionality with, so the cheapest I could find.) I've been running Leap 42.2 (beta => RC1) on that pair since I bought the SSD (in June I think). I have had zero issues with doing so, but I mostly tinker with that machine, so I don't have any meaningful benchmarks. One new thing to learn is the drive is NOT /dev/sda It is /dev/nvme* nvme => Non-Volatile Memory Express nvme0 => The first NVMe SSD nvme0n1 => the first namespace of the first NVMe SSD nvme0n1p1 => The first partition on the first namespace of the NVMe SSD If your MB (like most) doesn't have a connector, you can buy a PCIe adapter for $25 or so dollars. Here's one example: https://www.amazon.com/Ableconn-PEXM2-SSD-NGFF-Express-Adapter/dp/B017JGVTAM/ref=sr_1_2?ie=UTF8&qid=1478131341&sr=8-2&keywords=nvme+pcie+adapter I haven't used an adapter, so no pros/cons from me. I assume they work with older MBs and CPUs. Alright, a quick performance test with my hardware. I was doing some 32-bit openSUSE 13.1 compatibility testing, so I openSUSE 13.1 boot CD booted at the moment. I did: time dd if=/dev/nvme0n1 of=/dev/zero bs=1M count=10000 It took 15.5 seconds to read 10GB., or 675 MB/sec. Again, that's with a 3-year old 32-bit kernel. Booting back to 64-bit Leap 42.2 RC1 9.8 seconds, or 1.1 GB/sec I'm actually surprised the 64-bit speed is that low. HTH Greg Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, 03 Nov 2016, John Andersen wrote:

Thinking of replacing my Drive with a SSD. Probably happen about the time Leap 42.2 comes out.

Any words of wisdom here? I'm thinking I'll do the same drill I normally do, Fresh install, then copy /home a and /data over into similar partition sizes that I have before.

What to look out for? Any problem with a couple xfs/Luks partitions on the SSD? Brands?

-- After all is said and done, more is said than done.

I'm running Leap 42.2 (RC1) with a SATA Samsung SSD 850 EVO 250GB (AMD Phenom II X6 1090T, 8GB, Nvidia GTX 650 Ti, Seagate ST2000DM001). I'm using ext4 for root (I briefly toyed with btrfs, but backing up it's sub-partition structure proved difficult to retrofit to my simple rsync based backup regime). Btrfs is supposed to better support SSD's (but I gather its not a big deal). I did a fresh install of 42.2 (RC1) and re-applied all my usual settings and packages. It all went smoothly. There seems to be some confusion on the web about Samsung and trim support. My dmesg output contains: [ 3.267504] ata1.00: disabling queued TRIM support [ 3.267511] ata1.00: ATA-9: Samsung SSD 850 EVO 250GB, EMT02B6Q, max UDMA/133 I think this is mainly for older drives, which mine is not. I've decided not to worry about it. I may look into using fstrim (man 8 fstrim) but I'm not sure whether this too might be an issue. The 42.2 kernel build seems to have correctly picked to use the deadline scheduler for the SSD (only): cat /sys/block/sda/queue/scheduler noop [deadline] cfq I decided to put noatime in mount entry in /etc/fstab to reduce writes (some say this is no longer really necessary). My previous OCZ SSD died after 5 years. I've read that SSD's can fail without warning. In my case, the OS just started errorring like crazy and crashed. There was no possibility of recovering anything as the failed drive was no longer recognised. So it would be a good idea to keep backups on other media. I backup the OS to both online and offline hard drives, so I lose a day to a week depending. My SSD failed just after installing Tumbleweed in a spare partition, so perhaps all the new activity pushed the writes over some limit. I still keep /home on a hard drive - being into photography makes SSD to expensive for user space. Cheers. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Hello

Thinking of replacing my Drive with a SSD. Probably happen about the time Leap 42.2 comes out. Any problem with a couple xfs/Luks partitions on the SSD? Brands?

I just ordered a Crucial 525 MX 300 CT525MX300SSD1 SSD last week to install on an old laptop when 42.2 comes out. ### Crucial 525 MX 300 CT525MX300SSD1 Power Consumption Active Read/Write (Average in Watts): ? Note : The power consumption info appears to be a well garded secret. I can only find a reference to 0.075W Power Consumption Active Read/Write Idle (Watts) 0.075? Size: 525 Prix: 119,90 € at amazon.fr Prix/Go: 0.23 € Reliability (TBF) (Million hours): 1.5 Endurance (Total bytes written To): 220 Expected Lifetime writing 10 Go a day 10 : 61.7 years* Waranty 3 Years/160TBW Débit réel Mo/s hdparm -t /dev/sda ? - I have not installed it yet The following quote came off the Web somewhere: "The Crucial MX300 has an endurance of 220TBW, meaning you can write 220 terabytes of data to the drive before it becomes unreliable. To put this in perspective, if you write 50GB of data per day every day to the drive, it will take you some 12 years to wear it out. " [*] The following are my calculations Endurance : 220 To If I make 10GB hot writes per day (I have no idea but whatever), the expected drive life should be approximately (220*1024)/(10*365) = 61.7 years until total drive fault. ### I have also been using a Crucial M550 CT512M550SSD1 - 512 Go SSD on an old Thinkpad since Oct 2014. The machine only runsTumbleweed and it has a Luks encrypted ext4 data partition and I have never experienced any problems. The times I have re installed Tumbleweed, the installation process detects the encypted partition and just asks for the password / key. As a side note, the Crucial M550 CT512M550SSD1 SSD drive cost me almost twice as much € as the new CT525MX300SSD1 and its endurance (Total bytes written To) is only 70 To (compared to 220) so things have definitely improved ! ### I also love Samsung 850 PRO SSD and I have been using one in my main machine for the last 2 years with zero problems and regets. ### Samsung 850 PRO 1TB MZ-7KE1TOBW Power Consumption Active Read/Write (Average in Watts) 3.3W/3.0W Power Consumption Active Read/Write Idle (Watts) 0.4Watt Size: 1024 Prix: 540 € (on sale in Oct 2014); now 469 € Prix/Go: 0,53 € when I bought it (now 0,46 €) Reliability (TBF) (Million hours): 2.0 Endurance (Total bytes written To): 300 Expected Lifetime writing 10 Go a day 10 : 84,2 years* Waranty 10 Years/150TBW [*] The following are my calculations Endurance : 300 To # If I make 10GB hot writes per day (I have no idea but whatever), the expected drive life should be approximately (300*1024)/(10*365) = 84,2 years until total drive fault. My speed specs on a 5 year old motherboard follow : time dd if=/dev/sda1 of=/dev/zero bs=1M count=10000 10000+0 records in 10000+0 records out 10485760000 bytes (10 GB) copied, 18.5969 s, 564 MB/s real 0m18.600s user 0m0.020s sys 0m5.076s # hdparm -t /dev/sda1 /dev/sda1: Timing buffered disk reads: 1616 MB in 3.00 seconds = 538.66 MB/sec Regards James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org