3 ms·

Have you ever considered the possibility that your storage medium or random access memory is corrupt?

by jjawssd 10y ago

bangonkeyboard 10y ago
The Mac has passed the hardware diagnostics at the Apple Store multiple times. The components are unchanged from Yosemite, which did not have these issues. The OS has been freshly reinstalled, with the same problems. This is also just one of a myriad of issues that have plagued the OS. Sierra has introduced me to new and wonderful ways to fail: http://i.imgur.com/HbVLWDq.png http://i.imgur.com/HbVLWDq.png
- evmar 10y ago
  If git is failing due to a system-wide file limit, that would explain why other programs are also failing. Perhaps some process has gone mad with creating files and if you find and delete those it will help things recover. (I agree with your general point -- just trying to be helpful in getting your computer back working.)
  - bangonkeyboard 10y ago
    I reached the same conclusion, and the prime suspect in my investigations is Safari 10. However, once the system has hit the file limit, it never fully recovers without a reboot.
- extra88 10y ago
  Google "too many open files" and you'll find posts about OS X but also Linux. Could it be git itself that's hitting a limit? Maybe you're hitting the shell's ulimit, not the system's per process or per-system open files max.
alexpoulsen 10y ago
What year and ssd/hd? I've had no problems except a couple programs that had broken features for a few weeks.
antspiders 10y ago
Yeah, pretty much this. If you get macOS to pop out an error that it can't find Finder (especially on 10.11>, which has SIP), you dun pretty goofed. macOS (especially with SIP) is by far the most stable of the big three OSes. Windows its shortcomings are known, but as far as Linux goes (numbering is only for clarity): 1. No default power management. Why isn't TLP installed and activated by default on systems that are known to work with it? Macbooks get 12-13h on macOS vs 5h on Linux. The XPS13 gets 22h on Windows vs 11h(!) on Linux. Ubuntu 16.04 on my MBP 13" 2015 gets 7h with TLP and Powertop configured, so even with those tools there's still a very large discrepancy. 2. Package hell. Yes, shared libraries have advantages. No, they don't outweigh the benefits of containerizing. By now (with 'Snappy Packages' and 'Flatpak' getting bigger) its finally getting fixed, but still. 3. There is no unified repo, and no unified package manager. There's Pacman, RPM, apt, etc. etc. and if you switch distro's you have to re-learn. Now I understand that this is due to each distro being like a micro-country, but imagine this: 3x3 unified repos (free, non-free and community) each with 3 levels (bleeding edge, testing, stable). All distros could(would) tap into these repos, so you combine the efforts of every distro its maintainers. Same for the package manager development. For distro-specific stuff the distros could just use a separate repo 4. UI. There's 2 different UI toolkits (QT and GTK) that both are configured differently, behave slightly differently and thus something (usually the QT apps since GTK is used more often) feels 'off'. This split also gives issues with scaling sometimes. macOS does this perfectly with pretty much everything using Cocoa and having all options on the menubar. Saving is always under 'file', and 'file' is always in the same location. Same for 'Edit', 'View', etc. So far only Ubuntu replicates this, and they do it for a good reason. And those are only a few of my pet peeves. Here's a full list by someone that has much better knowledge of Linux than me. Quite staggering really.[0] [0]https://itvision.altervista.org/why.linux.is.not.ready.for.the.desktop.current.html https://itvision.altervista.org/why.linux.is.not.ready.for.t...

Have you ever considered the possibility that your storage medium or random access memory is corrupt?

by jjawssd 10y ago

Have you ever considered the possibility that your storage medium or random access memory is corrupt?

The Mac has passed the hardware diagnostics at the Apple Store multiple times. The components are unchanged from Yosemite, which did not have these issues. The OS has been freshly reinstalled, with the same problems. This is also just one of a myriad of issues that have plagued the OS. Sierra has introduced me to new and wonderful ways to fail: http://i.imgur.com/HbVLWDq.png http://i.imgur.com/HbVLWDq.png

evmar 10y ago
If git is failing due to a system-wide file limit, that would explain why other programs are also failing. Perhaps some process has gone mad with creating files and if you find and delete those it will help things recover. (I agree with your general point -- just trying to be helpful in getting your computer back working.)
- bangonkeyboard 10y ago
  I reached the same conclusion, and the prime suspect in my investigations is Safari 10. However, once the system has hit the file limit, it never fully recovers without a reboot.
extra88 10y ago
Google "too many open files" and you'll find posts about OS X but also Linux. Could it be git itself that's hitting a limit? Maybe you're hitting the shell's ulimit, not the system's per process or per-system open files max.

alexpoulsen 10y ago

What year and ssd/hd? I've had no problems except a couple programs that had broken features for a few weeks.

antspiders 10y ago

Yeah, pretty much this. If you get macOS to pop out an error that it can't find Finder (especially on 10.11>, which has SIP), you dun pretty goofed. macOS (especially with SIP) is by far the most stable of the big three OSes. Windows its shortcomings are known, but as far as Linux goes (numbering is only for clarity): 1. No default power management. Why isn't TLP installed and activated by default on systems that are known to work with it? Macbooks get 12-13h on macOS vs 5h on Linux. The XPS13 gets 22h on Windows vs 11h(!) on Linux. Ubuntu 16.04 on my MBP 13" 2015 gets 7h with TLP and Powertop configured, so even with those tools there's still a very large discrepancy. 2. Package hell. Yes, shared libraries have advantages. No, they don't outweigh the benefits of containerizing. By now (with 'Snappy Packages' and 'Flatpak' getting bigger) its finally getting fixed, but still. 3. There is no unified repo, and no unified package manager. There's Pacman, RPM, apt, etc. etc. and if you switch distro's you have to re-learn. Now I understand that this is due to each distro being like a micro-country, but imagine this: 3x3 unified repos (free, non-free and community) each with 3 levels (bleeding edge, testing, stable). All distros could(would) tap into these repos, so you combine the efforts of every distro its maintainers. Same for the package manager development. For distro-specific stuff the distros could just use a separate repo 4. UI. There's 2 different UI toolkits (QT and GTK) that both are configured differently, behave slightly differently and thus something (usually the QT apps since GTK is used more often) feels 'off'. This split also gives issues with scaling sometimes. macOS does this perfectly with pretty much everything using Cocoa and having all options on the menubar. Saving is always under 'file', and 'file' is always in the same location. Same for 'Edit', 'View', etc. So far only Ubuntu replicates this, and they do it for a good reason. And those are only a few of my pet peeves. Here's a full list by someone that has much better knowledge of Linux than me. Quite staggering really.[0] [0]https://itvision.altervista.org/why.linux.is.not.ready.for.the.desktop.current.html https://itvision.altervista.org/why.linux.is.not.ready.for.t...