On Sun, Mar 14, 2021 at 4:05 PM George R Goffe via test
wrote:
>
> Chris,
>
> The inode is NOT the same one. I tried a sqlite dump | restore operation but
> it didn't work...
>
> With your journalctl -f and trying dnf history, dnf reported I/O errors but
> no kernel or /var/log/messages appeared
First, this shouldn't be necessary, therefore I'm kinda suspicious.
But it's inspecific suspicion. Maybe it is conversion.
I also don't know if this will fix the SQLite I/O errors, or make
things worse, in which case you'd lose dnf history (probably not a big
loss).
sudo -i
cd /var/lib/dnf/
sqlit
On Sat, Mar 13, 2021 at 8:03 PM George R Goffe via test
wrote:
>
> Chris,
>
> I see NO I/O messages.
You previously reported them.
>History database is not writable: SQLite error on
>"/var/lib/dnf/history.sqlite": Executing an SQL statement failed: disk I/O
>error
>History database is not writ
RFS error (device sda5): bdev /dev/sda5 errs: wr
0, rd 0, flush 0, corrupt 85, gen 0
Mar 13 17:33:47 fc35 kernel: BTRFS info (device sda5): scrub: started on devid 1
Mar 13 17:34:39 fc35 kernel: BTRFS info (device sda5): scrub: finished on devid
1 with status: 0
---
On Sat, Mar 13, 2021 at 10:13 AM George R Goffe via test
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
On Fri, Mar 12, 2021 at 10:14 PM George R Goffe via test
wrote:
>
> Hi,
>
> Trying to upgrade this system with "dnf upgrade" gives messages:
>
> /usr/bin/dnf --noautoremove --refresh --skip-broken --allowerasing --best
> --setopt=zchunk=0 --exclude=*kernel* --exclude=environment-modules*
> --exc
Hi,
Trying to upgrade this system with "dnf upgrade" gives messages:
/usr/bin/dnf --noautoremove --refresh --skip-broken --allowerasing --best
--setopt=zchunk=0 --exclude=*kernel* --exclude=environment-modules*
--exclude=Lmod upgrade
Fedora rawhide openh264 (From Cisco) - x86_64
