September 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] WD Green AV HD: rsync read errors mapping
by Felix Miata 28 Sep '17

28 Sep '17

Running OS 13.1: 2017/08/27 03:38:05 [2308] building file list 2017/08/27 03:38:08 [2308] .d..t...... movie/ 2017/08/27 03:40:09 [2308] >f+++++++++ movie/bigBang0113-201312151700GDMX10wd.ts 2017/08/27 03:40:09 [2308] rsync: read errors mapping "/disks/esata/movie/bigBang0113-201312151700GDMX10wd.ts": Input/output error (5) 2017/08/27 03:42:30 [2308] >f+++++++++ movie/bigBang0220-201310061730GDMX10wd.ts 2017/08/27 03:42:30 [2308] rsync: read errors mapping "/disks/esata/movie/bigBang0220-201310061730GDMX10wd.ts": Input/output error (5) ... 2017/08/27 06:15:56 [2308] >f+++++++++ movie/CLO/closer0406-201306270230GDMX09.ts 2017/08/27 06:15:56 [2308] rsync: read errors mapping "/disks/esata/movie/CLO/closer0406-201306270230GDMX09.ts": Input/output error (5) ... 2017/08/27 06:24:14 [2308] >f+++++++++ movie/CLO/closer0411-201307180130GDMX09.ts 2017/08/27 06:24:14 [2308] rsync: read errors mapping "/disks/esata/movie/CLO/closer0411-201307180130GDMX09.ts": Input/output error (5) ... Above is from rsync log. Before interrupting the rsync and restarting it I logged output from hdparm and smartctl: http://fm.no-ip.com/Tmp/Hardware/Disk/hdpd-201207-fi965azbme-wd20eurs-os131… Similar logs from the first WD Green AV disk, first WD I ever bought: http://fm.no-ip.com/Tmp/Hardware/Disk/smart-wdAVGP3200AVVS.txt The smaller 320GB device I consider functional but unreliable, removed from SD DVR service shortly after the warranty expired and the DVR began producing inexplicable errors. The larger (disk of of current interest) has been in a satellite receiver that runs on a variation of Mips Linux Dreambox FOSSware using a 3.92 kernel, resulting in original creation of the files that error'd. I was able to delete the 4 uncopyable files, then restore them from backup. Smartctl -x reports from my few other WD disks all seem to have identical Reallocated_Sector_Ct, 200 200 140 Reallocated_Event_Count, 200 200 0 Current_Pending_Sector, 200 200 0 Offline_Uncorrectable 100 253 0 except for 200 173 0 on the bad 320 for current pending. Can anyone suggest what most likely caused the 4 files to be repeatedly uncopyable? Driver error or other error in the Dreambox software maybe? Before the 320 AV and the 2TB AV I had never ever purchased a WD disk, due to miserable experiences with used WD HDs that had come into my possession over the years. I was Quantum user for as long as it lasted, eventually switching to Seagate after nearly as bad experiences with Toshiba and Maxtor. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

13 57

[opensuse] About relatime and lazytime
by Carlos E. R. 28 Sep '17

28 Sep '17

