remove warning: inode_val: object : invalid bsd flags
Hello,I have found a bug on onedrive for mac. I use Mojave and APFS. I reproduced the issue with the volume encrypted and also without encryption (Filevault). The bug is the following, the folder gives a warning in DiskUtil with the following format:
warning: inode_val: object (oid 0x417de2): invalid bsd_flags (0x10)
I have verified is the onedrive folder using the following command from mac terminal:
find / -inum 4292066
where 4292066 is 417de2 in decimal
This bug has been fixed with the latest version of macOS Mojave. Let us know if you are still running into it after you upgrade.
Mathieu Elissen commented
I had the following message with macOS Mojave 10.14.5 : "Warning: inode_val: object (oid 0xc4309): invalid bsd_flags (0x10)". At the same time Finder was indicating the wrong sizes of folders and also indication of free space on the SSD of my Mac mini was completely wrong. Photoshop CC 2019 was complaining that the scratch disks had nomore free space anymore. After completely uninstalling OneDrive and rebooting these problems were solved. To avoid further problems I didn't dare to install OneDrive in macOS 10.14.6 again.
Caleb Yee commented
I have the same issue as everyone here. OsX Mojave and using OneDrive 19.103.0527.0002
Sharad Agrawal commented
All - this issue made my Mac very slow and to a point that I had to reinstall macOS after formatting the drive. Disk check revealed tons of bad inod errors before formatting. I have now ditched OneDrive for Mac (for now)
I correct myself: if the "file on request" function is activated and some files are downloaded, opening them, for all these files the warning appears again.
Therefore the problem is solved only if the "file on request" function is left disabled.
Yes, fixed for me too.
Sharad Agrawal commented
I noticed that with recent update to MacOS Mojave, this issue is fixed for me and I no longer get the inod bsd flag error when I run disk check.
Theoretically, what harm is there in leaving OneDrive working with an error like this? I have an SSD (Samsung 860). Does this just mess up your OS installation, or file system, or do actual damage to your drive, or mess up the directory structure or what? I'm sure many people are oblivious to this problem (you don't know its there until you run DU repair).
I get “inode_val: object (oid 0x10afcbb): invalid bsd_flags (ox10)”
I uninstalled OneDrive, deleted everything related to it, and the OneDrive synced folder and I’m still getting an error.
Shiki Suen commented
One more thing: This issue, thereotically, shouldn't do significant physical damage to SSD. If there is a such issue, it is likely because of another reason.
Shiki Suen commented
This is Shiki. Here comes new information forwarded from one of those developers in the OneDrive team:
Since the introduction of Files-on-Demand, OneDrive utilizes the BSD_flag (0x10) to mark the demanded state of a file. The choice of this BSD flag is made under discussion between Apple and Microsoft. However, the develpers of Disk Utility on the Apple side may know nothing about it yet, and Disk Utility treats this unknown flag as "Reserved" with warnings.
Note that this flag in (and only in) FreeBSD indicates "uunlink (system no unlink)" which has no relationship with macOS and APFS.
The radar number is 49155065 (submitted by someone else) and we have to wait for a fix from Apple towards the Disk Utility app in macOS.
Microsoft is aware of the issue and is working with APPLE to deal with this. it will not be an overnight fix but i believe if we all keep reporting the issue and REFUSE to use the APP it will get fixed. I have removed the app from my IMAC latest mojave etc and store my onedrive folder on an external disk with the sync function.
Kelly Woods commented
You can determine where the problem occurs by running:
find / -inum $((0x??????)) -print 2> /dev/null
This is what you'll get: https://pic1.zhimg.com/80/v2-4efce963b96c7da8c3091534ef8e2348_hd.jpg
For me, I just uninstall OneDrive on my Mac before MS/APPLE bring a solution: https://www.minicreo.com/mac-uninstaller/uninstall-microsoft-onenote-mac.html
Thor Landsverk commented
Same issue here. Using One Drive and Office 365
I have deleted the OneDrive app and whatever associated files I could find in the Library folder. I ran DiskUtility and the error persists. Though in my case it's "oid 0xbc272". Anyone know how to fix this? Am I missing something that I should have also deleted? Thanks!
Bavo Bostoen commented
All my Office 365 clients on Mac that use OneDrive to sync their files have this problem - MS and or Apple should solve this.
MS should understand that if their OneDrive client software does not work to the same standard as eg DropBox (*), it reflects badly on them and people will extend their criticism to the whole Office 365 suite, whether that is reasonable or not.
They should invest way more in this, and test everything in-house - just make it work already!
(*) it certainly is not on par with DropBox, it was even worse in the past but there are still too many problems with OneDrive syncing and also with online document collaboration (which uses OneDrive), no matter of on Mac or Windows, which currently works a lot better in Google product.
On my side, in the latest version, 19.012.0121.0009 the issue still present too.
Juan Miguel Duran commented
On my side, in the latest version, 19.012.0121.0009 the issue still present. Could you please check and share your feedback?
Yuri Bykov commented
Hello. I already fix the problem. When uninstalled app OneDrive, and after restart I have same problem in local snapshots - "warning: inode_val: object (oid 0x424a0f): invalid bsd_flags (0x10)".
And I used this manual to delete local snapshots: https://www.macworld.com/article/3260635/how-to-delete-time-machine-snapshots-on-your-mac.html
Then problem was removed.
It basically killed the SSD from my MacBook Air. Now I am running the OS from an SD card in high Sierra with hfs+ only. And ofc OneDrive cannot be installed on an external drive...
Michael Glass commented
does anybody know if this bug exists on standalone Word for Mac without entire Office Suite?