Errors in Zypper output.

Hello, I’m new to openSUSE (I chose to start with Tumbleweed, coming from Arch, keeping everything rolling :] ). I’m always getting errors in the Zypper output (see the end of the output):


> sudo zypper install iotop
root's password:
Loading repository data...
Reading installed packages...
Resolving package dependencies...


The following 7 NEW packages are going to be installed:
  iotop libdb-4_8 libgcc_s1 libpython2_7-1_0 libreadline6 python python-curses


7 new packages to install.
Overall download size: 1.9 MiB. Already cached: 0 B. After the operation,
additional 7.0 MiB will be used.
Continue? [y/n/? shows all options] (y): y
Retrieving package libgcc_s1-5.3.1+r231346-1.4.x86_64
                                           (1/7),  51.5 KiB ( 90.5 KiB unpacked)
Retrieving: libgcc_s1-5.3.1+r231346-1.4.x86_64.rpm .......................[done]
Retrieving package libpython2_7-1_0-2.7.10-4.1.x86_64
                                           (2/7), 617.0 KiB (  1.7 MiB unpacked)
Retrieving: libpython2_7-1_0-2.7.10-4.1.x86_64.rpm .........[done (490.8 KiB/s)]
Retrieving package libreadline6-6.3-86.2.x86_64
                                           (3/7), 156.1 KiB (336.6 KiB unpacked)
Retrieving: libreadline6-6.3-86.2.x86_64.rpm ...............[done (212.3 KiB/s)]
Retrieving package libdb-4_8-4.8.30-30.21.x86_64
                                           (4/7), 689.2 KiB (  3.1 MiB unpacked)
Retrieving: libdb-4_8-4.8.30-30.21.x86_64.rpm ..............[done (297.1 KiB/s)]
Retrieving package python-curses-2.7.10-4.1.x86_64
                                           (5/7),  47.6 KiB (134.9 KiB unpacked)
Retrieving: python-curses-2.7.10-4.1.x86_64.rpm ..........................[done]
Retrieving package python-2.7.10-4.1.x86_64
                                           (6/7), 311.5 KiB (  1.4 MiB unpacked)
Retrieving: python-2.7.10-4.1.x86_64.rpm ...................[done (295.9 KiB/s)]
Retrieving package iotop-0.6-6.1.noarch    (7/7),  53.0 KiB (170.4 KiB unpacked)
Retrieving: iotop-0.6-6.1.noarch.rpm .....................................[done]
Checking for file conflicts: .............................................[done]
(1/7) Installing: libgcc_s1-5.3.1+r231346-1.4.x86_64 .....................[done]
(2/7) Installing: libpython2_7-1_0-2.7.10-4.1.x86_64 .....................[done]
(3/7) Installing: libreadline6-6.3-86.2.x86_64 ...........................[done]
(4/7) Installing: libdb-4_8-4.8.30-30.21.x86_64 ..........................[done]
(5/7) Installing: python-curses-2.7.10-4.1.x86_64 ........................[done]
(6/7) Installing: python-2.7.10-4.1.x86_64 ...............................[done]
(7/7) Installing: iotop-0.6-6.1.noarch ...................................[done]
Additional rpm output:
error: rpmdb: read: 0x1ea6398, 4096: Input/output error
error: db4 error(5) from dbcursor->c_get: Input/output error

Are these errors bad? Or can I ignore them. The packages seem to be installed fine and so far they are working.

When I installed Tumbleweed, it accidentally installed to the thumbdrive that had the Tumbleweed network installer (overwriting the installer, not sure how that happened); I meant to install to the laptop hard disk. Then I copied the thumbdrive to the internal hard disk and resized the root partition, but this apparently left some things in unexpected shape (I remember coming across a file or program that depends on the knowing the location of the installation, which is now incorrect, I don’t rememmber what it was). Just throwing this out there in case this could be causing the problem. I intend to re-install Tumbleweed from scratch properly, again, but it takes so much time that I don’t have right now.

I would guess that those are inconsequential errors, mistakes made by the packager.

The important thing is the app is installed.
Anything in “Additional rpm output” usually is informative, not central to the app.

But, I’m sure the maintainers should appreciate it if you reported the packing mistakes, create a bug at
https:/bugzilla.opensuse.org

TSU

Yes

Or can I ignore them.

You should not. These errors indicate either filesystem corruption or hard drive issue. You need to check for hardware errors in kernel log.