Hi, relatively recently, "lazytime" has been added as the default for mounts - from man mount: lazytime Only update times (atime, mtime, ctime) on the in-memory version of the file inode. This mount option significantly reduces writes to the inode table for workloads that perform frequent random writes to preallocated files. The on-disk timestamps are updated only when: - the inode needs to be updated for some change unrelated to file timestamps - the application employs fsync(2), syncfs(2), or sync(2) - an undeleted inode is evicted from memory - more than 24 hours have passed since the i- node was written to disk. I understand that using this option (which is the default) supersedes using "relatime". However, I noticed that most mounts, not all, are using both options: > Telcontar:~ # mount | grep relatime | grep lazytime > /dev/sdd2 on /data/storage_d type xfs (rw,relatime,lazytime,attr2,inode64,noquota) > /dev/sdb8 on /opt type xfs (rw,relatime,lazytime,attr2,inode64,noquota) > /dev/sdb10 on /data/storage_b type xfs (rw,relatime,lazytime,attr2,inode64,noquota) > /dev/sda13 on /data/storage_a type xfs (rw,relatime,lazytime,attr2,inode64,noquota) > /dev/sdc13 on /var/spool/news type reiserfs (rw,relatime,lazytime,user_xattr,acl) > /dev/sda12 on /data/vmware type xfs (rw,relatime,lazytime,attr2,inode64,noquota) > /dev/sdc14 on /data/homedvl type reiserfs (rw,relatime,lazytime,user_xattr,acl) > /dev/sdc7 on /usr/local type reiserfs (rw,relatime,lazytime,user_xattr,acl) > /dev/sdc12 on /usr/gamedata type reiserfs (rw,relatime,lazytime,user_xattr,acl) > /dev/sdc6 on /usr/src type reiserfs (rw,relatime,lazytime,user_xattr,acl) > /dev/sdc16 on /data/storage_c type xfs (rw,relatime,lazytime,attr2,inode64,noquota) > /dev/sdc5 on /home_aux type xfs (rw,relatime,lazytime,attr2,inode64,noquota) > /dev/sdc8 on /home1 type xfs (rw,relatime,lazytime,attr2,inode64,noquota) > /dev/md0 on /data/raid type xfs (rw,relatime,lazytime,attr2,inode64,logbsize=128k,sunit=256,swidth=512,noquota) > /dev/mapper/cr_cripta on /data/cripta type xfs (rw,relatime,lazytime,attr2,inode64,noquota) > /dev/sda7 on /other/test_a1 type reiserfs (rw,relatime,lazytime,user_xattr,acl) > Telcontar:~ # Mounts that only use relatime: > Telcontar:~ # mount | grep relatime | grep -v lazytime > sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) > proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) > securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) > devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) > cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) > pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) > cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) > cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) > cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) > cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) > cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) > cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) > cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) > cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) > cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) > cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) > configfs on /sys/kernel/config type configfs (rw,relatime) > /dev/sde5 on / type ext4 (rw,relatime,data=ordered) > mqueue on /dev/mqueue type mqueue (rw,relatime) > debugfs on /sys/kernel/debug type debugfs (rw,relatime) > sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) > hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) > systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=35,pgrp=1,timeout=0,minproto=5,maxproto=5,direct) > nfsd on /proc/fs/nfsd type nfsd (rw,relatime) > /dev/sde4 on /boot type ext2 (rw,relatime,block_validity,barrier,user_xattr,acl) > /dev/sdc17 on /home type ext4 (rw,relatime,data=ordered) > binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime) > tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=817444k,mode=700) > tmpfs on /var/run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=817444k,mode=700) > tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=817444k,mode=700,uid=1000,gid=100) > tmpfs on /var/run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=817444k,mode=700,uid=1000,gid=100) > gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100) > gvfsd-fuse on /var/run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100) > fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) > Telcontar:~ # Ie, ext4 parttions use only relatime, and non real disk partitions. xfs and reiserfs use both relatime and lazytime. It is not my doing: > Telcontar:~ # grep relatime /etc/fstab > # default is "relatime", no need to add it (or atime,nodiratime) > #/dev/mapper/cr_storage_e /data/test xfs nofail,relatime,noauto 1 5 > Telcontar:~ # relatime Update inode access times relative to mod- ify or change time. Access time is only updated if the previous access time was earlier than the current modify or change time. (Similar to noatime, but it doesn't break mutt or other applications that need to know if a file has been read since the last time it was modified.) Since Linux 2.6.30, the kernel defaults to the behavior provided by this option (unless noatime was specified), and the strictatime option is required to obtain traditional semantics. In addition, since Linux 2.6.30, the file's last access time is always updated if it is more than 1 day old. Should I use "norelatime" manually on fstab entries? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

3 11

[opensuse] rkhunter: update not working?
by Markus Egg 27 Sep '17

27 Sep '17

I tried to do the usual rkhunter --update with some older version version 1.4.0 on an older machine, but it is stuck and never returns. "Checking rkhunter version..." is also stuck http://rkhunter.sourceforge.net/ also seems to be down: "It's not just you! rkhunter.sourceforge.net looks down from here." [ http://downforeveryoneorjustme.com/rkhunter.sourceforge.net ] What is going on there? BR ME -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Strange disk activity
by Carlos E. R. 27 Sep '17

27 Sep '17

Hi, I noticed in the graph of disk activity in GKrellM that there was some constant but intermittent activity on /dev/sda. Like this: __|__|__|__|__|__|__|__|__|__|__|__|__|__| It suddenly occurred to me that with GKrellM one can display a graph per partition! So I activated graphs for each one in /dev/sda and found the culprit: /dev/sda7. What do I have there? Well, nothing: Telcontar:~ # mount | grep sda7 /dev/sda7 on /other/test_a1 type reiserfs (rw,relatime,lazytime, user_xattr,acl) Telcontar:~ # It is a test partition of another system, nothing is active there: Telcontar:~ # cat /other/test_a1/etc/os-release NAME=openSUSE VERSION = 12.1 (Asparagus) VERSION_ID="12.1" PRETTY_NAME="openSUSE 12.1 (Asparagus) (x86_64)" ID=opensuse Telcontar:~ # I umounted it and the activity disappeared. Mounted it again and it kept silent. What was it? How can I find out the next time what is reading there? I see a similar intermitent activity on other partitions of disk /dev/sdc, on these partitions: /dev/sdc6 /dev/sdc7 /dev/sdc12 /dev/sdc14 /dev/sdc17 Telcontar:~ # mount | grep "sdc6\|sdc7\|sdc12\|sdc14\|sdc17" /dev/sdc17 on /home type ext4 (rw,relatime,data=ordered) /dev/sdc14 on /data/homedvl type reiserfs (rw,relatime,lazytime, user_xattr,acl) /dev/sdc7 on /usr/local type reiserfs (rw,relatime,lazytime, user_xattr,acl) /dev/sdc12 on /usr/gamedata type reiserfs (rw,relatime,lazytime, user_xattr,acl) /dev/sdc6 on /usr/src type reiserfs (rw,relatime,lazytime, user_xattr,acl) Telcontar:~ # So yes, it affects most of my reiserfs partitions (/var/spool/news is not affected). What is going on? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

