**Question one: Should I change
“UUID=3c4938af-c70d-42a9-abb3-91bced2eecc6 /var/lib/libvirt/images btrfs subvol=@/var/lib/libvirt/images 0 0”
and the other /var files to
“tmpfs /var//lib/libvirt/images tmpfs defaults,noatime,mode=1777 0 0” ?
Question two: I’ve added the following to my /etc/rc.d/boot.local file to create a filestructure in /var for /log,
for dir in apparmor apt cups dist-upgrade fsck gdm installer samba unattended-upgrades ;
if ! -e /var/log/$dir ] ; then
Should I be doing this for /spool and /tmp as well? What about the other directories mentioned in Question one? Is this necessary?
**Question three: **How are most people configing this on their SSDs? TIA
A word to the wise, you have your opinion, just like everyone else, we can all argue to the cows come home about the features etc of whichever filesystem, Desktop etc is better or not. If you want to make a change to the defaults, the forum here is not the place, either the Factory mailing list or a feature request and get some traction to changing it.
If wanting to help, then I suggest to keep things on a technical level (we have chat and soapbox) and guide/help the user with their specific issue if you can. Thanks
Thanks Malcolm. I’ve been using Samsung SSDs, both 250gb, one is an 840 the other is an 850. The 840 I’ve been using daily since 2013 and was starting to develop weird issues, (freezing, garbled text) that I’d attributed to my getting lazy in recent years and just installing the stock openSuse with no special tweaks for SSDs, (no swappiness adjusting, no tmpfs, etc). I’d figured that the openSuse developer lords had incorporated SSD adjustments (fstrim, etc) as standard in the stock distros, but had not seen mention of these changes anywhere. My recent problems w/the Samsung 840 had made me question this assumption.
Firmware on both is up to date. From what you have said, I gather that you are of the opinion that it is not needed to establish /tmp and /var in RAM via tmpfs? Correct? Thanks for the useful and thoughtful responses.
I have never worry about it these days, but that’s just me
I have five laptops here with various OCZ’s, a Crucial and a SanDisk SSD(s). When using ext4 on my oldest one (OCZ Agility 60GB) a number of years ago I did a few extra tweaks, but now just run the defaults, on average my systems are writing 6~7GB to the SSD a day, well below the manufacturers specs… the one above is at 38,770 power on hours and SSD_LIfe_Left is at 99% (has been like that for awhile)… There has been some discussion on the forum about the btrfs defaults, but I don’t see any indication of any of my SSD’s failing in the near future…
Here is an example of the garbled text that I am getting from the Samsung 840 drive, http://i279.photobucket.com/albums/kk152/portsample/garbledText_zpsejunfmcw.png
I’ve moved the drive to machines with similar hardware configs, and have totally wiped the drive using the Samsung bootable exe available from Samsung Magician and then totally openSuse 42.3 with standard SSD optimizations…still I get freeze-ups and this weird malformed text. Note that all of the capital "D"s and lower case"p"s are affected. This machine with the Samsung 850 installed runs fine. I think the drive is toast even though SMART drive calls it “good”. Go figure. Anyone here ever seen this before?
Warranty on the 840 is only 3 yrs, Samsung Magician (on the WinOS partition) says 4.2 tb written. Not sure how to get total power-on hours. I have done a total erase and reformat, so these metrics may no longer be available.
No need to re-install.
Just open up YaST > Partitioner and re-define whatever mount points you wish to change.
To the @OP,
Be aware that when doing a web browser download and possibly other types of downloads (except torrent), as your file downloads a temporary file is created in /tmp and when completed only then is moved to a destination (typically &USER/Downloads). This means that if you place /tmp in RAM, you need that much RAM… to accommodate all your running processes <and> the possibly massive file(s) if for instance you’re downloading DVD ISOs.
So, unless you’re able to re-direct various application behaviors, it’s generally not advisable to mount /tmp in RAM.
It should be enough that SSD read performance is generally pretty darn fast (writes can be slow, but is typically not that critical particularly if write-backs are implemented which is often the case).
A word of caution when using other distro HowTos… a lot on the second link is already done in openSUSE OTB with scheduler udev rules etc (openSUSE recommend deadline for SSD’s which they even dispute in the article saying to use deadline and not noop), so verify first by checking the parameters listed. If not sure post away in the forum
On Sun 20 Aug 2017 08:36:01 PM CDT, malcolmlewis wrote:
> Fantastic btrfs incest mode
A word to the wise, you have your opinion, just like everyone else, we
can all argue to the cows come home about the features etc of whichever
filesystem, Desktop etc is better or not. If you want to make a change
to the defaults, the forum here is not the place, either the Factory
mailing list or a feature request and get some traction to changing it.
If wanting to help, then I suggest to keep things on a technical level
(we have chat and soapbox) and guide/help the user with their specific
issue if you can. Thanks
So a clarification to the word used, since user V_idocq uses google
translate as English is not the first language…
The word in Italian was “incasinato”, the way I see it is the sentence should have been;
“Fantastic btrfs messed up mode”
But again the point still stands that technical help is the primary
purpose in these forums, opinions etc in the other forum areas
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.79-18.26-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Hmmmm…not sure about the 245 sudden power-offs. That does seem a bit high…however, I started using this drive in late December 2013…that’s approximately 180 weeks. That’s more than 1 sudden power-off per week. That does seem high. I do have VMWare Workstation installed on this SSD. The virtual hard drives are kept on a spinning HD.