public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: raghu.prabhu13@gmail.com
To: xfs@oss.sgi.com
Cc: Raghavendra D Prabhu <rprabhu@wnohang.net>, raghu.prabhu13@gmail.com
Subject: [PATCH 0/3] Print when ENOSPC due to lack of inodes.
Date: Sun,  3 Jun 2012 16:42:46 +0530	[thread overview]
Message-ID: <cover.1338721614.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 three-part patch series to print errors to kernel log with reasons,
when such a situation arises.

Raghavendra D Prabhu (3):
  XFS: Print error when xfs_ialloc_ag_select fails to find continuous
    free space.
  XFS: Print error when unable to allocate inodes.
  XFS: Print error when there are no free AGs.

 fs/xfs/xfs_ialloc.c |   13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

-- 
1.7.10.3

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2012-06-03 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-03 11:12 raghu.prabhu13 [this message]
2012-06-03 11:12 ` [PATCH 1/3] XFS: Print error when xfs_ialloc_ag_select fails to find continuous free space raghu.prabhu13
2012-06-05 14:00   ` Dave Chinner
2012-06-03 11:12 ` [PATCH 2/3] XFS: Print error when unable to allocate inodes raghu.prabhu13
2012-06-03 11:12 ` [PATCH 3/3] XFS: Print error when there are no free AGs raghu.prabhu13

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.1338721614.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