From: Dave Chinner <david@fromorbit.com>
To: Alex Lyakas <alex@zadarastorage.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Danny Shavit <danny@zadarastorage.com>,
Shyam Kaushik <shyam@zadarastorage.com>,
Yair Hershko <yair@zadarastorage.com>,
xfs@oss.sgi.com
Subject: Re: xfs resize: primary superblock is not updated immediately
Date: Fri, 4 Mar 2016 08:31:08 +1100 [thread overview]
Message-ID: <20160303213108.GQ30721@dastard> (raw)
In-Reply-To: <E965894DE8D542788CCE98F72C218C05@alyakaslap>
On Thu, Mar 03, 2016 at 11:18:43AM +0200, Alex Lyakas wrote:
> Hello Dave,
> Thanks for the patch! I confirm that it fixes the scenario.
>
> At [1] please find all the blknos that are being used during the log
> recovery (if that's of any interest).
....
> Mar 3 11:17:41 vc-00-00-350-dev kernel: [ 68.129739]
> _xfs_buf_find: blkno=200705 eofs=204800 >m_sb.sb_dblocks=25600
> Mar 3 11:17:41 vc-00-00-350-dev kernel: [ 68.129746]
> _xfs_buf_find: blkno=200705 eofs=204800 >m_sb.sb_dblocks=25600
Where is the warning that this block is out of range?
And why didn't recovery fail at this point because the block
requested is out of range and so the buffer lookup should have
failed?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-03-03 21:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3685DFAD20214109878873CF81232704@alyakaslap>
2016-02-22 21:20 ` xfs resize: primary superblock is not updated immediately Dave Chinner
2016-02-22 22:38 ` Alex Lyakas
2016-02-22 23:56 ` Dave Chinner
2016-02-23 12:25 ` Alex Lyakas
2016-02-23 22:59 ` Dave Chinner
2016-02-29 9:47 ` Alex Lyakas
2016-02-29 21:16 ` Dave Chinner
2016-03-01 7:20 ` Dave Chinner
2016-03-02 13:14 ` Fanael Linithien
2016-03-03 9:18 ` Alex Lyakas
2016-03-03 21:31 ` Dave Chinner [this message]
2016-03-06 9:46 ` Alex Lyakas
2016-03-06 15:46 ` Eric Sandeen
2016-03-06 20:49 ` Dave Chinner
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=20160303213108.GQ30721@dastard \
--to=david@fromorbit.com \
--cc=alex@zadarastorage.com \
--cc=danny@zadarastorage.com \
--cc=hch@infradead.org \
--cc=shyam@zadarastorage.com \
--cc=xfs@oss.sgi.com \
--cc=yair@zadarastorage.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