From: Jeff Liu <jeff.liu@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [RFC PATCH 4/4] xfs: implement parallism quota check
Date: Mon, 18 Nov 2013 20:41:09 +0800 [thread overview]
Message-ID: <528A0AE5.40702@oracle.com> (raw)
In-Reply-To: <20131118110449.GB1304@infradead.org>
On 11/18 2013 07:04 PM, Christoph Hellwig wrote:
> On Sun, Nov 17, 2013 at 09:01:08PM +0800, Jeff Liu wrote:
>> On 11/16 2013 01:26 AM, Christoph Hellwig wrote:
>>> As Dave pointed out this really should be xfs_bukstat_ag. But looking
>>> at the code you're almost 90% there anyway.
>> One main reason I did not make a per ag bulkstat is because bulkstat() will
>> skip an allocation group if read agi buffer failed, i.e,
>>
>> while (XFS_BULKSTAT_UBLEFT(ubleft) && agno < mp->m_sb.sb_agcount) {
>> cond_resched();
>> error = xfs_ialloc_read_agi(mp, NULL, agno, &agbp);
>> if (error) {
>> /*
>> * Skip this allocation group and go to the next one.
>> */
>> agno++;
>> agino = 0;
>> continue;
>> }
>> ....
>> }
>>
>> Should it capture this issue and drop a warning in this case?
>
> I've been thinking hard about this, but I can't really see any reason
> why we would skip an AG instead of propagating the error. The only
> error xfs_ialloc_read_agi can return is an I/O error from reading
> the buffer from disk, and we'd really want to propagate that sort
> of I/O errror. I'd suggest a patch at the beginning of the series
> to just change that behavior for all the two places in bulkstat that
> call xfs_ialloc_read_agi. None of the other callers seem to behave
> this way either.
Ok, thanks for clearing up my confusion.
Thanks,
-Jeff
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-11-18 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 9:30 [RFC PATCH 4/4] xfs: implement parallism quota check Jeff Liu
2013-11-15 17:26 ` Christoph Hellwig
2013-11-17 13:01 ` Jeff Liu
2013-11-18 11:04 ` Christoph Hellwig
2013-11-18 12:41 ` Jeff Liu [this message]
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=528A0AE5.40702@oracle.com \
--to=jeff.liu@oracle.com \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.