Yamaban composed on 2018-11-16 01:42 (UTC+0100):

Hint: as root or via sudo "rpmdb --rebuilddb" Please look at the manpage first, it's short. "man rpmdb" Also, that can take some time, plan for it to take hours, be happy if its done sooner.

Don't be surprised if much sooner. I don't think I've seen it take as long as 2 minutes since moving from 32bit to 64bit and EXT4. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 16/11/2018 02.43, Yamaban wrote:

On Fri, 16 Nov 2018 02:06, Felix Miata wrote:

...

Yamaban composed on 2018-11-16 01:42 (UTC+0100):

...

Hint: as root or via sudo "rpmdb --rebuilddb" Please look at the manpage first, it's short. "man rpmdb" Also, that can take some time, plan for it to take hours, be happy if its done sooner.

Don't be surprised if much sooner. I don't think I've seen it take as long as 2 minutes since moving from 32bit to 64bit and EXT4.

On a clean database from a "fresh install" e.g. fresh Leap 15.0 and only updates since then, no upgrades / distro changes to e.g. 15.1 or Tumbleweed, then yes, it takes usually less than 10 minutes.

But in my experiance, long time used systems, e.g. "it stated as 10.0, and I've upgrades regulary since" and more often than not not "top-of-the-line" hardware (at least by todays standards), then, if corruption occurs, it will take longer, much longer.

Longest I've ever had was just shy of eleven hours: core2duo, rotating rust, 4GB Ram, upgraded since first install. No fun.

Possibly it is much faster on SSD? I have done the operation more than once, but not since some years. It was never that long, though. I do not want to try on my system, as it is working nicely, but it is a quad core2 of several years vintage with upgrades since ever ;-) I could do a backup of the databases, then run the repair just for fun. Dunno. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)

On 16/11/2018 15.16, Michael Hirmke wrote:

Hi,

[...]

...

...

Longest I've ever had was just shy of eleven hours: core2duo, rotating rust, 4GB Ram, upgraded since first install. No fun.

...

Possibly it is much faster on SSD?

...

I have done the operation more than once, but not since some years. It was never that long, though. I do not want to try on my system, as it is working nicely, but it is a quad core2 of several years vintage with upgrades since ever ;-)

...

I could do a backup of the databases, then run the repair just for fun. Dunno.

had to run it on a machine, where the OS has been upgraded since 2003. The rpm db was corrupted. rpmdb ran about 2 minutes.

- Intel(R) Xeon(R) CPU E3-1220L V2 @ 2.30GHz 4 Cores - 8 GB RAM - 512 GB SSD Samsung

I made a backup of the database, then did a rebuild: Telcontar:~ # time rpmdb --rebuilddb real 0m17.212s user 0m10.241s sys 0m4.110s Telcontar:~ # It is an SSD disk, and the system has gone through many updates. Backup: Telcontar:/var/lib/rpm/copia # l total 464080 drwxr-xr-x 2 root root 4096 Nov 17 00:48 ./ drwxr-xr-x 4 root root 4096 Nov 17 01:08 ../ -rw-r--r-- 1 root root 40366080 Nov 10 13:16 Basenames -rw-r--r-- 1 root root 24576 Nov 10 13:16 Conflictname -rw-r--r-- 1 root root 10285056 Nov 10 13:16 Dirnames -rw-r--r-- 1 root root 110592 Nov 10 13:16 Group -rw-r--r-- 1 root root 245760 Nov 10 13:16 Installtid -rw-r--r-- 1 root root 413696 Nov 10 13:16 Name -rw-r--r-- 1 root root 106496 Nov 10 13:16 Obsoletename -rw-r--r-- 1 root root 362856448 Nov 10 13:16 Packages -rw-r--r-- 1 root root 8126464 Nov 10 13:16 Providename -rw-r--r-- 1 root root 12288 Mar 3 2011 Pubkeys -rw-r--r-- 1 root root 1613824 Nov 10 13:16 Requirename -rw-r--r-- 1 root root 794624 Nov 10 13:16 Sha1header -rw-r--r-- 1 root root 479232 Nov 10 13:16 Sigmd5 -rw-r--r-- 1 root root 8192 Oct 6 22:17 Triggername -rw-r--r-- 1 root root 49754376 Oct 7 2005 packages.rpm3 Telcontar:/var/lib/rpm/copia # Result: Telcontar:/var/lib/rpm # Telcontar:/var/lib/rpm # l total 373728 drwxr-xr-x 4 root root 4096 Nov 17 01:08 ./ drwxr-xr-x 113 root root 4096 Nov 17 01:08 ../ -rw-r--r-- 1 root root 0 Nov 17 01:08 .rpm.lock -rw-r--r-- 1 root root 34963456 Nov 17 01:08 Basenames -rw-r--r-- 1 root root 24576 Nov 17 01:08 Conflictname -rw-r--r-- 1 root root 8560640 Nov 17 01:08 Dirnames -rw-r--r-- 1 root root 118784 Nov 17 01:08 Group -rw-r--r-- 1 root root 143360 Nov 17 01:08 Installtid -rw-r--r-- 1 root root 442368 Nov 17 01:08 Name -rw-r--r-- 1 root root 102400 Nov 17 01:08 Obsoletename -rw-r--r-- 1 root root 327798784 Nov 17 01:08 Packages -rw-r--r-- 1 root root 7921664 Nov 17 01:08 Providename -rw-r--r-- 1 root root 12288 Mar 3 2011 Pubkeys -rw-r--r-- 1 root root 1560576 Nov 17 01:08 Requirename -rw-r--r-- 1 root root 684032 Nov 17 01:08 Sha1header -rw-r--r-- 1 root root 393216 Nov 17 01:08 Sigmd5 -rw-r--r-- 1 root root 8192 Nov 17 01:08 Triggername drwxr-xr-x 2 root root 4096 Oct 19 20:09 alternatives/ drwxr-xr-x 2 root root 4096 Nov 17 00:48 copia/ Telcontar:/var/lib/rpm # -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)

