AnsweredAssumed Answered

APFS - safe to use, maybe not yet (Dec'17)?

Question asked by wxtyrs on Dec 20, 2017
Latest reply on Aug 17, 2018 by wxtyrs

First the preliminaries:

 

FMPA v16.03. ; 7.87GB database file;

iMac (I7, late 2014) macOS 10.13.2 ; RAM 32GB ; 1TB Boot SSD, Samsung 850 ; >250GB free space

 

Now the circumstances:

 

On two occasions, in one month, I have had catastrophic failures while quitting a large FMPA database.

 

While FMP compacts the file, everything freezes, including macOS, and is not accessible.

 

I must then boot from another disk.

 

The Disk Utility (fsck) report is below.

 

Each time, I rebuild the disk from scratch, starting with formatting.

 

This time I will return to using HFS+.

 

I am concerned that APFS may not be handling large database writes properly.

 

Does anyone have some insight about the symptoms??

 

Thank you!

 

 

 

 

DISK UTILITY REPORT

 

Repairing file system.

Volume was successfully unmounted.

Performing fsck_apfs -y -x /dev/rdisk7s1

Checking volume.

Checking the container superblock.

Checking the EFI jumpstart record.

Checking the space manager.

Checking the object map.

Checking the APFS volume superblock.

Checking the object map.

Checking the fsroot tree.

error: invalid dstream.size (5419085824), is greater than dstream.alloced_size (3333865472)

error: xf : INO_EXT_TYPE_DSTREAM : invalid dstream

error: inode_val: object (oid 0x47a732): invalid xfields

fsroot tree is invalid.

The volume /dev/rdisk7s1 could not be verified completely.

File system check exit code is 0.

Restoring the original state found as mounted.

Operation successful.

Outcomes