Vytautas Mickus

I tried running bcachefs fsck: https://gist.github.com/Eximius/5f2a70b00d61a0f8d1fb8b11dd6068d7 It doesn't make sense that the metadata is this messed up even if one of the nvme drives had a mid-block-tree-rebuild failure under a...

As another comment, would be nice if fsck showed more than just the basename of the file when it reached a broken ent.:)

So... it (or similar) happened again. After a graceful reboot (after gpu froze up), the machine was no longer reachable after booting up. Booting into a usb stick gave the...

That is still in future tense though :) I have no idea what's happening here. I just had a minor issue again that needed a live usb. I didnt write...

Ahaha! The virtualization again locked up the machine. After 2 force-resets, and into live-usb, I have: ``` bcachefs: duplicate journal entries on same device, fixing bcachefs: superblock not marked as...

The journal replication issue is likely when you have a raid0 in bcachefs. bcachefs setup: ``` External UUID: 379774e3-3bc1-437f-81ca-970b92d7846b Internal UUID: 3ad677e8-9ab0-4a84-b405-9786dc60b160 Label: Version: 11 Created: Mon Nov 23 02:03:52...

I ran fsck on the raid, because I was still getting data checksum errors: ``` [root@archusb ~]# bcachefs fsck -fp /dev/nvme0n1 /dev/nvme1n1p2 recovering from clean shutdown, journal seq 6401305 journal...

Clean reboot after navi gpu lockup. (I would remove the pci device for the gpu and try a soft reset. The whole system is responsive.) ``` [ 23.581527] bcachefs (379774e3-3bc1-437f-81ca-970b92d7846b):...

It is a bit too painful having ordinary reboots kill the filesystem. So I will switch to something else. Also, having at least the filenames that are permanently removed shown...

Not sure if this is the best issue to add to. However, the fact that xonsh has no way of doing non-interactive shell config breaks many things. Such as PATH...