Il 16/11/18 05:13, H.Merijn Brand ha scritto:

On Fri, 16 Nov 2018 01:42:11 +0100 (CET), Yamaban wrote:

...

Hint: as root or via sudo "rpmdb --rebuilddb" Please look at the manpage first, it's short. "man rpmdb" Also, that can take some time, plan for it to take hours, be happy if its done sooner.

Linux 4.19.1-1-default [openSUSE Tumbleweed 20181112] HP ZBook 15G3 Core(TM) i7-6820HQ CPU @ 2.70GHz/1111(8 cores) x86_64 15958 Mb

# rpm -qa | wc -l 8862 6.212u 0.315s 0:06.27 103.9% 0+0k 0+0io 0pf+0w

# rpmdb --rebuilddb 9.784u 1.880s 0:12.27 95.0% 0+0k 0+897280io 0pf+0w

Root disk is SSD under 10 seconds :)

My disk is not a SSD: Cannot see time spent by the process (may be you used a specific command to compute it) but at first glance it was below 1 minute. Also I can see that the header #4768 error has been cleaned ;-) : linux-turion64:/home/marco/WSJT-X_build/build # rpm -qa|wc -l errore: rpmdbNextIterator: salto h# 4768 tag[34]: BAD, tag 1096 type 5 offset 30728 count 477 len 1908 5058 linux-turion64:/home/marco/WSJT-X_build/build # rpmdb --rebuilddb errore: rpmdbNextIterator: salto h# 4768 tag[34]: BAD, tag 1096 type 5 offset 30728 count 477 len 1908 linux-turion64:/home/marco/WSJT-X_build/build # rpm -qa|wc -l 5058 Cheers, -- Marco Calistri Build: openSUSE Tumbleweed 20181112 Kernel: 4.18.15-1-default - Cinnamon 3.8.9

Il 16/11/18 11:18, Patrick Shanahan ha scritto:

* Marco Calistri [11-16-18 08:14]: [...]

...

My disk is not a SSD:

Cannot see time spent by the process (may be you used a specific command to compute it) but at first glance it was below 1 minute. Also I can see that the header #4768 error has been cleaned ;-) :

linux-turion64:/home/marco/WSJT-X_build/build # rpm -qa|wc -l errore: rpmdbNextIterator: salto h# 4768 tag[34]: BAD, tag 1096 type 5 offset 30728 count 477 len 1908 5058

linux-turion64:/home/marco/WSJT-X_build/build # rpmdb --rebuilddb errore: rpmdbNextIterator: salto h# 4768 tag[34]: BAD, tag 1096 type 5 offset 30728 count 477 len 1908

linux-turion64:/home/marco/WSJT-X_build/build # rpm -qa|wc -l 5058

time rpmdb --rebuilddb

time rpmdb --rebuilddb real 0m38,301s user 0m11,607s sys 0m2,539s Thanks! -- Marco Calistri Build: openSUSE Tumbleweed 20181112 Kernel: 4.18.15-1-default - Cinnamon 3.8.9