Tag Info

New answers tagged


99.9% of the time the reason this happens is because one or more files have been deleted, but there is a process which is still writing to the old file handle. When a program wants to perform I/O operations on a file, it asks the kernel "hey kernel, I would like to access the file /bla.txt and I want to be able to read and write to it". The kernel then ...


I can only think of two reasons: a rootkit infection; filesystem curruption. Use dd to dump your partition to a removable/network disk and mount/check it elsewhere. You may get a few inconsistencies while dumping but a great chance is they will be fixable easily.


For me, changing fs.inotify.max_user_watches did the trick. root@grostruc:/# service ssh restart Error: No space left on device root@grostruc:/# sysctl fs.inotify.max_user_watches fs.inotify.max_user_watches = 65536 root@grostruc:/# sysctl fs.inotify.max_user_watches=262144 fs.inotify.max_user_watches = 262144 root@grostruc:/# service ssh restart Fix ...

Top 50 recent answers are included