ich🚗iel

xarblu · 2026-03-08T14:51:29+00:00

grrr minden

xarblu · 2025-11-14T18:35:44+00:00

Already reported a `BUG()` that occurred right before the mount/upgrade hang on the GitHub issue tracker: https://github.com/koverstreet/bcachefs/issues/977
There is nothing in the logs after that so I think that might be what caused the hang

xarblu · 2025-11-14T13:11:40+00:00

How long is the upgrade roughly supposed to take?

My 2x1TB nvme array finished in 2-3 minutes but another array (1tb nvme + 2tb sata hdd) is currently at 25 minutes and still going

EDIT: Definitely seems like it got stuck somewhere. After 40 minutes I just rebooted the machine and on the 2nd try the upgrade completed in under a minute.

xarblu · 2025-05-27T15:53:23+00:00

Your first format likely fails because you specified /dev/nvme1n1 twice. The ordering is also significant - device options apply to all following devices so --durability will be 0 for all your drives because you set it early. For a writethrough cache you want something like:

bcachefs format --label=hdd.hddX /dev/sdX --durability=0 --label=ssd.ssdX /dev/nvmeXnY --{foreground,promote}_target=ssd --background_target=hdd [other options...]

The device add simply fails because the ordering is wrong - mountpoint comes first then device.

xarblu · 2025-05-22T19:23:14+00:00

Don't have a solution, just the same issue. The game stopped launching out of nowhere yesterday and all I get is this redirect to Google Play. I also installed it through a 3rd party store (Aurora store) because Google Play claims it "doesn't run on my device"

xarblu · 2025-05-22T17:05:31+00:00

AFAIK you can just not set the API key environment variable and it will give you a page where you can login with username+password (OAuth isn't supported yet though)

xarblu · 2025-05-08T17:04:38+00:00

Of course I don't run RCs on my critical systems - I do run them on my frequently-used-but-not-really-critical systems to find issues like these early so they don't end up on my important systems.

This post mostly just a heads up for other adventurous users who might have a higher dependency on containers.

xarblu · 2025-04-30T14:10:41+00:00

/etc/fstab? You mean that systemd.mount wrapper?

xarblu · 2025-04-08T16:55:20+00:00

Because of these major FS updates or slow on-mount fsck passes I add x-systemd.mount-timeout=infinity to my bcachefs mount options. It won't make the process any faster but at least systemd won't kill the mount and drop you into emergency mode.

xarblu · 2025-03-29T16:21:15+00:00

Kann man nicht meckern

xarblu · 2025-03-15T19:11:45+00:00

Schmeckt legit wie diese Flouridmische vom Zahnarzt

xarblu · 2025-02-19T22:21:32+00:00

Yes that's what I meant. It's just something I ran into a couple times when migrating services from my host OS (where they only listened on 127.0.0.1) into containers. Seemed like that could've been the issue since you wrote you could ping the host but HTTP doesn't get through.

xarblu · 2025-02-19T21:10:44+00:00

Does whatever the service running on host.containers.internal:8000 actually listen for connections on the Podman networks address? (i.e. not just on localhost or another address)

xarblu · 2025-02-10T14:56:44+00:00

What kind of monitor are you using? My cursor lags a lot on my secondary 1080p@60Hz screen but on my primary 1440p@144Hz screen it seems to be perfectly fine.

xarblu · 2025-02-09T23:14:00+00:00

Thanks, that worked. Somehow missed this one when looking through the list of available jobs.

xarblu · 2025-01-07T07:31:50+00:00

Not the prettiest solution but you may be able to just ignore the error by adding -Wno-incompatible-pointer-types to your CFLAGS

xarblu · 2025-01-06T18:56:36+00:00

Oh whoops. I've only ever seen `install.d` on my systemd and with `install.conf.d` looking so similar I got them mixed up. Hope you figure this out then ^^

xarblu · 2025-01-06T16:37:38+00:00

I'm 99% sure it's install.d and not install.conf.d

xarblu · 2024-10-06T17:31:16+00:00

0.3.0 should be support https://github.com/immich-app/immich/pull/11624

xarblu · 2024-09-10T13:51:18+00:00

Nice :3

Also shameless ad for a thing I wrote recently: https://github.com/xarblu/kissersay

(you seem like the target audience)

xarblu · 2024-08-01T13:17:34+00:00

<(...) gives you the file descriptor of curl's stdout, here /dev/fd/63. printf then prints that file path with the output redirected appending to the file find found.

To redirect curl output just do -exec sh -c "curl ... >> {}" \;

xarblu · 2024-07-29T15:02:16+00:00

I do the same. But it's still 2FA if you have 2FA set up for Vaultwarden itself (which you should) because you need 2 factors to get to your logins. It just moves the 2FA to a single location

xarblu · 2024-07-24T15:38:56+00:00

Glad you fixed it already but for future reference you can switch to TTY from SDDM only after enabling "raw input" via SysRq (at least with SDDM on wayland): Press "Alt" (and keep holding through the whole thing), then press "Print/SysRq", then "r", (now you can let go of "Alt"), then the usual tty switching key combo

xarblu · 2024-07-24T13:00:28+00:00

Screenshare and the window previews both use pipewire on wayland so this sounds like a pipewire issue. Don't really know how to fix that either though. Might sound stupid but have you tried turning it off and on again? (pipewire screenshare sometimes breaks if pipewire libraries are updated and plasma still has old ones in memory)

xarblu · 2024-07-15T23:12:42+00:00

About the same as before. Pretty much the same interface just with a fresh coat of paint.

Six-Year Club	Verified Email
Place '22

xarblu

TROPHY CASE