打開文件過多錯誤,但 99.5% 的 inode 是免費的 (Too many open files error but 99.5% inodes are free)


問題描述

打開文件過多錯誤,但 99.5% 的 inode 是免費的 (Too many open files error but 99.5% inodes are free)

我收到錯誤“打開的文件太多”;但是 99.5% 的 inode 是免費的。ulimit 是 1024(軟)和 4076(硬)。錯誤可能是由於其他問題引起的嗎?


參考解法

方法 1:

Inodes are not related to open files. You can check current open files using lsof (sth. like lsof | wc ‑l). I would suggest to just raise the limit in the /etc/security/limits.conf

Try adding something like:

*  soft  nofile  20000
*  hard  nofile  20000

And see if that helps.

(by Karthik Srinivasalfheim)

參考文件

  1. Too many open files error but 99.5% inodes are free (CC BY‑SA 2.5/3.0/4.0)

#file-descriptor #Centos #linux






相關問題

在 Android 中持久化文件描述符 (Persisting File Descriptors in Android)

無法理解 select() 系統調用 (failure to understand select() system call)

文件描述符中實際存儲了多少信息? (How much information is actually stored in a file descriptor?)

為同一個文件描述符創建兩個文件是否定義明確? (Is creating two FILEs for the same file descriptor well-defined?)

Android文件描述符洩漏調試 (Android file descriptor leakage debuging)

C中的文件描述符分配 (File Descriptor Assignment in C)

在某些 linux 程序中關閉奇怪的描述符 (Strange descriptor closing in some linux programs)

c read() 導致錯誤的文件描述符錯誤 (c read() causing bad file descriptor error)

C中系統調用的文件句柄問題 (Filehandle issue with system call in C)

使用 copy_file_range 進行複制加速 (Copy acceleration with copy_file_range)

打開文件過多錯誤,但 99.5% 的 inode 是免費的 (Too many open files error but 99.5% inodes are free)

SIGPIPE 由於文件描述符和進程替換 (SIGPIPE due to file descriptors and process substitution)







留言討論