-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
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
fsevapi backend on macOS is buggy #45
Comments
UPDATE: The move to trash completed. I'd already made sure that there was nothing in /Volumes/Target/.Trash, only in /Volumes/Source/.Trash (as expected).
|
This is probably because of the devfs backend which is not properly implemented and sometimes it starts parsing trash from the device that it is not parsing it well. i've changed the default backend to be the btw fsmon-osx is now named fsmon-macos |
Please try again with latest 1.8.0, the devfs backend must be fixed but it's no longer the default so it's not that problematic now. i'll keep this issue opened with a fixed title for reference. |
Hi,
I wanted to use
fsmon-osx
to monitor a long, Finder file move operation, something I estimated would take about 20 minutes. In case it matters, I was copying between two mounted .dmg "Case-sensitive HFS+" filesystems. Let's call these /Volumes/Source and /Volumes/Target.In Finder, I selected the files to copy in /Volumes/Source, then did a paste operation into /Volumes/Target.
Meanwhile, because of issue #44 I downloaded and compiled
fsmon-osx
from source. No errors duringmake
. I then launched it with:Unfortunately, in the time it took me to download, compile and launch
fsmon-osx
, the Finder paste operation completed sooner than I expected;fsmon-osx
didn't show any activity. Not a big deal as I had more files to move so I just leftfsmon-osx
running.With the Finder paste operation successfully completed, I made the Finder window for /Volumes/Source active. It still had the files selected, so I proceeded to have Finder move them to Trash.
This is where it gets weird. Even though
fsmon-osx
was pointed to /Volumes/Target, as soon as Finder started moving files to Trash,fsmon-osx
started showing hundreds of lines like this:My questions:
Why would
fsmon-osx
start showing activity on the move to trash action for /Volumes/Source, when I told it to monitor /Volumes/Target?What do the errors above mean? "Error unknown type...", "Invalid length..." and "Overflow detected..." ?
The text was updated successfully, but these errors were encountered: