I have a question regarding the on-disk structure of sealed system volumes in macOS 11. When parsing the sealed system volume, I'm seeing non-leaf fstree nodes whose binv_child_oid does not correspond to an object id that is found in the volume's OMAP. Parsing the non-sealed volumes works as expected.
I can't find anything in the latest documentation that suggests that the child object ids in sealed volume fstrees should be handled any differently, and the flags in the tree suggest that these are virtual object ids. Is there another layer of indirection or a different omap that I need to parse to link the child nodes on sealed volumes? -- Joe T. Sylve, Ph.D.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Filesystem-dev mailing list (Filesystem-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/filesystem-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
