My old job was a company with less than 20 people. So, running the server fell to me. As such, that meant I left it running 24/7 with no shutdowns over weekends.
For the computers in my own area, I did the same. Full power, no sleep, apps left open, server shares connected. I wanted and expected to walk in each day, tap the spacebar and pick up exactly where I left off.
With the Mavericks SMB bug, that became a very irritating issue. Mavericks has the first implementation of SMB2. The server was running SMB 1 and 2 and so were the PCs in the office. But because of whatever Apple did, once you connected a Mac running Mavericks to a server share, you had a 24-hour window of use. Once those 24 hours were up, using the share was not possible.
The MP would maintain a connection, but you could only open files. The system threw an error if you tried to save a file. In the case of InDesign, this meant that the moment you tried to save, the program would just quit. No dialogs, no error messages, just boom - ID closed.
I'm in the habit of saving my work constantly and consistently, but whether I lose a lot of work or a little, having the app just quit on me was highly irritating. At first I thought it was InDesign, then I saw that other apps were throwing up errors as well. So, I tried disconnecting shares and then connecting again. And the problem repeated itself. The only solution was to restart. I found out later that restarting was what actually reset that 24-hour connection clock.
So, having to restart every day kind of defeats the purpose of leaving your computer on and running, right? I had multiple shares to connect to on startup, so this was very infuriating. And some apps depended on certain shares already being connected! I tried everything on the server side with Active Directory and Computer Policy, etc. Nothing worked.
It's only when I stumbled upon someone else who had the EXACT problem I did with InDesign that I found out there was a bug. They specifically stated that their problem was an SMB bug in Mavericks. The ONLY workaround was to force SMB1, which meant connecting via CIFS:// and not SMB:// Which, of course, defeats the purpose of using SMB2 at all right?
AFAIK, Apple never fixed the issue until the next macOS launch. But there you go. The Mavericks SMB bug means you cannot be connected to a server share for more than 24 hours. You then are forced to restart in order to reset the timer.
Most people shut down before they leave work, so never had any idea. I didn't, I don't now, and I won't in the future unless directed to do so. So this bug was a real problem for me.
Google's AI. But the problem is well known, just search…
View attachment 2458782