-
Notifications
You must be signed in to change notification settings - Fork 102
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
cobalt serve: No space left on device (inotify) #387
Comments
What version of Rust are you using? What OS and version is this? That seems strange that this error is coming up from the file system notifications. Why would that care about disk space? What happens when do you call |
The latest stable Rust and the latest version of Ubuntu.
$ cargo --version
cargo 0.25.0 (8c93e0895 2018-02-01)
$ rustc --version
rustc 1.24.0 (4d90ac38c 2018-02-12)
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 17.10
Release: 17.10
Codename: artful
|
Rust 1.24.1 just came out to fix many regression, can you see if it's still happening? |
Yes I have tried this but it didn't fix the problem @epage When I build the page it gets build. So it is the serving part that crashes $ cobalt build
[warn] Syntax theme named 'base16-ocean.dark' ignored. Reason: Themes are unsupported in this build.
[info] Building from "/home/{username}/Documents/git/kim/" into "/home/{username}/Documents/git/kim/_site"
[info] Build successful The built-in [info] Serving "/home/reinier/Documents/git/kim/_site" through static file server
[info] Server Listening on 127.0.0.1:3000
[info] Ctrl-c to stop the server
[debug] threads = 10
[trace] registering with poller
[trace] registering with poller
[trace] event loop tick
[trace] tick_to; now=0; tick=0
[trace] ticking; curr=Token(18446744073709551615)
[trace] event loop tick
Error: serve command failed
Caused by: Notify error
Caused by: other os error
Caused by: No space left on device (os error 28)
[trace] tick_to; now=0; tick=1 |
Ok, good, there aren't problems with So a workaround for this is to call Looks like this is a terrible way of saying you've reached a limit in inotify and might need to raise it. See notify-rs/notify#103 We should probably add this to the website as a FAQ item. |
Created an issue for documenting this on the website. Closing this in favor of that issue. |
Installed with cargo:
Check version:
Init a new repo:
Try to serve:
I have about ~50GB of free space on the disk that was used.
The text was updated successfully, but these errors were encountered: