Re: Is there a procedure to rebuild /var/lib/dnf/history.sqlite?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Mar 13, 2021 at 10:13 AM George R Goffe via test
<test@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Chris,
>
> I goofed and sent this with the wrong subject. Sorry about that.
>
>
> Thanks for responding.
>
> I converted /var to btrfs about 2 weeks ago so this isn't necessarily related to that (I hope).
>
> Here's what "btrfs filesystem usage /var" says about /var: (it is NOT mounted ro)
>
>
> fc35-bash 5.1 ~# btrfs filesystem usage /var
> Overall:
>     Device size:                  64.00GiB
>     Device allocated:             63.94GiB
>     Device unallocated:           65.68MiB
>     Device missing:                  0.00B
>     Used:                         50.30GiB
>     Free (estimated):             13.01GiB      (min: 13.01GiB)
>     Free (statfs, df):            13.01GiB
>     Data ratio:                       1.00
>     Metadata ratio:                   1.00
>     Global reserve:               61.03MiB      (used: 0.00B)
>     Multiple profiles:                  no
>
> Data,single: Size:63.15GiB, Used:50.20GiB (79.49%)
>    /dev/sda5      63.15GiB
>
> Metadata,single: Size:776.00MiB, Used:105.33MiB (13.57%)
>    /dev/sda5     776.00MiB
>
> System,single: Size:32.00MiB, Used:16.00KiB (0.05%)
>    /dev/sda5      32.00MiB
>
> Unallocated:
>    /dev/sda5      65.68MiB
>
>
>
>
> dmesg buffer, recent boot:

yeah what I'm looking for are the kernel messages at the time of the
I/O error you're getting from dnf. Do this:

journalctl -fk

And in another terminal shell, run the same dnf history command that
triggers the error, switch back to the first shell and see what
messages have appeared.


>You will note what looks like a kernel dump related to duplicate lock requests. This and other kernel oops like events happen on a regular basis on "my" systems. I got tired of reporting them and getting NO response to the bug reports. Sigh.

It's an older 5.11.0-rc6 debug kernel.  You don't need to report the
lockdep warnings. They come and go in kernel rc development. Pretty
sure that particular lock dep warning was fixed a while ago. The
current Fedora kernel is 5.11.5 with 5.11.6 heading to stable soon, so
you should update.



-- 
Chris Murphy
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux