On 2021-Nov-29, at 18:45, Mark Millard wrote:
> For:
>
> uname -apKU
> FreeBSD CA72_4c8G_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #22
> main-n250972-319e9fc642a1-dirty: Tue Nov 23 12:25:36 PST 2021
> root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENER
For:
uname -apKU
FreeBSD CA72_4c8G_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #22
main-n250972-319e9fc642a1-dirty: Tue Nov 23 12:25:36 PST 2021
root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72
arm64 aarch64 1400042 1400042
building a va
On 11/29/21 06:22, Jamie Landeg-Jones wrote:
> Dennis Clarke via freebsd-current wrote:
>
>> europa# xz -dc /var/backups/pkg.sql.xz.3 > /var/db/pkg/local.sqlite.dump
>>
>> europa#
>> europa# pkg backup -r /var/db/pkg/local.sqlite.dump
>> Restoring database:
>> Restoring: 100%
>> pkg: sqlite error
Dennis Clarke via freebsd-current wrote:
> europa# xz -dc /var/backups/pkg.sql.xz.3 > /var/db/pkg/local.sqlite.dump
>
> europa#
> europa# pkg backup -r /var/db/pkg/local.sqlite.dump
> Restoring database:
> Restoring: 100%
> pkg: sqlite error while executing backup step in file backup.c:98: not
>
I had another kernel panic on an AMD64 server. This has resulted in the
pkg database being messed up. Also I was running a QEMU instance for
aarch64 and that ended up with a messed up pkg database also.
I saw some docs in section 4.4.8. Restoring the Package Database here:
https://docs.free