On my 3 systems, F34, F34, and CentOS7, they are
1, 2, and 6 years old respectively.
Are old rescue kernels still useful? (6 years?)
Are there automated or manual procedures to update
a rescue kernel?
Are there best practices for rescue kernel update?
If there are, I've missed them.
Jon H. LaBadie jonfu(a)jgcomp.com
Sorry, I am a bit of list
This command line works in a shell, but not in a bash
I may miss some quotes !
Thanks for your help.
/usr/bin/rm -v !(ZMAT*|out*|Out*|GENBAS|Note*)
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988 | | Room# D114A
The utility FSlint has many of the attributes for scanning the dust
bunnies out of my drives. It doesn't seem to available of Fedora
anymore. Did it just lose a maintainer or be declared too hazardous to use?
I am currently using Fedora_linux 34, and I'd like to know, since I have
been using this OS for over a month and a half, and I find DNF's output
a bit... too much, if I could modify it somehow.
I'd like to modify how it outputs the installation of software.
For example, when the dnf install package name command is issued, the
first thing that will appear on the terminal is how long ago the last
dependency check was done.
Can that line of output be suppressed in any way?
If not, that's fine, I'll get used to it, but still, it would be cool if
Any help would be apriciated.
I'm getting a pretty bad history with BTRFS as the default filesystem
for Fedora Workstation. Its messing up repeatedly and leaving me
stuck. I should note that I have used ext2/3/4 for about 20 years, ZFS
on Solaris for even longer, and ZFS on Ubuntu for 2 major releases now.
I have 2 different machines that have had issues so far.
On my Gateway Fedora 33 daily-driver machine running the 5.11 kernels, I
had a single Patriot SSD using the default BTRFS partitioning scheme. I
kept seeing BTRFS scrub reporting uncorrectable issues and assumed that
it was a defective SSD. However, this SSD is now in a Mandriva machine
and is solid. Its not the SSD. I did about 10 reinstalls after having
the machine lock up at random times, and finally trashed the machine in
frustration. I later discovered that it had developed a bad memory
stick, which may have contributed to the initial problem cause.
However, the lack of BTRFS robustness, no obvious mechanism to keep
/home during a reinstall, and very poor BTRFS documentation have left me
On my current daily-driver machine, I have fully-updated Fedora 34
running the 5.12 kernels on 2 disks set up as as a BTRFS RAID-1 pair. I
expected that would allow for much more robustness than the single disk
setup on my F33 machine, giving me error protection similar to what I
would have on ZFS. Unfortunately, that does not appear to be the case.
I have run low-level diagnostics on everything in this machine, and it
is working properly. Unusually, there aren't even any failed lowlevel
disk blocks on either drive. So the hardware on this older
enterprse-class Lenovo desktop is not faulty. I believe that due to
faulty BIOS and security chip handling in the 5.12 kernel, I have had
issues requiring me to occasionally hard powercycle the machine to get
it to actually power down.
One would expect that with BTRFS doing RAID-1, recovery from lockups
should never leave the filesystem damaged. That does not appear to be
the case. Currently the disks have no low-level errors, but BTRFS scrub
shows 10 unrecoverable errors. That's messed up. Both disks are
enterprise-class Seagate Constellation 500GB SATA drives with slightly
different model numbers and manufacturing dates, so I don't believe that
there is any firmware issue with them. No matter what, I expect that
the initial fsck or brtfs check should keep data integrity, but possibly
backing out a few seconds in journal transactions.
I am aware of at least one kernel bug being highly relevant as the
initial trigger - bugzilla 195809. I believe that there are serious
bugs in the hardware optimization in Firefox (one bug filed) and in
Gnome and more relevant bugs in the kernel, but whatever the triggering
issue, the filesystem should never fail.
How do I recover? The machine is currently bootable and seems to run
ok, but locks up once in a while on powerdown and on exiting firefox. I
cannot describe it as stable with this BTRFS issue. A scrub currently
says that / (and therefore also /home) has 10 unrecoverable errors. I
can find no Fedora or Suse documentation on how to recover from what
should be impossible situations like this. A reinstall will not
preserve /home, leading to unacceptable data loss. I did an offline
btrfs check on my F33 machine that left the machine unbootable, so its
probably not an option either. I'm stuck at this point. Should I just
stop using the default BTRFS filesystem and go back to ext4?