From: "Peter Kovari" <peter@kovari.priv.hu>
To: linux-raid@vger.kernel.org
Subject: RE: Question regarding --backup-file
Date: Mon, 2 May 2011 19:39:59 +0200 [thread overview]
Message-ID: <001501cc08ef$f60cc620$e2265260$@priv.hu> (raw)
In-Reply-To: <4DBECEFA.1050203@fnarfbargle.com>
> > Hi all,
> >
> > I understand, that a change from RAID5 to RAID6 by adding a single disk
-
> > eg. keeping the number of data disks - requires a backup file throughout
the
> > whole reshape process. For a larger, multi-TB array this means millions
of
> > writes to the backup file, which - if i'm correct - means means millions
of
> > writes to the same physical sectors of the disk that holds the backup
file.
> > Is this not problematic? How many write operations can a typical drive
> > tolerate nowadays? (on the same sectors)
> Lots, where Lots >= 1 and Lots < infinity.
> I've never seen rotating media specify any form of limitation to writes.
> Have you?
No, that's why i'm asking.
Imho, in typical usage, write cycle counts on a certain sector may not be
that high, even on a database server. I doubt it ever goes over a few
hundred thousands during the life cycle of the hard disk. On the other hand,
a single reshape on a larger array can trigger tens of millions of write
cycles on certain sectors. Sectors do fail eventually, so I'm wondering if
the "no limit" is truly a no limit, or manufacturers just won't state this
info because in "normal" usage, customers will never reach that limit.
Btw, i'm sure SSD's are not meant to take such a pressure.
Cheers,
Peter
next prev parent reply other threads:[~2011-05-02 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 15:13 Question regarding --backup-file Peter Kovari
2011-05-02 15:34 ` Brad Campbell
2011-05-02 17:39 ` Peter Kovari [this message]
2011-05-02 19:05 ` David Brown
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='001501cc08ef$f60cc620$e2265260$@priv.hu' \
--to=peter@kovari.priv.hu \
--cc=linux-raid@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).