From: raghu.prabhu13@gmail.com
To: xfs@oss.sgi.com
Cc: Raghavendra D Prabhu <rprabhu@wnohang.net>
Subject: [PATCH V2 0/3] Print when ENOSPC due to lack of inodes in non-inode64 mount.
Date: Wed, 12 Sep 2012 03:43:21 +0530 [thread overview]
Message-ID: <cover.1347396641.git.rprabhu@wnohang.net> (raw)
From: Raghavendra D Prabhu <rprabhu@wnohang.net>
Currently, when there are no free inodes left / free space to allocate them (usually
without inode64), there is no indication anywhere of this case, making it harder
to diagnose this case.
Hence, this series prints the causes/reasons to kernel log in a ratelimited
manner, when such a situation arises.
-----
Version 1: Initially sent with pr_err_once to print the error only once.
Version 2: Added ratelimited functions to xfs_message.h instead of printing once
with pr_err_once on suggestion of Dave Chinner.
Raghavendra D Prabhu (3):
Add ratelimited printk for different alert levels
XFS: Print error when xfs_ialloc_ag_select fails to find continuous
free space.
XFS: Print error when unable to allocate inodes or out of free
inodes.
fs/xfs/xfs_ialloc.c | 24 +++++++++++++++++++-----
fs/xfs/xfs_message.h | 28 ++++++++++++++++++++++++++++
2 files changed, 47 insertions(+), 5 deletions(-)
--
1.7.12
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-09-11 22:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 22:13 raghu.prabhu13 [this message]
2012-09-11 22:13 ` [PATCH 1/3] Add ratelimited printk for different alert levels raghu.prabhu13
2012-09-11 22:43 ` Dave Chinner
2012-09-12 3:22 ` Joe Perches
2012-09-13 0:51 ` Dave Chinner
2012-09-11 22:13 ` [PATCH 2/3] XFS: Print error when xfs_ialloc_ag_select fails to find continuous free space raghu.prabhu13
2012-09-11 22:48 ` Dave Chinner
2012-09-11 22:13 ` [PATCH 3/3] XFS: Print error when unable to allocate inodes or out of free inodes raghu.prabhu13
2012-09-11 23:21 ` Dave Chinner
2012-09-21 7:16 ` Raghavendra D Prabhu
2012-09-26 6:14 ` Raghavendra Prabhu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1347396641.git.rprabhu@wnohang.net \
--to=raghu.prabhu13@gmail.com \
--cc=rprabhu@wnohang.net \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox