From: Stefan Behrens <sbehrens@giantdisaster.de>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] Btrfs: change scrub to support big blocks
Date: Fri, 23 Mar 2012 15:59:07 +0100 [thread overview]
Message-ID: <cover.1332513438.git.sbehrens@giantdisaster.de> (raw)
Scrub used to be coded for nodesize == leafsize == sectorsize == PAGE_SIZE.
This is now changed to support nodesize == leafsize == N * PAGE_SIZE.
The "Btrfs: fix scrub statistics report" patch that I sent on 2/10/2012
is also superseeded by this patch. This new patch includes similar
functionality.
Stefan Behrens (3):
Btrfs: introduce common define for max number of mirrors
Btrfs: minor cleanup in scrub
Btrfs: change scrub to support big blocks
fs/btrfs/ctree.h | 2 +
fs/btrfs/reada.c | 10 +-
fs/btrfs/scrub.c | 1380 ++++++++++++++++++++++++++++++++++++++++--------------
3 files changed, 1028 insertions(+), 364 deletions(-)
--
1.7.3.4
next reply other threads:[~2012-03-23 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 14:59 Stefan Behrens [this message]
2012-03-23 14:59 ` [PATCH 1/3] Btrfs: introduce common define for max number of mirrors Stefan Behrens
2012-03-23 14:59 ` [PATCH 2/3] Btrfs: minor cleanup in scrub Stefan Behrens
2012-03-23 14:59 ` [PATCH 3/3] Btrfs: change scrub to support big blocks Stefan Behrens
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.1332513438.git.sbehrens@giantdisaster.de \
--to=sbehrens@giantdisaster.de \
--cc=linux-btrfs@vger.kernel.org \
/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).