Re: APFS root filesystem. All files' inode id have offset of 0x200000000
Re: APFS root filesystem. All files' inode id have offset of 0x200000000
- Subject: Re: APFS root filesystem. All files' inode id have offset of 0x200000000
- From: Thomas Tempelmann <email@hidden>
- Date: Thu, 22 Mar 2018 21:51:01 +0100
Eric,
What information are you trying to get out of each scan? You will always
> have a time-of-use vs. time-of-check race condition here .. the filesystem
> is in a perennial state of flux.
>
That's one thing I was surprised about when using searchfs() on APFS vs.
HFS+: On HFS, I'd frequently get the specific return code telling me that
the btree has changed, meaning I should restart the search to make sure I
don't miss nodes.
However, I never see this with APFS. I did then assume, err, hope, that
searchfs on APFS holds a temporary snapshot, thereby preventing changes to
the searched tree. Are you saying that this is not the case, and even, that
searchfs on APFS doesn't tell me about changed node order when it should?
Thomas
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden