* [Bug 197335] New: Inode exhaustion should be logged to dmesg
@ 2017-10-20 19:11 bugzilla-daemon
2017-10-20 19:21 ` [Bug 197335] " bugzilla-daemon
2017-10-31 15:25 ` bugzilla-daemon
0 siblings, 2 replies; 3+ messages in thread
From: bugzilla-daemon @ 2017-10-20 19:11 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=197335
Bug ID: 197335
Summary: Inode exhaustion should be logged to dmesg
Product: File System
Version: 2.5
Kernel Version: 4.14.0-rc1
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: enhancement
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: teamathena.nitc@gmail.com
Regression: No
Problem: If the system runs out of inodes, the error messages show "No space on
disk". This is misleading to the user as the disk may still have space. Logging
to dmesg can help the user correctly identify the problem.
Bug #1665833 from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665833
My server just became unusable, because it ran out of inodes (something that
shouldn't happen on a relatively normal installation). The root-cause was a
misbehaving CRM program creating way too many session files and never deleting
them. However, while debugging, it would have been really really helpful if
there were something in the logfiles. But it just failed silently: the lack of
any error message makes diagnosing this error condition 100x harder than it
should be. We get messages about being out of disk-space, but that's not
helpful, especially when "df -h" shows it not to be true.
So, the bug report/feature request is this: when the kernel cannot create a new
file due to a shortage of inodes, it should emit a message to that effect, at
least in dmesg (and ideally also to syslog).
[For anyone else who chances upon this bug report, you can tell if you have run
out of inodes with "df -i", and you can find the offending directories with:
"find / -xdev -size +100k -type d" ]
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug 197335] Inode exhaustion should be logged to dmesg
2017-10-20 19:11 [Bug 197335] New: Inode exhaustion should be logged to dmesg bugzilla-daemon
@ 2017-10-20 19:21 ` bugzilla-daemon
2017-10-31 15:25 ` bugzilla-daemon
1 sibling, 0 replies; 3+ messages in thread
From: bugzilla-daemon @ 2017-10-20 19:21 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=197335
--- Comment #1 from Team Athena (teamathena.nitc@gmail.com) ---
I would like to patch this fairly small bug as a learning exercise.
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug 197335] Inode exhaustion should be logged to dmesg
2017-10-20 19:11 [Bug 197335] New: Inode exhaustion should be logged to dmesg bugzilla-daemon
2017-10-20 19:21 ` [Bug 197335] " bugzilla-daemon
@ 2017-10-31 15:25 ` bugzilla-daemon
1 sibling, 0 replies; 3+ messages in thread
From: bugzilla-daemon @ 2017-10-31 15:25 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=197335
--- Comment #2 from Team Athena (teamathena.nitc@gmail.com) ---
Created attachment 260449
--> https://bugzilla.kernel.org/attachment.cgi?id=260449&action=edit
Make a log in dmesg when file creation fails due to no free inode
Uses a ext4_warning to log to dmesg
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-10-31 15:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-10-20 19:11 [Bug 197335] New: Inode exhaustion should be logged to dmesg bugzilla-daemon
2017-10-20 19:21 ` [Bug 197335] " bugzilla-daemon
2017-10-31 15:25 ` bugzilla-daemon
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 NNTP newsgroup(s).