61–70 of 223 posts
Earlier quoted context omitted.
This is why one should generally be using network/cloud storage, with soft/hard limits. As soon as the soft limit is hit, fire off an alert. Have the hard limit set at double or more.
On my MacBook, I like to keep a few giant blank files that I can delete in a disk space emergency.
I was responsible for some dev ops stuff at a state's health department and one of the more infuriating things about working at that place was that it was like pulling teeth getting more storage allocated. Our backups would be running out of disk and they'd allocate me 50 or 100 GB at a time. I'm sure someone Toyototian was yelling that this was going to happen for the past 6 months.
Unfortunately, this strategy frustrates users who have a genuine need to expand storage and who are unable to efficiently obtain an exception to the process.
Earlier quoted context omitted.
I just had much more fun experience on Debian. The VM simply froze after startup as disk was absolutely full... And figuring out how to actually extend disk through all of the indirection layers took a bit of time.
Never happened to me.. You'll still be able to login, free up some space to get the services up again, and then resize your disk if that's needed.
For example, Google says that by default ext4 will reserve 5% of disk space.
So depending on your system, a “100% full” drive might still have a (sometimes significant) bit of space left.
Earlier quoted context omitted.
Because they wouldn't need to shut down factories if they had bigger stock of parts on site.
I wonder, wouldn't it be more of a question of how much later to shut down. Or in other words, how big is the time buffer you get for not being "just in time"? The article suggests (the way I read it, at least) that it is some fundamental time span, but I feel like it's more like half a day?
The order for a seat or mirror or door handle doesn't exist at the tier 1 suppliers where my equipment gets installed until 10 hours before it is needed. At that point, my PLC gets a request to induct a particular part number and paint color into the manifest, inducts it and acknowledges that request, the machine builds it, laser-marks a serial number onto it, tests it, uploads the test results with serial number to the database, packs it out into a foam-lined box or a dedicated nest and uploads the box barcode to the database, that box gets loaded onto a pallet, the pallet into a trailer, the trailer drives 20 minutes away to the OEM, and the trailer gets unloaded (in reverse order; truck size and the resulting last-in-first-out queue is one of the main drivers for JIT lifetimes) so the parts land at the assembly line just a couple hours before the vehicle they belong to is ready to receive them.
You'll notice that this does not leave a lot of wiggle room for anything to go wrong. When I'm physically a 5 hour drive away from the plant, it's not like I can drive to the site, debug a wiring issue, order a replacement widget online - even by UPS Next Day Air Early A.M. - and then install it on-site before holding up literally millions of dollars worth of production. And my little mirror line is just one of hundreds of parts that need to arrive on time.
Earlier quoted context omitted.
There was probably an array with a few dozen terabytes to spare and the guy made you run back to him once a month for some misguided job security purpose.
The audit department at my current gig says all records must be retained for eternity because of regulatory reasons but cannot direct anyone to the relevant regulation.
Earlier quoted context omitted.
> They have no time for development hipster nonsense https://support.microsoft.com/en-us/windows/windows-xp-suppo... > extraction games for unwanted features https://www.theverge.com/2022/7/12/23204950/bmw-subscription...
Funny when you never touched a computer in 20 years and as soon as microsoft posts "Support ended" it suddenly is a problem, when in fact, nothing changed. Computer still send signals and recieves signals just fine.
Yes, this is in fact the problem which gets exploited and said exploits remain unfixed because it's EOLd.
Earlier quoted context omitted.
> They have no time for development hipster nonsense https://support.microsoft.com/en-us/windows/windows-xp-suppo... > extraction games for unwanted features https://www.theverge.com/2022/7/12/23204950/bmw-subscription...
> If you continue to use Windows XP now that support has ended, your computer will still work but it might become more vulnerable to security risks and viruses It only matters if the machine is online, and they often aren't.
This was NOT my experience while working in the automotive industry.
I was responsible for some dev ops stuff at a state's health department and one of the more infuriating things about working at that place was that it was like pulling teeth getting more storage allocated. Our backups would be running out of disk and they'd allocate me 50 or 100 GB at a time. I'm sure someone Toyototian was yelling that this was going to happen for the past 6 months.
I'm just here to admire the fact that a Google search for "Toyototian" results this 1 hour old comment.
I was responsible for some dev ops stuff at a state's health department and one of the more infuriating things about working at that place was that it was like pulling teeth getting more storage allocated. Our backups would be running out of disk and they'd allocate me 50 or 100 GB at a time. I'm sure someone Toyototian was yelling that this was going to happen for the past 6 months.
We had an on-prem server at a new factory I was working at and less than a year in the whole thing shut down because we ran out of disk space for logs so none of the automation could successfully report back that they completed tasks to move to the next task. It turns out it was apparently terabytes of unallocated disk space on the server, so it was a quick fix but just felt so avoidable.
Earlier quoted context omitted.
I worked with an admin like that. We had a huge cluster, but he was greedy with the storage space for a service that was critical for the operation of the org. And I get that this is a good mindset for not wasting space overall, but if a single backup fills 90% of your storage space in test use, that machine is not ready for production. And we are not talking about a lot of space here. The backup was maybe 30 Gb the…
Having been on both sides (admin and developer), developers are notoriously bad at estimating how much space they need. You can't give them carte blanche to the storage because they'll waste it and consume as much as they're given without a thought to conserving it. And then when you put limits in, they'll whine and complain until they get what they want. Being an Artifactory service provider for a large IT dept gave…
They set all applications to "debug" level logs in production and were generating multiple gigabytes of logs per hour.
They wanted 90 days retention, and the ability to do advanced searching through the live log data so they could debug in production (they didn't really use their dev or stage environments, or have a process for documenting and reproducing bugs).