* [PATCH] inboxidle: clue users into resolving ENOSPC from inotify
@ 2020-12-26 5:59 Eric Wong
0 siblings, 0 replies; only message in thread
From: Eric Wong @ 2020-12-26 5:59 UTC (permalink / raw)
To: meta
It may not be obvious to users a ENOSPC error is from hitting
a (tunable) kernel-imposed limit on inotify watches, and not
some storage device running out of space. Give them a hint
here to reduce our own support burden.
---
lib/PublicInbox/InboxIdle.pm | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/lib/PublicInbox/InboxIdle.pm b/lib/PublicInbox/InboxIdle.pm
index 34606186..69da5f4f 100644
--- a/lib/PublicInbox/InboxIdle.pm
+++ b/lib/PublicInbox/InboxIdle.pm
@@ -39,6 +39,11 @@ sub in2_arm ($$) { # PublicInbox::Config::each_inbox callback
$self->{on_unlock}->{$w->name} = $ibx;
} else {
warn "E: ".ref($inot)."->watch($lock, IN_MODIFY) failed: $!\n";
+ if ($!{ENOSPC} && $^O eq 'linux') {
+ warn <<"";
+I: consider increasing /proc/sys/fs/inotify/max_user_watches
+
+ }
}
# TODO: detect deleted packs (and possibly other files)
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2020-12-26 5:59 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-26 5:59 [PATCH] inboxidle: clue users into resolving ENOSPC from inotify Eric Wong
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).