From: Phil Turmel <philip@turmel.org>
To: Dragon <Sunghost@gmx.de>
Cc: linux-raid@vger.kernel.org
Subject: Re:
Date: Sun, 19 Jun 2011 14:40:58 -0400 [thread overview]
Message-ID: <4DFE42BA.1050500@turmel.org> (raw)
In-Reply-To: <20110618203954.129920@gmx.net>
Hi Dragon,
On 06/18/2011 04:39 PM, Dragon wrote:
> Monitor your background reshape with "cat /proc/mdstat".
>
> When the reshape is complete, the extra disk will be marked "spare".
>
> Then you can use "mdadm --remove".
> -->after a view days the reshape was done and i take the disk out of the raid -> many thx for that
Good to hear.
>> at this point i think i take the disk out of the raid, because i need the space of
> the disk.
>
> Understood, but you are living on the edge. You have no backup, and only one drive
> of redundancy. If one of your drives does fail, the odds of losing the whole array
> while replacing it is significant. Your Samsung drives claim a non-recoverable read
> error rate of 1 per 1x10^15 bits. Your eleven data disks contain 1.32x10^14 bits,
> all of which must be read during rebuild. That means a _13%_ chance of total
> failure while replacing a failed drive.
>
> I hope your 16T of data is not terribly important to you, or is otherwise replaceable.
> --> nice calculation, where do you have the data from?
> --> most of it is important, i will look for a better solution
The error rate is from Samsung, for your HD154UI drives:
http://www.samsung.com/latin_en/consumer/monitor-peripherals-printer/hard-disk-drives/internal/HD154UI/CKW/index.idx?pagetype=prd_detail&tab=specification
error rate = 1 / 1*10^15 = 1x10^-15
The rest comes from your setup:
11 disks * (1465138496 * 1024) bytes/disk * 8 bits/bytes = 1.32026560152e+14
% odds of failure = (data quantity * error rate) * 100%
[...]
> --> and than, ext4 max size is actually 16TB, what should i do?
I've been playing with XFS. The only significant maintenance drawback I've identified is that it cannot be shrunk. Not even offline. It's not really holding me back, though, as I tend to layer LVM on top of my raid arrays, then allocate to specific volumes. I always hold back a substantial fraction of the space for future use of "lvextend".
> --> for an end-user you have many knowledge about swraid ;)
Thank you. I was a geek before I became an engineer :) .
Phil
next prev parent reply other threads:[~2011-06-19 18:40 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 20:39 (unknown) Dragon
2011-06-19 18:40 ` Phil Turmel [this message]
2011-06-21 14:46 ` Mail etiquette Phillip Susi
-- strict thread matches above, loose matches on Subject: below --
2020-08-12 10:54 Alex Anadi
2020-06-24 13:54 Re; test02
2017-11-13 14:55 Amos Kalonzo
2017-05-03 6:23 Re: H.A
2017-04-13 15:58 (unknown), Scott Ellentuch
[not found] ` <CAK2H+efb3iKA5P3yd7uRqJomci6ENvrB1JRBBmtQEpEvyPMe7w@mail.gmail.com>
2017-04-13 16:38 ` Scott Ellentuch
2017-02-23 15:09 Qin's Yanjun
2016-11-06 21:00 (unknown), Dennis Dataopslag
2016-11-07 16:50 ` Wols Lists
2016-11-07 17:13 ` Re: Wols Lists
2016-11-17 20:33 ` Re: Dennis Dataopslag
2016-11-17 22:12 ` Re: Wols Lists
2015-09-30 12:06 Apple-Free-Lotto
2014-11-26 18:38 (unknown), Travis Williams
2014-11-26 20:49 ` NeilBrown
2014-11-29 15:08 ` Re: Peter Grandi
2012-12-25 0:12 (unknown), bobzer
2012-12-25 5:38 ` Phil Turmel
[not found] ` <CADzS=ar9c7hC1Z7HT9pTUEnoPR+jeo8wdexrrsFbVfPnZ9Tbmg@mail.gmail.com>
2012-12-26 2:15 ` Re: Phil Turmel
2012-12-26 11:29 ` Re: bobzer
2012-12-17 0:59 (unknown), Maik Purwin
2012-12-17 3:55 ` Phil Turmel
2011-09-26 4:23 (unknown), Kenn
2011-09-26 4:52 ` NeilBrown
2011-09-26 7:03 ` Re: Roman Mamedov
2011-09-26 23:23 ` Re: Kenn
2011-09-26 7:42 ` Re: Kenn
2011-09-26 8:04 ` Re: NeilBrown
2011-09-26 18:04 ` Re: Kenn
2011-09-26 19:56 ` Re: David Brown
2011-06-10 20:26 (unknown) Dragon
2011-06-11 2:06 ` Phil Turmel
2011-06-09 12:16 (unknown) Dragon
2011-06-09 13:39 ` Phil Turmel
2011-06-09 6:50 (unknown) Dragon
2011-06-09 12:01 ` Phil Turmel
2011-04-10 1:20 Re: Young Chang
2010-11-13 6:01 (unknown), Mike Viau
2010-11-13 19:36 ` Neil Brown
2010-03-08 1:37 (unknown), Leslie Rhorer
2010-03-08 1:53 ` Neil Brown
2010-03-08 2:01 ` Leslie Rhorer
2010-03-08 2:22 ` Michael Evans
2010-03-08 3:20 ` Leslie Rhorer
2010-03-08 3:31 ` Michael Evans
2010-01-06 14:19 (unknown) Lapohos Tibor
2010-01-06 20:21 ` Michael Evans
2010-01-06 20:57 ` Re: Antonio Perez
2009-06-05 0:50 (unknown), Jack Etherington
2009-06-05 1:18 ` Roger Heflin
2009-04-02 4:16 (unknown), Lelsie Rhorer
2009-04-02 4:22 ` David Lethe
2009-04-05 0:12 ` RE: Lelsie Rhorer
2009-04-05 0:38 ` Greg Freemyer
2009-04-05 5:05 ` Lelsie Rhorer
2009-04-05 11:42 ` Greg Freemyer
2009-04-05 0:45 ` Re: Roger Heflin
2009-04-05 5:21 ` Lelsie Rhorer
2009-04-05 5:33 ` RE: David Lethe
2009-04-02 7:33 ` Peter Grandi
2009-04-02 13:35 ` Re: Andrew Burgess
2008-05-14 12:53 (unknown), Henry, Andrew
2008-05-14 21:13 ` David Greaves
2006-05-30 8:06 Jake White
2006-02-26 5:04 Norberto X. Milton
2006-02-15 4:30 Re: Hillary
2006-01-11 14:47 (unknown) bhess
2006-01-12 11:16 ` David Greaves
2006-01-12 17:20 ` Re: Ross Vandegrift
2006-01-17 12:12 ` Re: David Greaves
[not found] <57GDJLHJLEAG07CI@vger.kernel.org>
2005-07-24 10:31 ` Re: jfire
[not found] <4HCKFFJ3GIC1F340@vger.kernel.org>
2005-05-30 2:49 ` Re: bouche
2002-06-04 15:47 (unknown) Colonel
2002-06-04 21:55 ` Jure Pecar
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=4DFE42BA.1050500@turmel.org \
--to=philip@turmel.org \
--cc=Sunghost@gmx.de \
--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).