We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Catalina 10.15.3
searchfs seems unable to search the r/w mountpoint where all user data is stored. Tried v0.3 from https://sveinbjorn.org/files/software/searchfs.zip as well as compiling from master - same result:
searchfs
master
$ ./searchfs -l /dev/disk1s5 (apfs): / /dev/disk1s1 (apfs): /System/Volumes/Data /dev/disk1s4 (apfs): /private/var/vm /dev/disk2s2 (hfs ): /Volumes/TimeMachine $ ./searchfs -v / USBDriverKit.framework$ /System/DriverKit/System/Library/Frameworks/USBDriverKit.framework /System/Library/Frameworks/USBDriverKit.framework $ ./searchfs -v /System/Volumes/Data foo Not a volume mount point: /System/Volumes/Data $ ./searchfs -v /dev/disk1s1 foo Not a volume mount point: /System/Volumes/Data
Not sure if it matters, but I also tried granting the binary Full Disk Access, which did not make any difference. Am I doing something wrong?
The text was updated successfully, but these errors were encountered:
I'm still running on Mojave so I'm not sure about how Catalina may have broken things. Will take a look at this issue as soon as I upgrade.
Sorry, something went wrong.
Same issue on Big Sur 11.1
Manually allow-listing /System/Volumes/Data in is_mount_path() seems to do the trick.
No branches or pull requests
Catalina 10.15.3
searchfs
seems unable to search the r/w mountpoint where all user data is stored. Tried v0.3 from https://sveinbjorn.org/files/software/searchfs.zip as well as compiling frommaster
- same result:Not sure if it matters, but I also tried granting the binary Full Disk Access, which did not make any difference. Am I doing something wrong?
The text was updated successfully, but these errors were encountered: