public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Liu <jeff.liu@oracle.com>
To: Mark Tinguely <tinguely@sgi.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [PATCH 9/10] xfs: implement bulkstat per allocation group
Date: Tue, 31 Dec 2013 18:00:08 +0800	[thread overview]
Message-ID: <52C295A8.2040104@oracle.com> (raw)
In-Reply-To: <52C1B900.8080002@sgi.com>

On 2013年12月31日 02:18, Mark Tinguely wrote:
> On 12/28/13 05:22, Jeff Liu wrote:
>> From: Jie Liu<jeff.liu@oracle.com>
>>
>> With xfs_perag_bulkstat(), we can return stat information in bulk by
>> inode as per the given allocation group number and start inode number
>> in it via a new ioctl(2) in the future.
>>
>> Refactor xfs_bulkstat() with it.
>>
>> Signed-off-by: Jie Liu<jeff.liu@oracle.com>
>> ---
> 
> 
> causes xfs/183 to assert for me:
> 
> XFS: Assertion failed: fs_is_ok, file: /root/xfs/fs/xfs/xfs_itable.c,
> line: 409
Oops!! I guess the assertion is failed at:

+                       error = xfs_inobt_lookup(cur, 0, XFS_LOOKUP_GE, &i);
+                       if (error)
+                               break;
+                       XFS_WANT_CORRUPTED_GOTO(i == 1, error0);

Which means I have to take care of those non-primary AGs on an new initialized
empty-filesystem as there has no inode chunk has been allocated...

Thanks,
-Jeff

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

      reply	other threads:[~2013-12-31 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-28 11:22 [PATCH 9/10] xfs: implement bulkstat per allocation group Jeff Liu
2013-12-30 18:18 ` Mark Tinguely
2013-12-31 10:00   ` 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=52C295A8.2040104@oracle.com \
    --to=jeff.liu@oracle.com \
    --cc=tinguely@sgi.com \
    --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