Help with fsck file IDs anyone ?

[adam-stark]

Hi All,

After upgrading to Ventura Beta 4 I am getting a pause in the boot process, upon looking as to why, I ran first aid on my Data volume and got the following warnings:

Checking the fsroot tree.
warning: file has compression bsdflags, but doesn't have the compression xattr (id 161782158)
warning: file has dataless compression bsdflag, but has another compression type (id 161782158, type = -1)
warning: file has compression bsdflags, but doesn't have the compression xattr (id 172634449)
warning: file has dataless compression bsdflag, but has another compression type (id 172634449, type = -1)
warning: file has compression bsdflags, but doesn't have the compression xattr (id 172652700)
warning: file has dataless compression bsdflag, but has another compression type (id 172652700, type = -1)
Checking the extent ref tree.

I am trying to locate these files to see what they are and how i can potentially remove/fix etc... I thought the ID that is reported by fsck was the inode reference, but I cannot find these 3 files by inode at all....

Any ideas from anyone on Macrumors ?

Many thanks in advance.

Adam

 

[bogdanw]

Run First Aid from Recovery: “Repair volumes, then containers, then disks” https://support.apple.com/kb/HT210898

 

[adam-stark]

Run First Aid from Recovery: “Repair volumes, then containers, then disks” https://support.apple.com/kb/HT210898

Thanks but done all that, the above was a copy / paste from the diskutil / first aid process

Hence I am looking to be able to identify the files reported by the ID in diskutil....

 

[bogdanw]

Thanks but done all that, the above was a copy / paste from the diskutil / first aid process

From Recovery? Or even better, from a bootable macOS installer.

There is little information on
bsdflags
https://www.google.com/search?q=bsdflags site:https://opensource.apple.com&hl=en-US&gl=US
bsd_flags
https://developer.apple.com/support/downloads/Apple-File-System-Reference.pdf

 

[adam-stark]

Thanks again for replying.....

From Recovery....

Again, I am looking on how to look up a file using the ID reference returned from fsck.... it does not seem to be an Inode...

 

[bogdanw]

With GetFileInfo according to https://eclecticlight.co/2019/09/04/apfs-safe-saves-inodes-and-the-volfs-file-system/
Run stat on a file on your Data volume to get the first number, the second number should be the id in the log, ending up with GetFileInfo /.vol/first number/second number

 

[Killerbob]

I also have a pause in the boot process on my Mac Studio, with the boot sequence sitting there for a good 60 seconds before continuing. This came right after the update to Beta 4 - described here https://forums.macrumors.com/thread...o-beta-4.2353015/?post=31298476#post-31298476

I checked and I have similar bsdflags errors on my Data volume. I have run First Aid from the Recovery boot, and they are still present.

Any suggestions as to how to fix will be welcome...

 

[Killerbob]

OK - that sent me on a wild goose chase... The errors have cleared in First Aid, and the long boot time is still present.

 

[adam-stark]

With GetFileInfo according to https://eclecticlight.co/2019/09/04/apfs-safe-saves-inodes-and-the-volfs-file-system/
Run stat on a file on your Data volume to get the first number, the second number should be the id in the log, ending up with GetFileInfo /.vol/first number/second number

Thanks again...

I had come across this in google and tried it, and it didn't work.... I ran stat on a normal file and could use GetFileInfo to reference it...

So it made me think, is the ID returned by fsck indeed an Inode ? This is my question...

 

[adam-stark]

OK - that sent me on a wild goose chase... The errors have cleared in First Aid, and the long boot time is still present.

mm how did you clear them in First Aid ? I have run First Aid so many times and they are still present ?

So we need to continue to look at why some have a boot pause.... ok...(rolling sleeves up)

 

[bogdanw]

If you haven’t done this already, manually unmount the Data volume before running First Aid from Disk Utility.
You can also try from Terminal in Recovery
Example:
diskutil list physical
diskutil unmountDisk /dev/disk0
diskutil verifyDisk /dev/disk0
fsck_apfs /dev/disk0
fsck_apfs /dev/disk1s1

 

[Killerbob]

mm how did you clear them in First Aid ? I have run First Aid so many times and they are still present ?

I don’t know… I ran First Aid in Recovery, and they were there. The next day I ran it again, and this time they were gone…