Bug 1707702 - On a bcache partition updateing to or installing fedora 30 results in filesystem corruption.
Summary: On a bcache partition updateing to or installing fedora 30 results in filesys...
Keywords:
Status: CLOSED DUPLICATE of bug 1708315
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-08 07:02 UTC by Fredrik Chabot
Modified: 2019-05-13 08:07 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-13 08:07:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Fredrik Chabot 2019-05-08 07:02:29 UTC
1. Please describe the problem:

I've tried updating an Fedora 28 to Fedora 30, It used bcache.
First boot looked okay at first but filesystem corruption became apparent very quickly and the system became unbootable and fsck could not repair the filesystem.

Installing Fedora 30 fresh on a fresh bcache partition the filesystem corruption is enough I cannot successfully complete the installation


2. What is the Version-Release number of the kernel:

version 5.0.9


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

It worked in several previous releases inclusing Fedora 26 and 28


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Yes, Boot live install image.
From the commandline create a partition for /boot, on your hdd and one on the ssd.
Use make-bcache and create a bcache0 device. Put lvm on it pvcreate /dev/bcache0, create a vg, and a lv.
Start the installer, select manual partition and select the created partitions.

Start the installation.

Installation repeatedly crashes with some random error.

Look with journalctl and observe filesystem corruption messages. 


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

idk

6. Are you running any modules that not shipped with directly Fedora's kernel?:

no

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Fredrik Chabot 2019-05-13 08:07:44 UTC

*** This bug has been marked as a duplicate of bug 1708315 ***


Note You need to log in before you can comment on or make changes to this bug.