How did you fuck up recently?
-
I was clearing some brush with a machete, 6 stitches in my shin.
That reminds me of a few years ago when I noticed a neighbor down the street running a weed eater while wearing a small bikini. She had on heavy gardening gloves and safety goggles, but to protect the rest of her whole body just the bikini. And it was a really big-ass weed eater too, the kind with the extra side handle. Might have even been gas powered.
-
I planted hydrangeas in an area with too much sun exposure and they're getting scorched leaves while I wait for shade cloth to ship
wrote on last edited by [email protected]Hopefully you know that until the shade cloth arrives any kind of cloth will actually create shade.
-
For example, today i nearly set my house on fire after forgetting a pan on the stove.
wrote on last edited by [email protected]I decided it was a good idea to do the mandatory university stage while also working this summer, while also trying to pass my last four exams. I greatly overstimaded my capacities and the trust i should have gave to my employee when they said i would be working just some days a week.
-
I woke up to yet another day
I washed my dish towels with a yellow orange bag and now they're super bright yellow lol
wrote on last edited by [email protected]Many years ago there was something weirdly wrong with our old washer or dryer where white things occasionally came out stained bright pink. Not an overall tint like if you wash a cheap red shirt in the same load. It was always very distinct vivid stains, like if a little Pepto Bismol got splashed around. We never figured out what the hell was causing it.
-
I printed 200 labels at work all with a typo on it, so I had to print 200 more. Good thing the only thing that cost me was my time lol
Be glad. It could have been coffee mugs...
-
That reminds me of a few years ago when I noticed a neighbor down the street running a weed eater while wearing a small bikini. She had on heavy gardening gloves and safety goggles, but to protect the rest of her whole body just the bikini. And it was a really big-ass weed eater too, the kind with the extra side handle. Might have even been gas powered.
OMG. I worked on lawn care as a teen. I still to this day avert my face away from anyone weed whacking. Received many hits to the face even with safety gear.
-
For example, today i nearly set my house on fire after forgetting a pan on the stove.
Left my bicycle unattended (but locked) for 3 days. Came back to a bicycle without tires. Rip 300€
-
For example, today i nearly set my house on fire after forgetting a pan on the stove.
Bought some parts for my car without checking they fit. Two hour round trip to pick them up, hours grinding the old rust off them, more hours repainting them, another £100 buying all the extra bits I needed to fit them. Then got under the car and realised there was no way they were going to fit. Ended up just buying some refurbished ones off the internet so at least the extra parts weren’t wasted and I get to fit them.
They were anti-roll bars for anyone who cares.
-
Hopefully you know that until the shade cloth arrives any kind of cloth will actually create shade.
Aware, but heavy storms have been passing through for the last two weeks so I'm waiting it out instead of sacrificing cloth that won't hold up as well outdoors
-
I have textarea cache browser again installed (on desktop) for those rare cases where I want to recover text input.
I wouldn't attribute a fuckup on your end though. Just really unfortunate and depressing. Caused by someone else.
Eh, the mistake was in engaging with a post that was surely about to be deleted by the OP.
-
scary! did you lose the pan?
Fortunately not, cast iron is damn near invincible. Just a lot of smoke and a brief bit of terror.
-
For example, today i nearly set my house on fire after forgetting a pan on the stove.
wrote on last edited by [email protected]Oh I got this. Real good fuck up. So, I run a bunch of services for me and family and friends, like Nextcloud, Immich, Mastodon, etc. All of their data is stored on a big RAID array built with mdadm. I built it before I knew about dm-integrity, so I wanted to rebuild it with dm-integrity running on all the disks. So I took out one disk (it’s a RAID6, so it can stand losing a disk just fine), and added dm-integrity on top of it. When I tried to add it back to the array, mdadm was like, “that’s not a big enough device”. Ok, yeah, makes sense, dm-integrity takes up some space. So I took all the services offline and started a resize2fs to reduce from 22TB to 18TB. Well that was taking forever, so I canceled and ran e2fsck, no worries. I started a new resize2fs reducing from 22TB to 21.8TB, which should be good enough. On pass 4, it’s looking like it’s gonna take 8 DAYS. I can’t have my services offline for that long, so I cancel and run e2fsck. Thousands of errors. Oops.
At least it’s looking like all the errors are just in Mastodon’s cache files.
So now I’m moving all the files to an external drive in order to migrate the array properly. In its degraded state though, the array is painfully slow. At least my services are online.
So basically I risked my files (though I have a backup from about three days before all this), and gave myself an extra maybe ten days(?) of work.
Moral of the story, don’t ever use resize2fs unless you have time to wait.
-
Every time someone says millipede I get the millipede song stuck in my head.
how did I miss this, was this part of the original Charlie the Unicorn?
just wow, thank you for sharing this
-
For example, today i nearly set my house on fire after forgetting a pan on the stove.
wrote on last edited by [email protected]Left my iron plugged in for a week without realizing it.
Accidentally caused massive heat wave. Sorry folks, but I unplugged it so temps should start to go down now.
-
For example, today i nearly set my house on fire after forgetting a pan on the stove.
I made a move on a coworker I really like. Asked her if she wanted to fool around because I thought I would only be around for another week or two. But now that I've found a new place to live around here, it made me realize how shitty my train of thought was to put her in that sort of position.
-
For example, today i nearly set my house on fire after forgetting a pan on the stove.
I left a thermocouple connector unsecured and it fell onto an aftertreatment unit during testing.
When the aftertreatment unit was red hot the connector caught fire.
Was my first time ever using a fire extinguisher!
-
Left my bicycle unattended (but locked) for 3 days. Came back to a bicycle without tires. Rip 300€
Damn that sucks. I have a chain lock but it only loops through the frame and front wheel. I use a shitty old cable with it to loop through the back tire and my pannier strap if I’m leaving it on the bike. I do this because I’ve had a wheel jacked before also, it fucking sucks.
-
I ate too many blueberries yesterday and regret it today.
-
Forgot a lunch box for weeks at work, and then they threw it out while I was sick, so now I have to buy a new lunch box.
I am the one at my workplace who throws moldy lunchboxes away. Though in pur fridge it is mostly unopened yoghurts that somebody brings and forgets about. So disappointing how much food is wasted
-
Oh I got this. Real good fuck up. So, I run a bunch of services for me and family and friends, like Nextcloud, Immich, Mastodon, etc. All of their data is stored on a big RAID array built with mdadm. I built it before I knew about dm-integrity, so I wanted to rebuild it with dm-integrity running on all the disks. So I took out one disk (it’s a RAID6, so it can stand losing a disk just fine), and added dm-integrity on top of it. When I tried to add it back to the array, mdadm was like, “that’s not a big enough device”. Ok, yeah, makes sense, dm-integrity takes up some space. So I took all the services offline and started a resize2fs to reduce from 22TB to 18TB. Well that was taking forever, so I canceled and ran e2fsck, no worries. I started a new resize2fs reducing from 22TB to 21.8TB, which should be good enough. On pass 4, it’s looking like it’s gonna take 8 DAYS. I can’t have my services offline for that long, so I cancel and run e2fsck. Thousands of errors. Oops.
At least it’s looking like all the errors are just in Mastodon’s cache files.
So now I’m moving all the files to an external drive in order to migrate the array properly. In its degraded state though, the array is painfully slow. At least my services are online.
So basically I risked my files (though I have a backup from about three days before all this), and gave myself an extra maybe ten days(?) of work.
Moral of the story, don’t ever use resize2fs unless you have time to wait.
wrote on last edited by [email protected]I've done something like this before, but thankfully it only impacted services that I host for my own use, didn't affect any family and friends.
Btw, I've found the easiest (but not the cheapest) way to fix this is to simply buy bigger disks. Swap out each disk for a bigger one one-by-one, then resize the whole volume to fill the new disks. Resizing upwards is much faster than shrinking a volume.
I've never had a volume shrink operation work without errors, and yes it takes days if you have more than 4TB.
