A NAS will use a network file protocol (SMB/NFS/AFP/SFTP etc) to access data rather than direct disk access, so the types of failures are different. Generally you don't really have to "eject" but disconnecting during a large transfer can cause incomplete writes.
The main risk with directly attached storage is that most kernels will do "buffered writes" where the data is written to memory before it's committed to disk. Yanking the drive before writes are synced properly will obviously cause data loss, so ejecting is always a good idea.
Generally, NAS is a bit safer for this type of storage because the protocols are built with the assumption that the network can and will be interrupted. As a result, things are a bit slower since you're dealing with network overhead. So, like everything, there are some trade-offs to be made.
Yeah, this is textbook "shadow IT" that could easily lead to something going seriously wrong. It's a fun example, but not something to aspire to.
Ultimately the problem is that in a lot of big corps, IT is basically unaccountable for setting things up wrong. Their only KPI is tickets closed, not the quality or success rate of their fixes.
I've always felt that if business types can get over their fetish for trying to measure absolutely everything, we wouldn't have problems like these that stem from poorly thought out KPIs.
They default to tickets closed, uptime, SLA adherence as KPIs because you can't effectively measure "is it set up correctly?" and because the business absolutely must measure everything, they come up with bullshit KPIs so they can have a pretty dashboard and pretend like they're actually managing.
Glad I'm no longer in huge corps, but still an IT manager. Shadow IT is a direct symptom of IT not providing the right tools or having poor processes. But responsibility still lies higher up in the chain. If we weren't forced to quantify all activity, these issues wouldn't exist.
Ticket closing and KPI chasing is alive and well in small companies too. I have a client (less than 100 folks) that has a JIRA reporting process on par (and as bad as) as F500 company.
Seems to geared towards tracking work and increasing accountable behavior.
But then the consultant overseeing it (not me) sent a Claude generated report with some sort of JIRA ticket dump as input. All the tickets closed were in fact not done or not relevant. But they were “closed” in JIRA. Same thing with completed tickets.
Embarrassing work product and embarrassment for the company.
Chopping the plug is a very good idea, everybody should practice that.
I once had a recurring problem with patch cables between workstations and drops going bad, four or five in one area that had never had that failure rate before. Turns out, every time I replaced one somebody else would grab the "perfectly good" patch cable from the trash can beside my desk. God knows why people felt compelled to do that when they already had perfectly good wires, maybe they thought because it was a different colour it would make their PC faster... So, now every time I throw out a cable that I know to be defective, I always pop the ends off. No more "mystery" problems.
When cost and reliability is no concern, you can do truly crazy things...
> 2.0-liter boxer engine ... 670 horsepower and 680 lb-ft of torque
Those are V10 numbers coming from something the size you'd find in an econo-box.
Obviously unlike your Camry this thing is not going to do 300,000 KMs over its lifetime, and will be rebuilt frequently. This is the extreme end of the engineering tradeoff, and it's interesting to see what happens when the scale tips all the way over.
2 liters is hardly econobox, even without a turbo. A new honda civic sedan is 1.3 liters (NA). 2.0 is more typical for sedans imho. The 2.0 turbo in this biuld originally turned 250+ hp (wrx) which is well beyond econo anything.
That was a big thing with Japanese sports cars in general: proving more cylinders was a dead end and just extra weight. Pretty much all of the big JDM classics of the 90s and 2000s are 4-cyl (aside from Mazda's rotary engine cars) putting down 200-300hp range with favorable power/weight.
I can't think of any from the 90s that weren't 6 cylinders. Nissan 300Z, Nissan Skyline GT-R, Honda/Acura NSX, Toyota Supra, and Mitsubishi 3000GT VR-4 were all 6 cylinders.
The only exceptions I can think of are the Subaru Impreza WRX/STI, and the Mitsubishi Lancer Evolution.
A majority of those made in the ballpark of 150hp or less, with the exception of the S2000. A few variants of the MR2 and the Nissan made over 200, but not many.
None ever came near Japan’s gentlemen’s agreement of “276” hp.
Sure, if you completely disregard the legendary straight sixes from Toyota and Nissan (RB, JZ...). I agree 4 bangers are huge historically in JDM sports cars, but so too is the straight six - the classic Z cars, Supras, GT-Rs...
Heh, very true. These days most new cars have a 1.0-1.5 turbo (or hybrid) rather than a larger 2.0 NA. And even 20 years ago most European cars were around 1.5 or less because of their higher fuel prices and registration taxes.
I'm a bit spoiled with the beefy 2.5 in my Mazda... Though it's still about 480 HP less than this beast ;)
It's funny, because it's also one of the most "gotcha-filled" things you can do. Click the wrong box, and they'll stick you in a seat with no leg room or make you pay extra for a carry-on bag. I have very little confidence that an AI would be able to make the "correct" choice on an airline ticket consistently without making a rather impactful mistake.
It will work for a while and then the airlines will game their systems against AI agents just like they currently do against consumers.
It's just a temporary solution. A real solution would be for laws to force them to not do this. But airlines are often very intertwined with the state and a prestige thing for a country.
All you need to know about Toronto is that the generational effort to build a raccoon-resistant trash can has failed every time. They're unstoppable beasts!
It seems it's presently only still here because of previous inefficient irrigation (from the Colorado River) and that farmers restricting their water usage is actually leading to the Salton's decline.
Not just inefficient, it was a large scale industrial accident. A canal wall was breached and not repaired for two years and the runoff all collected in this low lying area. It’s a very odd place to visit now though for marketing reasons they tried to make it into a resort destination before it became a place you can only tolerate for a very short time.
I was visiting Palm Springs one year, late summer. I had assumed that since it was in the middle of the desert, that water use would be regulated.
But as I drove around over there, I was shocked to see massive lawns being watered in the middle of the day, and large amounts of water just flowing out from these lawns into the drains. Sometimes the giant sprinklers were watering the sidewalks and roads too.
What a waste of water! Speaking to a local, they claimed that due to some old water rights agreement, Palm Springs gets its water for really cheap and there is no incentive to conserve it. Sad state of affairs.
The whole system is a mess. As wasteful as it can be, all residential use is only a small fraction of water consumption in this region. An order of magnitude more is used to grow water intensive crops in the SW deserts, and those farmers are only paying on average 1/10th the price per gallon for that same water as people pay for their home use. In many cases the farmers are incentivized to not be more water efficient, because the old water rights can be use it or lose it. They are essentially being paid to waste obscene amounts of water.
Municipal use and waste get the most attention because they are by far the most visible use, but most policies there are just tinkering around the edges and hardly move the overall numbers.
Not Palm Springs but close enough, reporting in for the curious. I've been wastelanding for a few years now in an unincorporated rural township, lucky to be close to allegedly sweet aquifers, but the utility is definitely mismanaged to the extent that it's pretty doubtful if anyone really knows how much water there is. Gold-mining interests are not far away (hello arsenic?), lithium interests are probably looking for an angle. I'm no geologist but maybe an endorheic basin that collects the sweet stuff is good for that too. Anyone think any of this water is being tested with a dismantled EPA?
Anyway a water bill is about $40/month up to 8000 gallons, $3 extra per 1000g overage. About half of the base rate is claimed as "upgrade surcharge". Since it's practically unlimited for free, does that sound right to anyone? The neighbors seem to be feral ghouls about 200 years old, they definitely don't care much about any poisons or the town drying up and blowing away, so they are always YOLOing a honking great deluge of whatever juice is still left into all different kinds of stupid inappropriate leafy greens but fuck it, you know? The pentagon is looking to restart nuclear testing in the backyard anyway so those of who still aren't irradiated yet can look forward to that!
The Salton Sea is drying up due to _decreased_ agricultural water consumption in the area; it was formed by agricultural run-off, which is why it's so toxic, and now there's less runoff to fill it up.
No, its lifespan was extended by agricultural runoff offsetting the natural drying out which would have otherwise occurred after the event which formed it was corrected, but it was formed by a breach in an irrigation canal that occurred in 1905 and wasn't repaired until 1907.
Regardless, it's sort of a bad example of "humans are the virus" type thinking, since it both lived and died by agriculture.
If you really dig into the story there is an interesting commentary about the horrible Western US water rights compacts system and the continuing inability for US states, especially in the West, to accurately price water consumption in a way that makes consumers sensitive to inefficient water use. But even then, in the case of the Salton Sea, the system actually did work: inefficient agricultural use was "improved" when San Diego called for more water and farmers were forced to be more efficient. Perhaps in an ideal world those farms would never have existed at all.
> it's sort of a bad example of "humans are the virus" type thinking, since it both lived and died by agriculture.
from "Islands of Abandonment":
> As I get further out, my feet sink deeper into the thin, grey sand. When I look closer, I see it is not sand at all, but the dry bones of fish, pounded into shards, and the tiny, skull-like husks of barnacles. This is a foul place. The air is thick with brine and guano and decomposition. Even now, in the violet dusk, the heat is oppressive. But as I cross the crystallised flats, the water gleams into view, an impossible sea in the middle of the desert.
> It is a poison lake whispering sweet nothings. It promises cool succour, quenched thirst. Despite what I know of this shimmering mirage - despite the stink and the rot and the waste that surrounds it, despite the staring eyes of the dead and desiccating fish that litter its shrinking shores, despite the absence of vegetation - I can’t help but quicken my pace. I stumble through sucking mud towards this false vision, on and on until the muck is over my feet, and up to my ankles, and I am shin-deep in a warm broth that, when stirred, releases a draught so stagnant I can taste it.
Seems like an excellent example of "humans are the virus" to me. Human error created an entire lake and then human inefficiency sustained it (for a while). Now the end product of all of that human activity is poisoning the air around it.
That was exactly the goal with the Buffalo Bicycle project, and I'd say it worked pretty well. Make a bike that's mechanically simple & reliable, maintainable with common tools, and train technicians to fix and upkeep them. Basically create the Toyota Landcruiser of bikes. I kind of want one, even though it's a "bad" bike by the standards of most western audiences (heavy, slow, ugly, etc)
Nextcloud, and before it Owncloud, have been "in production" in my household for nearly a decade at this point. There have been some botched updates and sync problems over the years, but it's been by far the most reliable app I've hosted.
In terms of privacy & security, like everything it comes down to risk model and the trade-offs you make to exist in the modern world. Nextcloud is for sharing files, if nothing short of perfect E2EE is tolerable it's probably not the solution for you, not to mention the other 99.999% of services out there.
I think most of the problems people report come down to really bad defaults that let it run like shit on very low-spec boxes that shouldn't be supported (ie raspi gen 1/2 back in the day). Installing redis and configuring php-fpm correctly fixes like 90% of the problems, other than the bloated Javascript as mentioned in the op.
End of the day, it's fine. Not perfect, not ideal, but fine.
It's much easier to reason about when you frame it closer to reality: you're not on a circular path, you're continuously falling, and because you're moving forward, you're continuously missing the earth, with its pull decreasing with distance.
The main risk with directly attached storage is that most kernels will do "buffered writes" where the data is written to memory before it's committed to disk. Yanking the drive before writes are synced properly will obviously cause data loss, so ejecting is always a good idea.
Generally, NAS is a bit safer for this type of storage because the protocols are built with the assumption that the network can and will be interrupted. As a result, things are a bit slower since you're dealing with network overhead. So, like everything, there are some trade-offs to be made.
reply