Postings by Rolf Fokkens

Upgrade to Fedora 30 consistently corrupts bcache storage - is there some kind of emergency brake possible during upgrade?

Hi All,

There's this issue: <a href="" title=""></a>

Would have been better if I discovered it during Alpha or Beta, but
unfortunately I didn't.

When to make packeges "dnf protected"

Hi all,

As the maintainer of bcache-tools I ran into the situation that a
collegue accidentally removed bcache-tools, resulting in a system that
failed to boot after installing and using a new kernel. dnf logs showed
that the package had been erased, with a bunch of other packages. It
happened 3 weeks ago, and the colleague did not recall what he actually
did at that time.

I'm considering to make bcache-tools protected (by including a config
file in the package in /etc/dnf/protected.d/) to prevent accidental
erasure of the package.

Sunday 13th of October: SSD cache test day

Hi All,

The Fedora SSD Cache is this sunday October 13th 2013. This Fedora Test
Day will focus on bcache based SSD Caching in Fedora 20.

<a href="" title=""></a>

If you're interested in trying out the new bcache SSD caching
functionality step by step instructions are available for:

- bcache on physical hardware
- bcache in a virtual machine
- non-root FS on bcache (with or without LVM)
- root FS on bcache (wtih or without LVM)

The objective of this Test day is to demonstrate a working Fedora 20
system using bcache.

bcache, udev rules and calling blkid


On bugzilla there was a brief discussion on how to reduce the number of
blkid calls during udev rules processing:

<a href="" title=""></a>

The general idea was to rely on earlier calls to blkid instead of having
later rules calling blkid themselves. Specifically for bcache this meant
relying on 13-dm-disk.rules and 60-persistent-storage-rules, which all
worked fine until...

...until I tested stacking bcache on top of raid (md). In that situation
61-bcache.rules was out of luck, because there was no prior call to
blkid so bcache was not detected.

Dracut, Anaconda & bcache


The following change has been accepted for F20:
<a href="" title=""></a>

More details: <a href="" title=""></a>

For F20 it'll be SelfContained, but for F21 the plans are to make it

I'm focussing currently on bcache, and I think bcache-tools is getting
into shape for F20 and non-root filesystems will work fine.

bcache-tools: How and when loading kernel module bcache

Hi all,

I'm working on packaging bcache-tools, see
<a href="" title=""></a>

I'd like some advice on "when and how to load the bcache kernel module".

The easiest way for now is to have a file
/etc/modules-load.d/bcache.conf in the package which makes systemd load
the module. This works when using bcache for some filesystems, but it
will also load the bcache module when no bcache is actually used. So, is
this the right approach?

An alternative would be to have the udev "bcache.rules" file load the
kernel module whenever a bcache block device is spotted.

Self Introduction

Hi All,

Having a great interrest in combining both the qualities of SSD's
(speed) and the qualities of HDD's (capacity) I added the following
change: <a href="" title=""></a>

Since this change was accepted, I now have to really do something :-) As
a result here's my first review request:
<a href="" title=""></a>

I have to admit that my interest in the combination of SSD's and HDD's
is primarily a user's interest. I'm not an experienced Fedora developer,
but in general I built all kinds of software in the past.