-
Notifications
You must be signed in to change notification settings - Fork 228
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
Error "No space left on device" #103
Comments
It's inotify's way of saying that the watch limit has been reached. (Having a dedicated error type for that case in rsnotify might be a good thing though.) |
Thanks, that makes sense. I'm not sure that a dedicated error type or error handling is needed. In this case, errno is set to I was confused by the std::fmt::Debug implementation of std::io::Error, which is where the "No space left on device" message comes from. Perhaps it could be argued that inotify_add_watch should have used a specialized errno, but that ship has sailed. |
Hi, I'm having trouble getting the example
monitor_debounced
to run without error on linux (kernel 3.16 debian amd64) compiled with rustc 1.13.0.It seems to run fine on most directories on my filesystem (ZFS from zfsonlinux.org), but there are at least two directories where I get a "No space left on device" error. The distinguishing feature of these directories is that there are many files and subdirectories (e.g. hundreds of thousands of files and tens of thousands of subdirectories).
The thing is, I don't know what device should have no space left. The filesystem in question has 45 TB free and the root filesystem (with /tmp) has 97 GB free. Also, diving into the code I don't see any temporary file allocations. Any hints on what's behind this and how to debug it?
The text was updated successfully, but these errors were encountered: