type of girlthing who just ran a script that did `mv */* .` in its $HOME several times
yes, i am completely fucked
type of girlthing who just ran a script that did `mv */* .` in its $HOME several times
yes, i am completely fucked
by "just now" i mean a few hours ago, and by "completely fucked" i mean that i have 3871 (at least) files left to sort manually, out of more than 8000
most of these things are version-controlled and replicated at least once (and i didn't lose any .git directories because */* doesn't select them), which is why i don't really do backups (except for really important stuff like contracts and evidence and so on); when your code is almost entirely open-source and globally distributed it feels wrong to waste space and time copying it over slow (compared to hundreds of GB of checkouts) WiFi in a cronjob
@whitequark This is the sort of thing that'd make me restore a backup.
@jernej__s don't have one
at a rate of about 200/hour i will be here for quite a while
@whitequark I have a file named -i in my home directory.
@purpleidea ... good idea, but would not help me here
@whitequark even for things with no back up, i personally run 15-minutely btrbk btrfs snapshots with decaying retention for earlier files. snapshots like these take minimal time to create and help with being able to create backup in a more consistent state
i will probably switch to zfs for my next computer/drive, whichever comes first, but the principle is the same.
ofc this depends on fs support. i'm not aware if lvm is capable of doing this on a block dev but it sounds sketchy
@whitequark I know, sorry. You'll be ready for next time!
@dramforever oh this is a fantastic idea. lvm should be able to do it and i already use it
@whitequark i found some anecdote that "thin-provisioned LVM snapshots" work well. i don't know if you can smoothly start using this
@dramforever i just checked and i can convert my existing LV to a thin one on the fly. my one concern is that corruption of the thin metadata volume might cause extremely severe data loss
@dramforever i think i want RAID1 for the thin metadata via LVM RAID, which should be at least somewhat repairable
@whitequark that makes sense, and also matches my haven't-ever-used-lvm intuition that it seems a bit sketchy...
@dramforever LVM has been incredibly reliable for me so it doesn't worry me a lot; I worry about drives
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.