3 4

[opensuse] Leap 42.3 MIME Types in Dolphin
by Roger Oberholtzer 27 Sep '17

27 Sep '17

On my system, all files that do not have an explicit MIME type are listed in Dolphin as Type "Python File (no console)". This includes files with names like: cis.txt xx.repo noExtension The mime type it shows in the Properties->General->FileTypeOptions is text/plain. So that part is okay. But when listing a name for this, "Python File (no console)" is used. Anyone else see this? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] SUSE Linux turns 25: From business distro leader to cloud power | ZDNet
by James Knott 26 Sep '17

26 Sep '17

"SUSE, one of the oldest Linux and open-source businesses, celebrated its 25th birthday while setting its eyes on its future in the cloud and software-defined infrastructure." http://www.zdnet.com/article/suse-linux-at-25/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] HD docking station
by Istvan Gabor 26 Sep '17

26 Sep '17

Hello: Does such thing work with openSUSE / linux? https://www.amazon.com/dp/B073H2HLRK I think it should work as a regular USB 3/2 device. What to look for when buying some? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 8

[opensuse] xrandr info HDMI-1 disconnected
by C. Brouerius van Nidek 26 Sep '17

26 Sep '17

After an interesting read about the inner working of xrandr I started reading the manpage. Got the version of my xrandr and got further info about my system. And then I was lost in a swell of info and possibilities. My problem with monitors is following: I am using as my main monitor a Philips 196V3L, 18,5" 13766x768. For movies and such I would like to use my television set with a bigger screen via HDMI. The TV has one HDMI plug which is connected with a box from the TV provider. If I disconnect the tv from the tv box and plug it in on my motherboard I can use HDMI as my second monitor. That is not feasible for daily use. I found myself a HDMI cable with one HDMI connector and on the other end three colored (green, blue and red) video plugs. When I plug this cable into the HDMI plug of the motherboard and the three colored video plugs int the TV set I expected to receive a signal on the TV set. The television set is only showing the input "component" with these three plugs inserted. With xrandr I read HDMI-1 and -2 disconnected. Also DP1 and 2 are not connected. How can I force a connection with the HDMI cable and would that change anything? -- opensuse:tumbleweed:20170913 Qt: 5.9.1 KDE Frameworks: 5.37.0 kf5-config: 1.0 KDE Plasma: 5.10.5 plasmashell 5.10.5 Kernel: 4.13.1-1-default Linux User 183145 working on a Pentium IV . -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4

[opensuse] some mp4 cannot be played "decoder profile above limits"
by Daniel Bauer 26 Sep '17

26 Sep '17

Hi everybody "Suddenly" the mp4-videos from my mobile phone cannot be played anymore, no matter what player I use: it only shows a black screen plus plays the sound, but no image. As for my small tests it only affects the mp4 from my samsung mobile that are larger than 10MB (9.8MB works, 11.2MB does not work, neither larger). But downloaded mp4, avi, etc. work normally even in GB size. I tried to start from commandline, and maybe the messages say something to somebody of you...: vlc 20161005_085414.mp4 VLC media player 2.2.6 Umbrella (revision 2.2.6-0-g1aae78981c) [000055aac07500c8] core libvlc: VLC wird mit dem Standard-Interface ausgeführt. Benutzen Sie 'cvlc', um VLC ohne Interface zu verwenden. [00007f236c0b6378] vdpau_avcodec generic error: decoder profile above limits: level 51 3840x2160 [00007f236c0c48b8] freetype spu text error: Breaking unbreakable line QObject::~QObject: Timers cannot be stopped from another thread I see a limit, but don't know where I can change this limit. Everything worked a few weeks ago with the same system, but meanwhile there were some updates and of course I have no idea which one changed that... Leap 42.3 KDE 5.8.7 Kernel 4.4.87-25 default Latest "zypper up" done 5 minutes ago. All "media-things" installed from packman. Any hints? Thanks! Daniel -- Daniel Bauer photographer Basel Barcelona https://www.patreon.com/danielbauer http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 35

Re: [opensuse] C++ Question
by Greg Freemyer 25 Sep '17

25 Sep '17

> > ask for help on getting the spec file right. Here or there is a packaging > mailing list. But at this basic level, here should be fine. > > Greg I forgot to say specfiles can get pretty complicated. I maintain the one for sleuthkit and it isn't too bad. Use it as an example of what you need to do as you hit stumbling blocks: https://build.opensuse.org/package/view_file/security:forensics/sleuthkit/s… Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0