It's not comparable, Microsoft have been trying, and failing, to push out ReFS for six years and fall back to the safe default which is is NTFS. Apple is forcing users to go to Apple File System whether they like it or not.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
APFS Bug in macOS High Sierra Can Cause Data Loss When Writing to Disk Images
- Thread starter MacRumors
- Start date
- Sort by reaction score
Yeah Mike is good and lots of people swear by CCC, but I still prefer Superduper! and think it's safer
You converted all the disk images to sparse APFS, then what? Very curious what would trash the drive.
APFS is only for SSD, remember.
Color me another one of those absolutely not 'upgrading' to High Sierra until I absolutely have to. I make my living using Macs. An unexpected loss of data like this one that could propagate to my multiple backups could wipe out my livelihood.
I'll note again that Apple's MacOS quality has declined. It has to be a management issue. It can't be a resource issue - the company has nearly one-quarter trillion dollars in cash or cash equivalents. The annual investment yield of just 5% of that resource would support literally thousands of QA engineers - as a tax-deductible expense - forever. WTF, Apple?
I'll note again that Apple's MacOS quality has declined. It has to be a management issue. It can't be a resource issue - the company has nearly one-quarter trillion dollars in cash or cash equivalents. The annual investment yield of just 5% of that resource would support literally thousands of QA engineers - as a tax-deductible expense - forever. WTF, Apple?
No. Time Machine does use sparse images, but doesn't use APFS.
break in HS
I know... I'm counting all the 'major' isses that are piling up as we speak
I know... I'm counting all the 'major' isses that are piling up as we speak
I've been dealing with this same issue, however, I'm still using Sierra, not HS. Began right after Sierra update.
Unlikely. I’ve been using two NAS for time machine backups for years, long before high Sierra, and have had this issue on and off for that while time. It hasn’t happened to me for about 6 months, though. It seems updates to synology’s operating system and macOS have stabilized the issue for me.
Also, it is unlikely that you are using APFS images for time machine targets on your NAS. More likely these are still HFS+.
Huh? I thought it was only SSDs... not HDDs, and not Fusion Drives.
My installation of High Sierra certainly didn't convert the existing filesystem to APFS.
Generally everything goes wrong with me, and I haven't had any issues with High Sierra, even on my old Mac Pro. But if I did video work or something where I don't just have easy cloud backups of everything, I'd stay the heck away from AFPS for a while so people can work out bugs like this.
P.S. My work-only laptop is on a very conservative upgrade cycle of staying on the oldest OS that has both Xcode support and security updates. And security updates seem to go back to El Capitan.
Last edited:
I’ve been using OS X/macOS since version 10.0.0 and there sure has been problems in many of the major versions previously too.
OS X 10.2 (the first usable version, speed wise?) had an issue that caused the loginwindow process to crash in certain scenarios which immideately throwed you back to the login screen causing all your non-saved work to be lost. Wasn’t fixed until OS X 10.3.
OS X 10.4 had an issue when browsing network shares that could cause a kernel panic. Wasn’t fixed until OS X 10.5.
OS X 10.5 got a bug in one of its updates (I think 10.5.2 or so) which corrupted a photoshop file (not sure if it also affected other file types, but I think so) the second time you attempted to save it on a network share. Was fixed in the next dot update this time, but still.
Just a few examples I remember from the top of my head.
High Sierra is in fact very stable and quite fast for me, overall.
Last edited:
Same here. Until 2020 at least or maybe I'll wait until macOS 10.20.
Funny (...or not), just yesterday I got several freezes and my Mac mini with High Sierra wouldn't boot any more. Going into recovery and Disk Utility gave the message "error: apfs_extentref: btn: invaldid o_oid (0x0)". Nothing to be done I understood. Pulling out the SSD and connecting it to a HFS+ Mac was no use since it can't read APFS.
So I had to use the Terminal to back up important stuff to an external drive. Reinstalling Lion which was booed out when it came actually seems quite fast and stable in comparision. Will have to update to Mavericks for software compatibility though, maybe El Capitan for Hardware compatibility. Would maybe install Sierra but never again High Sierra due to the file system.
oh boy..another embarrassing bug in a operating system that used to be solid and extremely reliable..(years ago)..
I hate High Sierra and also Sierra..both slowed down my 2016 retina MacBook and I just regret updating to this awful version.
It's been a while..I'm looking into downgrading and will NEVER upgrade OSX again.
bugs aside,I have no doubt Apple is deliberately slowing down Macs too, just like the embarrassing leak about iPhones..they do it with Macs too.
I hate High Sierra and also Sierra..both slowed down my 2016 retina MacBook and I just regret updating to this awful version.
It's been a while..I'm looking into downgrading and will NEVER upgrade OSX again.
bugs aside,I have no doubt Apple is deliberately slowing down Macs too, just like the embarrassing leak about iPhones..they do it with Macs too.
You DO realize, of course, that a "Memory Leak" is a SOFTWARE issue, NOT a hardware one, right?
[doublepost=1519075345][/doublepost]
You had a bad "stick" of Hynix RAM. Nothing more, nothing less.
[doublepost=1519075652][/doublepost]
Only on EVERY iOS device for TWO major revisions.
You think that's enough "units" for you?
[doublepost=1519075834][/doublepost]
And you think Microsoft and the Linux Distros don't do the same thing? EVERY OS has bugs that seem to go on and on. This one is reportedly already fixed.
[doublepost=1519076363][/doublepost]
Oh, GOD no!
Sigh...
No HARDWARE that isn't running on the Starship Enterprise can detect/prevent/repair it when SOFTWARE doesn't know how to properly use malloc or whatever it is called in a particular computer language. Releasing unused blocks of memory (or rather, forgetting-to) is what causes a "Memory Leak", which is the gradual decline in FREE MEMORY as time goes on, sometimes because a process/thread crashes, and the OS doesn't reclaim the memory, and sometimes, like with certain versions of Safari, because the Application doesn't "flag" unused blocks of memory as being "purge-able", like when you close a browser Tab.
[doublepost=1519076567][/doublepost]
You can thank Oracle for all that.
This is an old problem with time machine. The verification often fails and after n failures time machine requires to make a new backup. Not only is the history lost. While the new backup is created, there is no backup at all.
BTW. During verification I loose WiFi every couple of minutes. I have to disable Wifi an reable it again to keep on working.
The user is suspended, but to anyone wondering, memory leaks are software bugs that have nothing to do with faulty memory.
[doublepost=1519077668][/doublepost]
Geez. If so, all TM backups are hosed. Good thing I almost never update my server.
Ask Oracle. They ruined it for Apple by dicking-around with the licensing.
After Oracle bought Sun and as a bonus, inherited ZFS, Apple got worried that Oracle could take ZFS completely private at any time, and so they decided not to bet the farm on it for the next 20 years or so...
Again, get this straight: You had some bad/out-of-spec Hynix RAM. You bought some non-bad/correctly-specced Micron RAM.
Glad you're happy now. But NEITHER of those two RAM samples were "leaky". (rolls eyes)
But please don't make yourself look like an idiot by trying to talk authoritatively about things you simply don't understand.