Re: APFS root filesystem. All files' inode id have offset of 0x200000000

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

Re: APFS root filesystem. All files' inode id have offset of 0x200000000

> > So far I hadn't had much lack in scanning by this order, sparse filesystem > makes the /.vol// option inefficient. > As for the searchfs option, I haven't seen in the man page any way to > control the order of the files. > The order is arbitrary, as it walks over the btree nodes in the most

Re: APFS root filesystem. All files' inode id have offset of 0x200000000

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. Eric > On 22 Mar 2018, at 12:53 PM, Irad K wrote: > > Hi and thanks for the

Re: APFS root filesystem. All files' inode id have offset of 0x200000000

> On Mar 21, 2018, at 1:38 PM, Irad K wrote: > > Eric, > > Thanks for the info, that can explain the offset since I previously upgraded > the OS from Sierra which uses HFS+ for its root filesystem. > > The reason that brought me looking into the fileid values, is

Re: APFS root filesystem. All files' inode id have offset of 0x200000000

> > 1. Is there any way to extract the current file-id range (minimum to > maximum fileid). > Well, both HFS+ and APFS know the last used FileID and whenever a new node (file, dir) is created, the last ID + 1 will be used for it. But you cannot query that value directly (only indirectly, by

Re: APFS root filesystem. All files' inode id have offset of 0x200000000

Eric, Thanks for the info, that can explain the offset since I previously upgraded the OS from Sierra which uses HFS+ for its root filesystem. The reason that brought me looking into the fileid values, is some file scanner design I'm currently working on that instead of iterating the files

Re: APFS root filesystem. All files' inode id have offset of 0x200000000

Irad, This is because your volume went through the HFS -> APFS converter. As a side effect of some on-disk APFS format differences from HFS, we need to make sure we can differentiate large EAs and resource from data forks. So the large EAs/resource forks in APFS retain the original HFS inode