APFS container version mismatch?!

I use APFS on my external 1tb ssd hard drive. Today the second time I noticed an strange warning after mounting my drive "macOS can't repair volume:…".

When I started fsck_apfs what is going on I got the following printout
Code Block
➜  ~ sudo fsck_apfs /dev/rdisk3s1
Password:
Checking the container superblock.
warning: container has been mounted by APFS version 1677.0.6, which is newer than 1412.141.1
warning: disabling overallocation repairs by default; use -o to override
error: (oid 0x401) nr: invalid o_oid (0xa132)
error: (oid 0x401) nr: invalid o_type (0x80000003, expected 0x80000011)
error: verification/reading of the nx_reaper object failed: Illegal byte sequence
The volume /dev/rdisk3s1 could not be verified completely.

On my Mac I'm still on 10.15.7. I did mount my drive once with my iPad Pro with iPadOS 14.0 and worked on it.

Did iPadOS change the APFS version? If yes: WHHHY?!
Do I risk a data loss, if I work with my drive under the current circumstances of the APFS version mismatch?

I fixed this or similar problem by adding a volume to the container, following the bottom post on this question on stack exchange "macOS Catalina - can't mount external hdd - verification/reading of the omap object failed: Illegal byte sequence"


The version warning is harmless; fsck_apfs is simply disabling a very specific kind of repair just to be extra careful. As for the error you’re getting, the macOS 11 version of fsck_apfs should be able to handle this better.

APFS container version mismatch?!
 
 
Q