Event JSON
{
"id": "937ba8dc9d13450a95fa739b427f551cbd50f893d972633ce160a63897a4a106",
"pubkey": "beee28c6450eb5d21bf94279d1f3f41e524c87abf86393835b45e6a1e98390e7",
"created_at": 1688953108,
"kind": 1,
"tags": [
[
"p",
"7c6b9abd7afe41ece9808d7b8f99d9c3b13ff7aadf314a1d83684f76b9efcb91",
"wss://relay.mostr.pub"
],
[
"p",
"a9418a6c1007fda46f9aedc8c7fd66cc64c5a28c2bb186c7ef9ad5c4cd5f4730",
"wss://relay.mostr.pub"
],
[
"e",
"2c24086c4153607f6b45422d8cc1f152c3279be25830545c5c62a9dfa80bea52",
"wss://relay.mostr.pub",
"reply"
],
[
"t",
"fedora"
],
[
"t",
"btrfs"
],
[
"mostr",
"https://mastodon.online/users/vwbusguy/statuses/110687230914354118"
]
],
"content": "nostr:npub1034e40t6leq7e6vq34aclxwecwcnlaa2muc558vrdp8hdw00ewgs8gfpua Same. I've been running #btrfs on #Fedora since around 2015 and never had any data loss. Most data loss I've seen was people trying to do software RAID5/6 with it. Pretty much every \"it killed my drive\" I've seen ended up not being due to btrfs but bad hardware that was DOA (happens more often than people think). Only biggish downsides I can really think of is btrfs is still probably a little slower for RDBMS backends and it's pretty much impossible to forensically recover.",
"sig": "fa8bf941a674a33dc3e04bf2d0f32a4782c9c65c6cf0b348a53d9c504c0da9d6ff293a1f47f96b896f5472ada13b16227ef9cb17b411149f27db88c007593063"
}
