linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: linux-btrfs@vger.kernel.org
Cc: Miao Xie <miaox@cn.fujitsu.com>, Jan Schmidt <list.btrfs@jan-o-sch.net>
Subject: bi_vcnt checks for repair
Date: Thu, 10 Nov 2016 12:06:01 -0800	[thread overview]
Message-ID: <20161110200601.GA2859@infradead.org> (raw)

Hi all,

btrfs_check_repairable and bio_readpage_error have somewhat odd
looking check for bi_vcnt, checking on how to proceed based on that.

Does anyone remember what they actually are checking for?  Depending
on the exact devices merging bi_vcnt can mean quite a few different
things, and we should probably check for what people actually intended
to check.

The suspect for adding these checks are in Cc, although the commit
history is a bit murky.

             reply	other threads:[~2016-11-10 20:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10 20:06 Christoph Hellwig [this message]
2016-11-11 19:31 ` bi_vcnt checks for repair Liu Bo
2016-11-12 17:34   ` Christoph Hellwig

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=20161110200601.GA2859@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=list.btrfs@jan-o-sch.net \
    --cc=miaox@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).