Its been a bug for 15 years. Gotten better, but still exists. I don't know if we have a specific bug that is open.
@softraid-support Shouldn't a bug be opened if it is still corrupting external filesystems?
The problem is they get closed. Also, if bugs cannot be easily reproduced, they are closed. In order to ensure a bug is fixed, we have to have very reproducible steps. On bugs like this, that is very hard to do.
@softraid-support So I understand, you are claiming that the filesystem corruption issue described in this forum thread is a result of a long-standing bug in macOS and not an issue with SoftRAID and that when a bug is filed with Apple on this issue, they close it because they can't reproduce it, correct? My question is: how do you know this is a macOS bug? If you have proof/analysis showing macOS is at fault, then this should make it difficult for Apple just to close the bug.
I'm going on about this because I am very concerned about filesystem/data corruption on the large amount of storage I have managed by SoftRAID. I am not comfortable with the idea that if I do a macOS upgrade with my Thunderbay DAS attached and running the filesystem may be corrupted. If you are positive this is a macOS problem, I hope you escalate this issue with Apple since it directly affects the reliability of SoftRAID storage.
The fact that "Disk Warrior" exists and works is proof enough. 20+ years it has fixed volumes that do not mount.
we have been trying to get this fixed, but the way Apple engineering works is reproducability. Show specific steps to reproduce a problem, they can fix it.
"First Aid" never did much.
APFS is all that is being managed at present, so if we get APFS issues, we can report those and given steps, or a corrupted APFS directory, we can send that to Apple for evaluation. Problem is usually users do not want to send their "data" to Apple, understandably.
this is a difficult kind of issue, as the occurances are relatively rare, and getting "steps to reproduce" extremely difficult.

