Resource Fork xattr is missing for compressed file

Gautis wrote:

Well, to be honest, am I struggling with Terminal commands.

What du I put in where it says: find /Volumes/Data/ -inum ######## (Volums and Data?) ( -inum I understand)

You put the inode number in place of the "########".

For example using the sample output in your earlier post:

find  /Volumes/Data  -inum  308825

And when I says: Open Disk Utility, mount the Data volume and quit Disk Utility, is it enough to just mark the disk, and then close the Disk Utility ?

You launch Disk Utility, select the "Data" volume on the left pane and click the "Mount" button on the right side. Then quit Disk Utility.

Because every time I run First Aid, the same "error" is still there.

Like @Barney-15E says, it is a "warning", not an error. As long as you are not experiencing an actual problem, then it should be safe to ignore the "warnings". I believe those "warnings" are a programmer's/developer's reference/notation like @Barney-15E mentions which has a different meaning from what most end users would expect a "warning" to mean. I've never seen First Aid repair any "warnings". I have seen First Aid repair "errors" though (at least some of them anyway). If an "error" (it will literally be noted as "error") is not fixed, then you should definitely deal with it since an "error" will usually cause a problem.

Those "warnings" are in reference to extended attributes (xattr) for resource forks. Basically this provides some extra information about a file/folder. The reason these "warnings" came back is because these are hidden files associated with a file/folder and these extended attributes are not properly marked as such anymore or have become corrupted (no idea on the exact problem as I really don't know much about them except for quickly skimming a few articles today). This error does not affect the actual data on the disk, only some of the extra meta data which may be associated with a file/folder. Here are a couple of article regarding these items in case you are interested:

https://eclecticlight.co/2017/12/11/an-introduction-to-extended-attributes-xattrs/

https://eclecticlight.co/2019/12/10/stick-a-fork-in-it-and-other-flashbacks/

https://forums.macrumors.com/threads/follow-up-question-about-resource-forks-and-how-it-affects-my-data-archival.2290263/

smellcoffee wrote:

I'm getting:

warning: inode (id 29530400): Resource Fork attr is missing for compressed file

warning: inode (id 54389627): Resource Fork attr is missing for compressed file

If you are running First Aid on the boot drive, then run First Aid while booted into Recovery Mode to see if it will repair those items. Try running First Aid several times. If they cannot be repaired even when booted into Recovery Mode and you have issues with the file system, then you will need to perform a clean install of macOS by first erasing the disk followed by reinstalling macOS & restoring from a backup. Make sure to have a good backup before performing a clean install or erasing the disk.

It says the disk is ok and operation successful. What is wrong that you think there is need to investigate those superfluous warnings?

I'm getting:

warning: inode (id 29530400): Resource Fork attr is missing for compressed file

warning: inode (id 54389627): Resource Fork attr is missing for compressed file

This problem is getting annoying, all my ssds have this problem, 2 identical drives, clone back ups yet one of them lacks 100 GB difference in space free., unless im confusing this space with something else the only thing I can think of is the drive has this index problem causing it

Does this help:

Ominous "warnings" in Disk Utility even a… - Apple Community

It’s not an error, it’s a warning which may not even pertain to the user.

It may be in there purely for their own developers.

What do you mean by “DEACTIVATED the disk, and just ACTIVATED it again?”

Did you unmount and mount?

Hi, correct me if I’m wrong, but do you need to reboot and recovery mode? If you user home folder is on an external drive and you’re getting these warnings on that drive?