# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 10
# self = https://watcher.sour.is/conv/mouv5ba
mckinley-cc
mckinley.cc
View Thread
Pro tip: Don't run out of space on Btrfs.
movq
www.uninformativ.de
View Thread
@mckinley I don’t intend to. But what happens if you do? Are you stuck because everything is literally copy-on-write, even deleting files?
movq
www.uninformativ.de
View Thread
@mckinley I don’t intend to. But what happens if you do? Are you stuck because everything is literally copy-on-write, even deleting files?
movq
www.uninformativ.de
View Thread
@mckinley I don’t intend to. But what happens if you do? Are you stuck because everything is literally copy-on-write, even deleting files?
mckinley
twtxt.net
View Thread
@movq Pretty much. In my situation I was able to delete some files and snapshots and run a couple of different btrfs balance commands to move some allocations around. It looked like writes weren't all committed properly to the disk but nothing told me that explicitly.

I did a system update in this state and I think I remember mkinitcpio throwing more warnings than usual but I was doing something else and I didn't pay close attention to them. This coincided with a power outage and there was a lot of inconsistency, making me think it was hardware related. It was just btrfs, as far as I can tell, and I fixed it by reinstalling all the packages on the system once there was enough room. Luckily, I hadn't done anything important with that computer after the system update.
movq
www.uninformativ.de
View Thread
@mckinley

> It looked like writes weren't all committed properly to the disk but nothing told me that explicitly.

Oof? That would be a pretty horrible bug. 😳

I just played with a btrfs volume for a bit and tried to “break” it, but I just got ENOSPC and everything worked as expected. (Would have been really weird, though, if I were able to find bugs with just a few tests.)
movq
www.uninformativ.de
View Thread
@mckinley

> It looked like writes weren't all committed properly to the disk but nothing told me that explicitly.

Oof? That would be a pretty horrible bug. 😳

I just played with a btrfs volume for a bit and tried to “break” it, but I just got ENOSPC and everything worked as expected. (Would have been really weird, though, if I were able to find bugs with just a few tests.)
movq
www.uninformativ.de
View Thread
@mckinley

> It looked like writes weren't all committed properly to the disk but nothing told me that explicitly.

Oof? That would be a pretty horrible bug. 😳

I just played with a btrfs volume for a bit and tried to “break” it, but I just got ENOSPC and everything worked as expected. (Would have been really weird, though, if I were able to find bugs with just a few tests.)
mckinley
twtxt.net
View Thread
@movq Yeah, it seems like that should never happen under any circumstances but that's the best explanation I can come up with for what happened and once I fixed the space issue the other problems went away. That particular filesystem is on a LUKS device on a disk image served with NBD. The machine in question and the NBD server are both on Arch Linux so it has potentially unstable versions of all the software involved.

It's a real house of cards and I'm not surprised something like this happened. I'm keeping lots of backups. My setup is pretty unique but I stand by my original post. Running out of space on Btrfs isn't fun, even when it's functioning properly.
mckinley
twtxt.net
View Thread
@movq Yeah, it seems like that should never happen under any circumstances but that's the best explanation I can come up with for what happened and once I fixed the space issue the other problems went away. That particular filesystem is on a LUKS device on a disk image served with NBD. The machine in question and the NBD server are both on Arch Linux so it has potentially unstable versions of all the software involved.

It's a real house of cards and I'm not surprised something like this happened. I'm keeping lots of backups.