From: Ric Wheeler <ricwheeler@gmail.com>
To: Arne Jansen <sensille@gmx.net>
Cc: chris.mason@oracle.com, linux-btrfs@vger.kernel.org, jansen@webgods.de
Subject: Re: [PATCH v2 0/6] btrfs: scrub
Date: Fri, 11 Mar 2011 11:17:20 -0500 [thread overview]
Message-ID: <4D7A4B10.7050904@gmail.com> (raw)
In-Reply-To: <cover.1299854593.git.sensille@gmx.net>
On 03/11/2011 09:49 AM, Arne Jansen wrote:
> This series adds an initial implementation for scrub. It works quite
> straightforward. The usermode issues an ioctl for each device in the
> fs. For each device, it enumerates the allocated device chunks. For
> each chunk, the contained extents are enumerated and the data checksums
> fetched. The extents are read sequentially and the checksums verified.
> If an error occurs (checksum or EIO), a good copy is searched for. If
> one is found, the bad copy will be rewritten.
> All enumerations happen from the commit roots. During a transaction
> commit, the scrubs get paused and afterwards continue from the new
> roots.
> For future improvements please see the inline comments.
>
> The accompanying user mode patches will follow shortly.
>
> This v2 mainly changes the dev_info ioctl interface.
>
> Thanks,
> Arne
>
Great work!
I do wonder if we should also worry about the unallocated part of the storage
device. Often, with local disks specifically, your unused space might accumulate
errors over time.
What you add to your scrub phase is a simple read operation for the unallocated
ranges (optionally a READ_VERIFY which validates the data on platter without
transferring data over the bus to the host).
The recovery operation here would be to write (zeros) to the block if an error
is detected, so we might be pessimistic and simply use write to "zero" those
unallocated ranges as well. Note that there are "WRITE_SAME" commands that RAID
people use for initializing unused drives for example.
I would not run the overwrite or read check on SSD or arrays so this would be an
optional type of scrub I suppose.
Regards,
Ric
> Arne Jansen (5):
> btrfs: add parameter to btrfs_lookup_csum_range
> btrfs: make struct map_lookup public
> btrfs: add scrub code and prototypes
> btrfs: sync scrub with commit& device removal
> btrfs: add state information for scrub
>
> Jan Schmidt (1):
> btrfs: new ioctls for scrub
>
> fs/btrfs/Makefile | 2 +-
> fs/btrfs/ctree.h | 46 ++-
> fs/btrfs/disk-io.c | 16 +
> fs/btrfs/file-item.c | 8 +-
> fs/btrfs/inode.c | 2 +-
> fs/btrfs/ioctl.c | 131 +++++
> fs/btrfs/ioctl.h | 55 ++
> fs/btrfs/relocation.c | 2 +-
> fs/btrfs/scrub.c | 1463 ++++++++++++++++++++++++++++++++++++++++++++++++
> fs/btrfs/transaction.c | 3 +
> fs/btrfs/tree-log.c | 6 +-
> fs/btrfs/volumes.c | 16 +-
> fs/btrfs/volumes.h | 17 +
> 13 files changed, 1743 insertions(+), 24 deletions(-)
> create mode 100644 fs/btrfs/scrub.c
>
next prev parent reply other threads:[~2011-03-11 16:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 14:49 [PATCH v2 0/6] btrfs: scrub Arne Jansen
2011-03-11 14:49 ` [PATCH v2 1/6] btrfs: add parameter to btrfs_lookup_csum_range Arne Jansen
2011-03-11 14:49 ` [PATCH v2 2/6] btrfs: make struct map_lookup public Arne Jansen
2011-03-11 14:49 ` [PATCH v2 3/6] btrfs: add scrub code and prototypes Arne Jansen
2011-03-11 16:34 ` David Sterba
2011-03-12 10:54 ` Arne Jansen
2011-03-22 16:38 ` David Sterba
2011-03-23 14:19 ` Arne Jansen
2011-03-11 14:49 ` [PATCH v2 4/6] btrfs: sync scrub with commit & device removal Arne Jansen
2011-03-11 14:49 ` [PATCH v2 5/6] btrfs: add state information for scrub Arne Jansen
2011-03-11 16:53 ` David Sterba
2011-03-12 13:13 ` Arne Jansen
2011-03-11 14:49 ` [PATCH v2 6/6] btrfs: new ioctls " Arne Jansen
2011-03-11 16:17 ` Ric Wheeler [this message]
2011-03-12 13:20 ` [PATCH v2 0/6] btrfs: scrub Arne Jansen
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=4D7A4B10.7050904@gmail.com \
--to=ricwheeler@gmail.com \
--cc=chris.mason@oracle.com \
--cc=jansen@webgods.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=sensille@gmx.net \
/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).