Comment # 21 on bug 942940 from Alexander Nolting

Hello thomas,

her my fstab:

/dev/disk/by-id/ata-Samsung_SSD_840_Series_S14GNEAD229172E-part2 / ext4
noatime,acl,user_xattr 1 1
/dev/mapper/cr_home  /home                ext4      
noatime,acl,user_xattr,nofail 0 2
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
# tmpfs                /var/log             tmpfs     
defaults,noatime,mode=0755 0 0
# tmpfs                /tmp                 tmpfs     
defaults,noatime,mode=1777 0 0
# tmpfs                /var/spool           tmpfs     
defaults,noatime,mode=1777 0 0

and crypttab:

cr_home        
/dev/disk/by-id/ata-Samsung_SSD_840_Series_S14GNEAD229172E-part3 none      
none

I've played with systemd only for fstrim. But after the issue came up I
disabled it. With no change to the issue. The other optimizations made were
related to mount /var/log etc... to tmpfs. As you can see this is also disabled
as there were a message from rpm after updating once a time systemd saying that
the folder /var/log/journal couldn't found in /var/log. But this issue must
there for a longer time as my old /var/log folder on the root partition does
also not have this subfolder <-- Note, that this laptop is updated to several
openSUSE distribution over many years with no complete fresh installation at
any time. Also the change from 13.1 to tumbleweed had shown no bigger issue
with had forced my to open a bug report. From that perspective I'm quiet happy
with stability and the qm by the staff working for openSUSE. :)

Alex