Edit/update: April 4. 2022
Is someone willing to/able to reproduce this error? 'Disk Full'
You need (shortest way of reproduction, see below for original setup):
- Two internal SSD's (macmini server)
- SSD0 in 2 partitions (Sys1 (small eg. 16GB) +Data)
- SSD1 in 2 partitions (Sys2 (small eg. 16GB) +Data)
diskutil apfs create disk0s2 disk1s2 System
(and leave the other/data partions alone, or convert them into RAID)
This creates a logical APFS container with one drive named System spanning two physical SSD's. There are no errors and the drive checks out OK in diskutil First Aid.
Behaviour (seen in all MacOS versions i've tested so far):
After writing a file that during copy passes the phycial border between disk0 and disk1 the system reports a 'Disk Full' error and aborts copy with (in my case) 50% of the drive still having free space.
This behavior does not occur:
- when the APFS Logical Container of only Disk in the container is formated HFS+ so it's an APFS only problem.
- when disk0 and disk1 are fully assigned to the container (e.g diskutil resetfusion or diskutil apfs create disk0 disk1).
This however has a big speed disadvantage over AppleRaid, and formating both drives as RAID is not possible because of Apple restrictions to boot Catalina or newer from RAID (Catalina can be done however).
------
Original post:
This is for the tweakers
or FS-wizards
In order to get the most out of my Mac mini 2012 I use as a home server , kids (Apple Arcade) gaming box and 'Apple TV'/vid player/foto presenter hooked op on 4K TV (SwitchRes X). I made the following setup:
Setup:
base Mac mini 2012 i5 with 16GB and 2 identical 1TB Samsung SSD's (that until Catalina worked in full RAID)
MacOS: Big Sur (OCLP)...I think OCLP has nothing to do with this, combined APFS & Raid has imho.
What I did to get RAID working on Big Sur:
Divide the base Samsungs in 4 parts:
- System - disk 0 64GB
- System - disk 1 64GB
- Data - disk 0 935GB
- Data - disk 1 935GB
Out of System disk 0 & 1 I made a 128GB APFS SYSTEM Fusion Drive/logical drive since BigSur can't boot from Raid. I did that with the diskutil commands from cleared/zeroed drives.
Out of Data disk 0 & 1 I made a 1,8GB RAID 0 APFS DATA drive (that works flawlessly with great speed).
All seemed to work perfectly stable and great for months...but:
after crossing the 50% mark (64GB) of disk space on the Fusion System disk MacOS refuses to write data as if the second part of the fusion drive is read only (disk full error while there is enough space left). There are no real errors other than disk full or an install failure and the disk space left for files is (not surprisingly enormous=64GB). It really is the 64GB+ border that can't be crossed.
I still think this is hackable/solvable and that I might have found an unsupported/bug/to be expected quirk in APFS.
But before y'all say 'told you so': I just like the endeavor of trying this. And hope for some clever help.
Question: is this solvable by reconstruction the disk and do it all over again properly? And most important: How?
Only if you have spare time and see the benefit of doing this...
I have clones/backups so wiping is a pain but not a problem.
Thanks in advance!
Update:
- Today I reconstructed the fusion disk in Terminal with according to this manual:
https://apple.stackexchange.com/questions/309739/apfs-container-over-multiple-physical-disks#
That did NOT work
- Today I reconstructed the fusion disk (Logical Volume) with a Internet Recovery version of DiskUtil using:
-diskutil cs create (which was deprecated afterwards)
The result was a JHFS+ drive from 128GB that actually DID WORK again
I then
- converted it in APFS which failed
- formatted it APFS which worked but the same error returned, so the error is APFS related
- recreated the JHFS+ drive checked if it filled up for 80% and that worked again
- installed Big Sur on it next to the already present very large video files (which for now resulted in an error in a new tool called 'macOS-update-assistant'
Is someone willing to/able to reproduce this error? 'Disk Full'
You need (shortest way of reproduction, see below for original setup):
- Two internal SSD's (macmini server)
- SSD0 in 2 partitions (Sys1 (small eg. 16GB) +Data)
- SSD1 in 2 partitions (Sys2 (small eg. 16GB) +Data)
diskutil apfs create disk0s2 disk1s2 System
(and leave the other/data partions alone, or convert them into RAID)
This creates a logical APFS container with one drive named System spanning two physical SSD's. There are no errors and the drive checks out OK in diskutil First Aid.
Behaviour (seen in all MacOS versions i've tested so far):
After writing a file that during copy passes the phycial border between disk0 and disk1 the system reports a 'Disk Full' error and aborts copy with (in my case) 50% of the drive still having free space.
This behavior does not occur:
- when the APFS Logical Container of only Disk in the container is formated HFS+ so it's an APFS only problem.
- when disk0 and disk1 are fully assigned to the container (e.g diskutil resetfusion or diskutil apfs create disk0 disk1).
This however has a big speed disadvantage over AppleRaid, and formating both drives as RAID is not possible because of Apple restrictions to boot Catalina or newer from RAID (Catalina can be done however).
------
Original post:
This is for the tweakers
or FS-wizards In order to get the most out of my Mac mini 2012 I use as a home server , kids (Apple Arcade) gaming box and 'Apple TV'/vid player/foto presenter hooked op on 4K TV (SwitchRes X). I made the following setup:
Setup:
base Mac mini 2012 i5 with 16GB and 2 identical 1TB Samsung SSD's (that until Catalina worked in full RAID)
MacOS: Big Sur (OCLP)...I think OCLP has nothing to do with this, combined APFS & Raid has imho.
What I did to get RAID working on Big Sur:
Divide the base Samsungs in 4 parts:
- System - disk 0 64GB
- System - disk 1 64GB
- Data - disk 0 935GB
- Data - disk 1 935GB
Out of System disk 0 & 1 I made a 128GB APFS SYSTEM Fusion Drive/logical drive since BigSur can't boot from Raid. I did that with the diskutil commands from cleared/zeroed drives.
Out of Data disk 0 & 1 I made a 1,8GB RAID 0 APFS DATA drive (that works flawlessly with great speed).
All seemed to work perfectly stable and great for months...but:
after crossing the 50% mark (64GB) of disk space on the Fusion System disk MacOS refuses to write data as if the second part of the fusion drive is read only (disk full error while there is enough space left). There are no real errors other than disk full or an install failure and the disk space left for files is (not surprisingly enormous=64GB). It really is the 64GB+ border that can't be crossed.
I still think this is hackable/solvable and that I might have found an unsupported/bug/to be expected quirk in APFS.
But before y'all say 'told you so': I just like the endeavor of trying this. And hope for some clever help.
Question: is this solvable by reconstruction the disk and do it all over again properly? And most important: How?
Only if you have spare time and see the benefit of doing this...
I have clones/backups so wiping is a pain but not a problem.
Thanks in advance!
Update:
- Today I reconstructed the fusion disk in Terminal with according to this manual:
https://apple.stackexchange.com/questions/309739/apfs-container-over-multiple-physical-disks#
That did NOT work
- Today I reconstructed the fusion disk (Logical Volume) with a Internet Recovery version of DiskUtil using:
-diskutil cs create (which was deprecated afterwards)
The result was a JHFS+ drive from 128GB that actually DID WORK again
I then
- converted it in APFS which failed
- formatted it APFS which worked but the same error returned, so the error is APFS related
- recreated the JHFS+ drive checked if it filled up for 80% and that worked again
- installed Big Sur on it next to the already present very large video files (which for now resulted in an error in a new tool called 'macOS-update-assistant'
Attachments
Last edited:
