Apple is Upgrading Millions of iOS Devices To a New Modern File System Today (theverge.com)
Apple today began rolling out iOS 10.3, the latest point update to its mobile operating system. iOS 10.3 brings with it several new features, chief among which is a new file system -- called the Apple File System (APFS). From a report: It's a file system that was originally announced at WWDC last year, and it's designed with the iPhone, iPad, Apple Watch, Mac, and Apple TV in mind. Apple has been using its 31-year-old Hierarchical File System (HFS) for iOS devices so far. It was originally designed for Macs with floppy or hard disks, and not for modern mobile devices with solid state storage. Even its successor, HFS+, still doesn't address the needs of these mobile devices enough. Apple's new APFS is designed to scale across these new types of devices and take advantage of flash or SSD storage. It's also engineered with encryption as a primary feature, and even supports features like snapshots so restoring files on a Mac or even an iOS device might get a lot easier in the future.
Sent from APFS
Hmmm...this actually sounds like a useful upgrade. Given Apple's recent "innovations," I'm left wondering what the catch is. There must be something in this update that screws over the customer somewhere.
In an interview at Melbourne's linux.conf.au conference, Linus Torvalds called the standard file system of Mac OS X "complete and utter crap." Mac fans are only slightly outraged, pointing out that HFS+ isn't really "complete and utter crap," rather, it's just slightly crap-ish.
On a personal level, I have had multiple corrupt HFS+ filesystems, one of which was unrecoverable. I tried switching to exFAT which also proved to be corruptible but repairable. Now I just store any data I care about on a NAS running a linux ext4 filesystem.
Hopefully, AFS will fix these corruption problems. I have been sending Apple upgrade suggestions for years. Looks like they finally got around to it. One filesystem to rule them all, but will it support upper/lower case?
Back in my day, a new filesystem would denote more than just a point release.
In the spirit of "what could possibly go wrong" this may actually be one of those times you want to back up your device before upgrading.
I am not interested in articles about life extension advancements.
I kinda would like my iPod Touch to be upgraded past 9.3. It's not really that old.
Kriston
Great! This is definitely on the list of things the computer industry needs more of!
1. Text editors
2. chat apps
3. web apps
4. Office program file formats
5. Filesystems
6. Linux distributions
7. Code style guidelines.
8. Types of serial ports.
9. Types of video ports.
Glad to see people tackling some of these.
Modern APP APPERS don't use any luddite filesystem to store their data. They use APPFS to APP their APPS in! APPS!
If you lose data due to a corrupt filesystem - it's not the filesystem's fault that you didn't backup your data.
Even if you had the most reliable filesystem in the world - it would, most likely be running on spinning disks or flash media - both fail quite regularly.
Backup your data frequently and test your backups regularly.
And we'll all have access to the file system from the native iOS UI right? Riiiiiiight?
Just because I can hook a shark from a boat, I do no offer to wrestle it in the water.
Will this add any security against NSA / Immigration trying to steal your data?
I'm wondering if this will affect known methods used by law enforcement to break into iPhones in high-profile cases (such as the San Bernardino shooting). Anyone have any insight as to whether the underlying encryption has an affect on those attack vectors?
Trying to avoid talking about whether it is a good or bad thing that police can break into iPhones when necessary -- just curious if anyone has any technical insight.
Don't trust Apple with your data. I expect to make a bundle with data recovery requests.
https://xkcd.com/927/
No, but it IS the filesystems fault for corrupting itself no? Nowhere did he say he blamed his harddrive or ssd, he blamed the filesystem. A valid complaint, so dont try to hand wave it away by blaming it on lack of backups.
See my subject & mark my words - it's ALL going to be diskbound but SSD ram diskbound that saves state & loads fast.
* REMEMBER I SAID THAT...
APK
P.S.=> It takes out a WHOLE LAYER of overheads (yes, SSD (for now) is SLOWER than system RAM, but not for long) of the File Open/Read-Write/Close-Flush cycles OFF DISK into RAM - you get disk as fast as RAM, especially when it saves state on disk? You don't NEED system RAM... apk
... let the bricking begin.
Oh, zfs! I remember it corrupting all my file systems while I was a university student. Maybe it was the Linux implementation, I don't know, but I'm never touching that fs again.
Also my NAS corrupted its file system more recently and guess which fs it was?
http://dtrace.org/blogs/ahl/20...
Even if you don't lose data, you still lose uptime. Backups are only one layer.
Oh, zfs! I remember it corrupting all my file systems while I was a university student. Maybe it was the Linux implementation, I don't know, but I'm never touching that fs again. Also my NAS corrupted its file system more recently and guess which fs it was?
I have been running ZFS for ~5 years now across ~40 servers. Never failed once.
I even had one particular server with 8 drives in a RAIDZ2 lose a drive while two others started failing. I replaced them all successfully. Less than 12 hours later two additional drives failed and a third started acting flakey. I replaced them all successfully. No data loss. I'll trust AUFS when I see it handle weird hardware BS like that.
There's no place like
I will never forgive you apple
...that argument once again, when you're not so quite drunk.
Yippee!
Maybe one of these years they will finally move to F2FS as the default for mobile devices. Apple finally added a new feature before Android had it.
Finder app comeing?
Been running it with FreeNAS for over a year on recommended hardware - Intel Xeon, 16GB ECC RAM, directly attached (No RAID controllers) HDDs. No problems.
What do you mean? Onion or cake layers?
#DeleteFacebook
The non-analogy type.
I'll second the observation. I have found ZFS (on both FreeBSD and linux) to be phenomenally reliable through several years. I have no worry at all when power failure hits my 75 TB worth of RAID-Z2 and RAID-Z3 storage pools using a total of 25 drives. I don't even bother with a UPS. Disclaimer - my pools are only occasionally written to; mostly read.
I've been posting with the 10.3 beta for months.
I don't plan on upgrading my iOS until they roll back the changes they made to email threads. The latest versions I literally can't follow what is happening in an email thread... why they felt the need to 'fix' something that wasn't broken is beyond me.
I have an iPad 2 which still works great. Since there is no fucking way for me to directly interact with the file system, what does it matter.? I can't plug a USB stick or MMC card into it. If I want to load a movie on to my iPad I've got to jump through obstacles and hoops to do it. When this bitch dies, it's going to be time for a Samsung or whatever. Anything but a control freak Apple piece of shit.
Apple is Upgrading Millions of iOS Devices To a New Modern File System Today
Sweet. Maybe I'll purchase some Apple crap now...
a new file system -- called the Apple File System (APFS)
Wait. I thought you said a 'modern file system'. You know....like ZFS.
Well, since APFS has been in development for only a year or so, and ZFS is like 10 years old at this point, I'd say that APFS is the more "modern" FS.
Oh, zfs! I remember it corrupting all my file systems while I was a university student. Maybe it was the Linux implementation, I don't know, but I'm never touching that fs again.
Also my NAS corrupted its file system more recently and guess which fs it was?
I have been running ZFS for ~5 years now across ~40 servers. Never failed once.
And I have run HFS and HFS+ since 1984 or '85, on several dozen machines. Never failed once.
Now what?
Sounds like it has some of the features of ZFS without being full blown ZFS. Sounds Apple-ly.
In other words, it functions the same way as copy-on-write filesystems such as Btrfs and ZFS, or log-structured filesystems such a various flash-oriented systems (F2FS and the likes) or as the venerable UDF.
Or thank you apple for finally having a filesystem that is not decades out-dated, but finally joining the club of other modern Unices.
I am just wondering why they needed to re-invent their own wheel, instead of opting for re-using ZFS.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
No, but it IS the filesystems fault for corrupting itself no?
File systems with a lesser tendency to corrupt themselves :
file systems that do not over-write themselves.
such as Copy-on-Write filesystems (Btrfs, Zfs, etc.) and Log-structured filesystems (F2FS, UDF, etc.)
according to source, APFS is also going to be copy-on-write, making it similarly more resilient to corruption.
(if system crashes or loses power mid-write, you don't end-up with a corrupted file system.
You end up with the previous version of the filesystem, plus new copies of data that may or may not be corrupted.
For those copies which are corrupted, you can trivially revert to previous copy)
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
Wait. I thought you said a 'modern file system'. You know....like ZFS.
You need to recalibrate your sense of time. APFS was announced last year and launched today. ZFS has been around for a decade or so at this point. I'd wager you couldn't name a production-ready filesystem intended for widespread use that's newer than APFS without doing a search for one.
To be clear, I have no problem with ZFS. It has its shortcomings and strengths, just like anything else. I'm considering using it with a NAS I'm looking at putting together (via UnRAID). But this suggestion that APFS isn't "modern" is preposterous, given that it's a ground-up filesystem written in the last few years, taking into account the strengths and drawbacks of most other recent filesystems.
I believe we have had those devices for some time now.
"I believe in Karma. That means I can do bad things to people all day long and I assume they deserve it." : Dogbert
A major problem with copy on write is that users can not scrub their data and that has to be done by a root user.
The Posix committee needs to get its act together and provide a F_OVERWRITE fcntl system call that says "when I write a block back to the disk for this file, put it in the same place".
As an example of why this is needed: /dev/sda
echo "123SomeMagic" >file
echo "XYZZY123" >file
grep "123SomeMagic"
You get the same results if you do a open, write, sync, seek 0, write.
dd if=/dev/zero of=file&rm zero; won't even scrub the data off the disk most of the time with ZFS, APFS or BTRFS. Encryption won't help either since the OS will happily give you a bunch of unencrypted blocks if you have the right privilege levels.
Worst case - I lose all of my data I think. I'll give it a week or two.
Reads like Timmy's Fuck'n File System.
Now all the porn shit on iCloud (HFS/HFS+) will be unreadable! Perfect solution to "encryption" in Timmy's Dime-Store Mind from KKK south Alabama.
Ha ha
You are confusing "new" with "modern". APFS may be an improvement on HFS, but Apple's choice to exclude end to end checksums was extremely foolish. At the bare minimum, a modern filesystem should guarantee the integrity of the data it stores. History teaches us that every layer of the storage stack is capable of corrupting data, and this corruption will propagate to backups if not detected. Every other filesystem designed since ZFS has taken this lesson to heart.
my 75 TB worth of RAID-Z2 and RAID-Z3 storage pools
My God! It's full of porn!
There's no place like
And I have run HFS and HFS+ since 1984 or '85, on several dozen machines. Never failed once.
Now what?
Have you recovered 100% of your data from a 6 our of 10 drives failing within a 48 hours window?
Can you yank the drives out of one machine, put them into a pile, and then randomly plug them into another machine and access your data?
Can you do that while the OS is running?
How about in the middle of writing data?
Without running chkdsk or fsck?
There's no place like
Apple uses premium storage media. It doesn't need to waste CPU cycles on stuff like that.
And I have run HFS and HFS+ since 1984 or '85, on several dozen machines. Never failed once.
Now what?
From wikipedia:
Apple File System uses checksums to ensure data integrity for metadata, but not user data.
I'm glad ZFS cares about the integrity of *my* data, not just its metadata.
There's no place like
Oh... so, parfait it is.
And I have run HFS and HFS+ since 1984 or '85, on several dozen machines. Never failed once.
Now what?
Have you recovered 100% of your data from a 6 our of 10 drives failing within a 48 hours window?
Can you yank the drives out of one machine, put them into a pile, and then randomly plug them into another machine and access your data?
Can you do that while the OS is running?
How about in the middle of writing data?
Without running chkdsk or fsck?
Can you boot from your ZFS drives?
CPU (especially for operations like XOR for checksumming) is basically free.
'Premium storage media'. I've worked for vendors in the enterprise storage space for the past 17 years or so. Even the most expensive drives still fail in spectacular ways, from the oops (you asked to write to block 64 but it actually wrote to block 2048, but only 1/billion operations, and that's silent corruption) to the catastrophic (flying height issues, bearing issues, oil issues).
SSDs, while much better, also have software (firmware) bugs and also media issues. Trusting the media is a bad idea.
Here be dragons... XIIV
If a filesystem is crap, I think I'll still blame the filesystem, thank you.
Onion or cake layers?
What do you have against brick?
Well, since APFS has been in development for only a year or so ...
Uh, actually, AFPS has been in development for several years.
Can you boot from your ZFS drives?
Yes. Is there some reason I shouldn't be able to?
There's no place like
Every other filesystem designed since ZFS has taken this lesson to heart.
So, I take it you're unaware of ext4? It's arguably the most wide-used filesystem designed since ZFS, but it doesn't support the end-to-end checksums you're talking about.
No matter how good your backups are, filesystem corruption still sucks. It's a failure mode that's basically impossible to detect and recover from automatically. I've never seen a filesystem corruption that wasted less than an hour of sysadmin time.
i use linux to back up my ios devices' photos and other stuff .. will that still work? i.e. does that read the filesystem directly or does it use some sort of file sharing protocol (e.g. nfs) that allows the ios device to present the same info to linux even if the filesystem format has changed.
Google posted a blog about SSDs vs spinning rust, and they say on average, SSDs can write as much data as spinning rust before failure, but SSDs are overall 1/2 as likely to fail in their work loads. The main difference if you can write data much faster to SSDs causing them to fail faster relative to a wall-clock but not faster relative to data written.
Not only can FreeBSD boot from a ZFS volume, but it can snapshot the boot volume, mount it in a Jail, run an OS upgrade in the Jail, point the bootloader to the new volume. Even roll-back if something actually went wrong.
I can't see the average person wanting to reformat just to upgrade unless there's something I'm don't know.
Well, since APFS has been in development for only a year or so ...
Uh, actually, AFPS has been in development for several years.
Citation, please?
Can you boot from your ZFS drives?
Yes. Is there some reason I shouldn't be able to?
News to me. When did they get that working?
That was one of the main reasons that Apple didn't adopt it back in the Leopard days, when they had that experimental ZFS driver running.
News to me. When did they get that working?
That was one of the main reasons that Apple didn't adopt it back in the Leopard days, when they had that experimental ZFS driver running.
Not sure if you missed my original post or what...but I don't use Apple crap *because* of the brain-damaged 'features'. Like APFS. I use ZFS on FreeBSD and occasionally Linux. Booting works fine from both, although FreeBSD has a nice polished installer to do it for you. In Linux it's a very manual process to set it up. As for ZFS on Apple? I have no clue. In two decades I only ever had one client that absolutely couldn't be switched from Apple to FreeBSD or Linux to achieve better results.
There's no place like
Look it up. It's been widely known (and reported here 3 years ago) that Apple was working on a new filesystem.
News to me. When did they get that working?
That was one of the main reasons that Apple didn't adopt it back in the Leopard days, when they had that experimental ZFS driver running.
Not sure if you missed my original post or what...but I don't use Apple crap *because* of the brain-damaged 'features'. Like APFS. I use ZFS on FreeBSD and occasionally Linux. Booting works fine from both, although FreeBSD has a nice polished installer to do it for you. In Linux it's a very manual process to set it up. As for ZFS on Apple? I have no clue. In two decades I only ever had one client that absolutely couldn't be switched from Apple to FreeBSD or Linux to achieve better results.
Well, I was simply asking when the ZFS folks got booting working, because it used to be a problem IIRC.
But since you can't hold a rational discourse with spewing Apple Hate, I guess we're done here.
Well, I was simply asking when the ZFS folks got booting working, because it used to be a problem IIRC.
It's been working fine on FreeBSD and Linux.
But since you can't hold a rational discourse with spewing Apple Hate, I guess we're done here.
Yeah, I hate apple. I have good reason to. I just listed one--they went with their own shit-tastic filesystem and last time I checked, they aren't open enough to boot from ZFS.
It may surprise you, but my work computer is a piece-of-shit Macbook Pro. I am forced to use it by policy. It's *terrible*. If I don't fit the 'Apple mold' and just use brain-dead point-and-click applications all day, I end up with segfaults, performance problems, and out-of-memory issues. Hell--vim segfaults 2-3 times per hour on my Macbook. I've never seen that on Linux or FreeBSD. I measure my Macbook uptime in hours, my Linux uptime in months, and my FreeBSD uptime in years.
So yeah--I have a *lot* of hate for Apple products. All it took was using a Macbook Pro for ~3 months in my life, and a newly issued iPhone S (for evaluating an iOS app) for the last week. You might not like the hate, but it's absolutely justified hate. And since this is about filesystems and Apple just released a product that screams "we wanted ZFS, but not-invented-here" that doesn't checksum user data...well...one more reason to hate Apple products.
There's no place like
Well, I was simply asking when the ZFS folks got booting working, because it used to be a problem IIRC.
It's been working fine on FreeBSD and Linux.
But since you can't hold a rational discourse with spewing Apple Hate, I guess we're done here.
Yeah, I hate apple. I have good reason to. I just listed one--they went with their own shit-tastic filesystem and last time I checked, they aren't open enough to boot from ZFS.
It may surprise you, but my work computer is a piece-of-shit Macbook Pro. I am forced to use it by policy. It's *terrible*. If I don't fit the 'Apple mold' and just use brain-dead point-and-click applications all day, I end up with segfaults, performance problems, and out-of-memory issues. Hell--vim segfaults 2-3 times per hour on my Macbook. I've never seen that on Linux or FreeBSD. I measure my Macbook uptime in hours, my Linux uptime in months, and my FreeBSD uptime in years.
So yeah--I have a *lot* of hate for Apple products. All it took was using a Macbook Pro for ~3 months in my life, and a newly issued iPhone S (for evaluating an iOS app) for the last week. You might not like the hate, but it's absolutely justified hate. And since this is about filesystems and Apple just released a product that screams "we wanted ZFS, but not-invented-here" that doesn't checksum user data...well...one more reason to hate Apple products.
You've got something hardware-related wrong with that MacBook.
I have had exactly ONE Kernel Panic (what you are incorrectly calling a "Seg-fault") in my years of running OS X/macOS (and that started with OS X 10.0.0; so MANY years), and that was some Freeware "scanner driver" that was a POS. An Unhandled Interrupt if I had to guess.
The only other time I had KPs (and a LOT of them!) was when I bought some dodgy memory for a G5 tower that wasn't up to spec. Hardware Test figured that one out. I replaced the RAM, and not one other KP, ever.
And before you say that is because all I use are "approved", "safe" applications, then perhaps you should look to the quality of the APPLICATIONS, and stop blaming the PLATFORM. If you search for "vim crash os x", you will find a long and storied history of that simple Editor being an unstable POS. Don't think it's the Mac's fault. It's a fucking EDITOR, FFS! Just one that has an issue that no one has bothered to track down and fix.
Howabout you?
You've got something hardware-related wrong with that MacBook.
Apple's own diagnostics tools say the hard drive and memory are fine.
Apple's own techs (the company shipped it off to Apple) say it's fine.
I have had exactly ONE Kernel Panic (what you are incorrectly calling a "Seg-fault")
Nope. I'm not incorrect. The kernel has never panic'd on my Macbook. But lots of applications (like 'vim') will suddenly dump me back to the command line with a segfault message.
And before you say that is because all I use are "approved", "safe" applications, then perhaps you should look to the quality of the APPLICATIONS, and stop blaming the PLATFORM. If you search for "vim crash os x", you will find a long and storied history of that simple Editor being an unstable POS. Don't think it's the Mac's fault. It's a fucking EDITOR, FFS!
Weird. Vim workes perfectly for me on Linux, FreeBSD, and Windows. No crashes. Must just be a Mac thing.
...but I will say one nice thing about Apple...they do appear to take user privacy *very* seriously when compared to Microsoft and Google. If they could just fix their retarded interface and brain-damaged ideas about doing thing 'differently' for the sole purpose of appearing different than Microsoft...I would consider buying it.
Anyways, the Mac may be perfect for you. It's definitely not for me. Ignoring the constant crashing for a moment, nothing is more intuitive to me than having to remember CTRL+T opens a new tab on Linux, FreeBSD, and Windows...but for the elitist Mac platform I have to shift my finger over and hit APPLE+T.
Or how about Linux, FreeBSD, and Windows using the home/end keys go to the beginning and end of a line. But the elitist Mac platform scrolls to the beginning and end of a browser window, document, etc...
Or how about the weird Mac Mail issues where it absolutely refuses to show the status of a SMIME signed or encrypted message?
Or how about turning on an Android phone without a SIM card and being able to instantly begin to use it for developing apps? But the elitist Mac platform absolutely requires you to activate the iPhone with a SIM card, followed by the requirement to set up a valid credit card before installing a *free* application from their store.
How about deploying tablets to fire, EMS, or police vehicles? With Google you simply sign up for Google Apps by entering some basic information, then provisioning the tablets. Done. In about 45 minutes. But the elitist Apple platform requires you to set up an account for volume purchasing. Oh, you already had an iTunes account? Sorry, that won't work. Create a new e-mail address and a new account. Then wait for all sorts of business verification (like your DUNS number) before you get access to an account that appears to have the sole purpose of issuing a signing certificate and allowing you to authorize other accounts (don't use existing ones!) to sign in to the tablets. Then buy a Mac Mini, buy the $20 OSX server software, start to configure it---oops, there's an update to the OS. Upgrade and find all your server shit broken. Oh, and by the way, you have to re-buy the *new* server software for the newly upgraded OS. Then try to fix it. After 9 months of having various Apple 'professionals' stumble around and not be able to deploy it, I spend two weeks during business hours using Apple Support to get it working. After throwing away and re-creating 20 iCloud accounts because Apple couldn't delete them or change them to the right type so it can participate in their VPP program. Screw that mess.
So once again, yeah, I have a *lot* of Apple hate. It's a toy OS for people who don't have to do anything more complicated than check e-mail and browse the web in a *very* playskool "my first computer"-type interface.
There's no place like