lukefor
Repos
59
Followers
40
Following
30

Software implementation of LTO Ultrium tape AES-GCM decryption and SLDC decompression

3
1

Windows driver to enable S3 sleep support for sedutil encrypted NVMe drives

C
6
1

Minimalist watchface for Pebble

C
1
2

Firefox extension that allows system-wide push-to-talk in the Discord web client

Events

Created at 1 week ago
started
Created at 1 week ago
Created at 2 weeks ago
Created at 1 month ago
Created at 1 month ago
started
Created at 2 months ago
Created at 2 months ago
Created at 2 months ago
Created at 2 months ago
opened issue
Add option to silence Btrfs CoW journal warning or detect Btrfs RAID systems

Component

systemd-journald

Is your feature request related to a problem? Please describe

I re-enabled CoW due to losing journal contents during a partial disk failure on a Btrfs RAID 1 system. Btrfs does not guarantee any consistency for CoW files in RAID volumes - it does not checksum them or even check they are matching between disks! It is always unsafe to disable CoW on Btrfs RAID volumes. I was surprised to find systemd doing this by default

As a result of this, my dmesg is full of: systemd-journald[342]: Creating journal file /var/log/journal/xxxxxxxxxxxx/xxx.journal on a btrfs file system, and copy-on-write is enabled. This is likely to slow down journal access substantially, please consider turning off the copy-on-write file attribute on the journal directory, using chattr +C.

Describe the solution you'd like

In an ideal world systemd would detect Btrfs RAID and not disable CoW on these systems.

Failing that, you could detect the presence of /etc/tmpfiles.d/journal-nocow.conf and not print the warning, as the user has made an explicit choice

And failing both those, it would be nice to have an option to silence the warnings

Describe alternatives you've considered

No response

The systemd version you checked that didn't have the feature you are asking for

247

Created at 2 months ago
Created at 2 months ago
started
Created at 2 months ago
PS5 Remote Play + Wireguard

Not a bug but could be something to add to the readme. I was able to get PS5 Remote Play (both discovery and the actual video stream) working over Wireguard with the following:

./udp-broadcast-relay-redux --id 1 --port 9302 --dev wg0 --dev eno1 -t 192.168.0.255
./udp-broadcast-relay-redux --id 2 --port 9303 --dev eno1 --dev wg0 -t 10.69.0.2

Both instances of udp-broadcast-relay-redux are running on a Wireguard server on the same physical network as the PS5 (192.168.0.0/24). 10.69.0.2 is the IP of the Wireguard client.

Created at 2 months ago
Created at 2 months ago
Created at 2 months ago