I don’t bother stopping services during backup, each service is contained to a single LVM volume, so snapshotting is exactly the same as yanking the plug. I haven’t had any issues yet, either with actual power failures or data restores.
Yes, I have. I should probsbly test them again though, as it’s been a while, and Immich at least has had many potentially significant changes.
LVM snapshots are virtually instant, and there is no merge operation, so deleting the snapshot is also virtually instant. The way it works is by creating a new space where the difference from the main volume are written, so each time the application writes to the main volume the old block will be copied to the snapshot first. This does mean that disk performance will be somewhat lower than without snapshots, however I’ve not really noticed any practical implications. (I believe LVM typically creates my snapshots on a different physical disk from where the main volume lives though.)
I’m assuming you have a lot of flush-mount ceiling fixtures (aka boob lights)? My experience with them is that they’re very effective LED bulb killers.
The only two that have lasted are in my range hood for light above my stove. Those experience extreme heat and yet they are fine.
They only experience heat when you’re cooking, and are able to vent that heat to a large volume of air (assuming they’re not enclosed, or only enclosed by a thin sheet of plastic). The rest of the time they’re probably powered off and at ambient temperatures. Compare that to enclosed flush-mount fixtures, in which bulbs stay on for large portions of the day, trapping lots of heat in a small space for long periods of time. That’s a perfect recipe for killing LED bulbs.
If your house was built prior to LED bulbs being so widespread, it might be worthwhile to consider new fixtures that were actually designed with LED bulbs in mind.
Also, don’t buy no-name bulbs off Amazon. Chinese factories crank out shitty bulbs that are designed and built as cheaply as possible, and they will fail quickly.
Is there a list of what each app failed? It would be nice for the devs to be able to see. I use Mlem, and there is about to be a new release rebuilding it from the ground up. Hopefully it will rate higher once that happens.
Thanks. Interesting how the apps, even those that have lower scores, perform better than a web browser. Using Safari and Firefox (on a laptop) and both open your links in Lemmy.world instead of that thread on my instance. Neither recognize the user as anything other than text.
I’m always for shitting on TERFs, but I have no idea what this meme is about. Probably because I try my best to keep ‘anti-woke’ things out of my orb. Can someone please get me in on this joke that I desperately want to be a part of haha
I dont actually know either, but I assume it’s referring to a sad statistic relevant to the trans community and the role of gravity in the abrupt termination of velocity.
Honestly, my biggest issue with LLMs is how they source their training data to create “their own” stuff. A meme calling it a plagiarism machine struck a chord with me. Almost anyone else I’d sympathize with, but fuck Spez.
Yep they now get paid for the data we have them. I have no sympathy lol. At least these models can’t actually store it all losslessly by any stretch of the imagination. The compression factors would have to be like 100-200X+ anything we’ve ever been able to achieve before. The numbers don’t work out. The models do encode a lot though and some of it is going to include actual full text data etc but it’ll still be kinda fuzzy.
I think we do need ALL OPEN SOURCE. Not just for AI, but I know on that point I’m preaching to the choir here lol
What resonated with me is people calling LLMs and Stable Diffusion “copyright laundering”. If copyright ever swung in AI’s favor it would be super easy to train an AI on stuff you want to steal, add in some generic training, and now you have a “new” piece of art.
LLMs and Stable Diffusion are just compression algorithms for abstract patterns, only one level above data.
I've never had to replace an LED bulb, ever. They last forever if there isn't a problem with your installation, like poor electrical wiring or poor ventilation
Exactly. LEDs are rated for 10k hours. 10-15 watt power supplies made both to cram into a tiny space defined by GE 100 years ago for a completely different lighting technology, and to hit a $2.00 price point for the whole assembly? Not so much.
I’ve actually got a super cheap and super bright LED in my garage that has been working for a long time, but it’s one of those big ugly sunflower looking ones that would never fit in an enclosed fixture anyway, so it actually lets the power supply breathe. Even then, I’m sure it’s putting out more lumens than is good for whatever half-assed components and heat sink are in it.
The first LED I bought is about 7 years old at this point, so that tracks. I was being hyperbolic when i said "forever", they aren't designed to last literally forever, i just meant many many many years
It should work that way. If you use the recommended Docker Compose scripts for immich, you’ll notice that only a few volumes are mounted to store your data. These volumes don’t include information about running instances. If you take snapshots of these volumes, back them up, remove the containers and volumes, then restore the data and rerun the Compose scripts, you should be right where you left off, without any remnants from previous processes. That’s a pro of container process isolation
Docker doesn’t change the relationship between a running process and its data. At the end of the day you have a process running in memory that opens, reads, writes and closes files that reside on some filesystem. The process must be presented with a valid POSIX environment (or equivalent). What happens with the files when the process is killed instantly and what happens when it’s started afterwards and it re-reads the files doesn’t change based on where the files reside or where the process runs. You could run it in docker, in a VM, on Linux, on Unix, or even Windows. You could store the files in a docker volume, you could mount them in, have them on NFS, in the end they’re available to the process via filesystem calls. In the end the effects are limited to the interactions between the process and its data. Docker cannot remove this interaction. If it did, the software would break.
That’s the trivial scenario that we know won’t fail - stopping the service during snapshot. The scenario that I was asking people’s opinions on is not stopping the service during snapshot and what restoring from such backup would mean.
Let me contrast the two by completing your example:
docker start container
Time passes
Time to backup
docker stop container
Make your snapshot
docker start container
Time passes
Shit happens and restore from backup is needed
docker stop container
Restore from snapshot
docker start container
Now here’s the interesting scenario:
docker start container
Time passes
Time to backup
Make your snapshot
Time passes
Shit happens and restore from backup is needed
docker stop container
Restore from snapshot
docker start container
Notice that in the second scenario we are not stopping the container. The snapshot is taken while it’s live. This means databases and other files are open, likely actively being written to. Some files are likely only partially written. There are also likely various temporary lock files present. All of that is stored in the snapshot. When we restore from this snapshot and start the service it will see all of that. Contrast this with the trivial scenario when the service is stopped. Upon stopping it, all data is synced to disk, inflight database operations are completed or canceled, partial writes are completed or discarded, lock files are cleaned up. When we restore from such a snapshot and start the service, it will “think” it just starts from a clean stop, nothing extra to do. In the live snapshot scenario the service will have to do cleanup. For example it will have to decide what to do with existing lock files. Are they there because there’s another instance of the service that is running and writing to the database or did someone kill its process before it had the chance to go through its shutdown procedure. In the former case it might have to log an error and quit. In the other it would have to remove the lock files. And so on and so forth.
As for th effect of docker on any of this, whether you have docker stop container or systemctl stop service or pkill service the effects on the process and its data is all the same. In fact the docker and systemctl commands will result in a kill signal being sent to the process of the service anyway.
The simple answer is that it’s a bad idea to take snapshots of running databases because at best they could be missing info and at worst they can corrupt.
Very disappointing if the only reason is competition. I don’t really think that any Obsidian RPG is going to sell gangbusters, and there’s not really any competition within the space, so if this is just Microsoft wanting to pad out their release schedule to keep people hooked on Game Pass, that’s scummy as fuck.
Hopefully the extra time in the tank prevents the typically Obsidian jank from creeping in at least.
Whether or not theres competition in the genre, putting a release around the holiday schedule is usually a bad time for your game unless you are a top name in the industry. The most famous case being Titanfall 2 being sandwiched between CoD and Battlefield with Gears of War, Final Fantasy, Pokemon, and South Park releasing at similar times too. Titanfall was drowned out by relevant and irrelevant competition and was likely the best game in that holiday season. Simply delaying it to January could have been the difference between being forgotten and the next biggest franchise.
I mean, even despite that release date, Titanfall 2 sold 4 million copies that holiday season and is certainly remembered today more than Battlefield 1 or CoD: Infinite Warfare. The franchise has managed to continue through Apex Legends. Maybe delaying it would have caused it to sell a little bit better initially, but I think positive word of mouth gave it much longer legs.
Also…is anything actually releasing later this year that’s worth pushing back for? Especially in the realm of RPGs? If anything pushing it back is going to cause it to conflict with Dragon Age Veilguard, which is also looking to be released very late 2024-early 2025, and is realistically the closest competition Avowed could run into. There’s basically no other RPGs releasing this fall, so who’s to say that it wouldn’t get a ton of attention by being one of the only options in town?
I recognize I’m kind of being one of those “it works on my machine!” types, but I’m rolling pop!os on a lenovo built intel/nvidia laptop and have zero issues. Am I just exceptionally lucky?
You’re not. I think that’s the experience of most Linux users. It’s selection bias; I don’t go to forums to make a post advertising how my system is working great with no bugs. When my system is working great with no bugs I just use it; I don’t talk about it.
I roll popos and tried nobara and mint a month ago. I’m back on pop because it just works and installing games on it is no issue. There are a couple games that after playing a few hours a day for three or four days, the computer kind of freezes for a second here and there. I just log out and in and it’s fixed. I would rather throw my computer in the street and run it over than go back to windows.
Which Lenovo laptop, if you don’t mind me asking? I know there are Lenovo laptops with Linux support, but I am on a Lenovo Legion Slim 5, and I have heard there are quite a few issues that would need to be sorted.
I’ve got the legion y540 with an RTX 2060, apparently they made this same model number with a couple different gpu‘s.
I have no idea if it officially has linux support or not, I just got frustrated when it wouldn’t stop bluescreen’ing with windows 10. Ubuntu worked fine but was finnacky with peripherals, and I couldn’t change the brightness without fixes. Pop!OS has just worked perfectly across the board, straight out of the box.
What’s whacky is I could swear games run better on linux. Not even natively, like WINDOWS games run better through proton than they did when the same system ran windows. I’d bet a lot of it is just overhead from general bloat; windows is expensive to run these days.
If my experience is anything to go by, just start installing whatever OS strikes your fancy and hope for the best. Keep a windows usb handy just in case, but just start fucken around! You could spend a week reading documentation on ONE SINGLE OS, or you could spend just an afternoon trying probably every single OS you could find a modern ISO for. Just make sure you try the popular ones first hahaha
kbin.life
Newest