From: Michal Soltys <soltys@ziu.info>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Using the new bad-block-log in md for Linux 3.1
Date: Thu, 28 Jul 2011 14:53:36 +0200 [thread overview]
Message-ID: <4E315BD0.7040400@ziu.info> (raw)
In-Reply-To: <20110727141652.7511fc51@notabene.brown>
W dniu 27.07.2011 06:16, NeilBrown pisze:
>
> If you create an array with this mdadm it will add a bad block log - you
> cannot turn it off (it is only 4K long so why would you want to). Then as
> errors occur they will cause the faulty block to be added to the log rather
> than the device to be remove from the array.
I was wondering, 4KiB is "just" 512 entries assuming these are only
64bit sector addresses - it's possible to imagine a failing drive with
lots of not reloctable (for whatever reason) adjacent sectors, that
could fill up the log relatively quickly (mentioned 512 entries ~ 256KiB
worth of data on 512b drives, just a few chunks before the drive is
kicked out). Though - how realistic such scenario is with modern drives,
is hard for me to judge.
Still - are there any plans to make that 4KiB size not hardcoded, also
perhaps along with customizable offset to the 1st chunk ?
Something of analogous functionality to lvm's options such as:
--metadatasize
--dataalignment
--dataalignmentoffset
(though again, hard to judge if there's any practical use for those
aside exotic scenarios)
prev parent reply other threads:[~2011-07-28 12:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 4:16 Using the new bad-block-log in md for Linux 3.1 NeilBrown
2011-07-27 6:21 ` keld
2011-07-27 6:49 ` NeilBrown
2011-07-27 8:17 ` keld
2011-07-27 10:22 ` Mikael Abrahamsson
2011-07-27 12:30 ` Lutz Vieweg
2011-07-27 12:44 ` John Robinson
2011-07-27 13:06 ` Lutz Vieweg
2011-07-27 13:23 ` Lutz Vieweg
2011-07-27 20:55 ` NeilBrown
2011-07-28 9:25 ` Lutz Vieweg
2011-07-28 9:55 ` John Robinson
2011-07-28 12:53 ` Michal Soltys [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=4E315BD0.7040400@ziu.info \
--to=soltys@ziu.info \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).