From: "Göran Uddeborg" <goeran@uddeborg.se>
To: linux-ext4@vger.kernel.org
Subject: Contents of files exchanged
Date: Mon, 8 Nov 2021 23:15:13 +0100 [thread overview]
Message-ID: <24969.41329.680145.538898@gargle.gargle.HOWL> (raw)
Is a "user question" acceptable on this list?
When helping a friend with a system that wouldn't boot, we
investigated the file system from a live image. It turned out that a
lot of files had had their contents replaced with a completely
different file's contents. As an example, the libuuid.so.1.3.0 file
had the contents of the README file from the zfs-fuse package. They
still had different inode numbers; they were not links to the same.
There were at least dozens of files "replaced" in that way, we stopped
searching after fixing a few.
This started after an abrupt unplanned power loss, so a fsck on reboot
was expected. But how could it possibly have such a drastic effect?
In case it is relevant, it was on a Fedora 34, initially installed
before btrfs was default on Fedora, and upgraded since.
reply other threads:[~2021-11-08 23:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24969.41329.680145.538898@gargle.gargle.HOWL \
--to=goeran@uddeborg.se \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).