From: Konstantinos Skarlatos <k.skarlatos@gmail.com>
To: "André-Sebastian Liebe" <andre@lianse.eu>, linux-btrfs@vger.kernel.org
Subject: Re: mount time of multi-disk arrays
Date: Mon, 07 Jul 2014 16:54:05 +0300 [thread overview]
Message-ID: <53BAA67D.1050101@gmail.com> (raw)
In-Reply-To: <53BAA2E5.2090801@lianse.eu>
On 7/7/2014 4:38 μμ, André-Sebastian Liebe wrote:
> Hello List,
>
> can anyone tell me how much time is acceptable and assumable for a
> multi-disk btrfs array with classical hard disk drives to mount?
>
> I'm having a bit of trouble with my current systemd setup, because it
> couldn't mount my btrfs raid anymore after adding the 5th drive. With
> the 4 drive setup it failed to mount once in a few times. Now it fails
> everytime because the default timeout of 1m 30s is reached and mount is
> aborted.
> My last 10 manual mounts took between 1m57s and 2m12s to finish.
I have the exact same problem, and have to manually mount my large
multi-disk btrfs filesystems, so I would be interested in a solution as
well.
>
> My hardware setup contains a
> - Intel Core i7 4770
> - Kernel 3.15.2-1-ARCH
> - 32GB RAM
> - dev 1-4 are 4TB Seagate ST4000DM000 (5900rpm)
> - dev 5 is a 4TB Wstern Digital WDC WD40EFRX (5400rpm)
>
> Thanks in advance
>
> André-Sebastian Liebe
> --------------------------------------------------------------------------------------------------
>
> # btrfs fi sh
> Label: 'apc01_pool0' uuid: 066141c6-16ca-4a30-b55c-e606b90ad0fb
> Total devices 5 FS bytes used 14.21TiB
> devid 1 size 3.64TiB used 2.86TiB path /dev/sdd
> devid 2 size 3.64TiB used 2.86TiB path /dev/sdc
> devid 3 size 3.64TiB used 2.86TiB path /dev/sdf
> devid 4 size 3.64TiB used 2.86TiB path /dev/sde
> devid 5 size 3.64TiB used 2.88TiB path /dev/sdb
>
> Btrfs v3.14.2-dirty
>
> # btrfs fi df /data/pool0/
> Data, single: total=14.28TiB, used=14.19TiB
> System, RAID1: total=8.00MiB, used=1.54MiB
> Metadata, RAID1: total=26.00GiB, used=20.20GiB
> unknown, single: total=512.00MiB, used=0.00
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Konstantinos Skarlatos
next prev parent reply other threads:[~2014-07-07 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 13:38 mount time of multi-disk arrays André-Sebastian Liebe
2014-07-07 13:54 ` Konstantinos Skarlatos [this message]
2014-07-07 14:14 ` Austin S Hemmelgarn
2014-07-07 16:57 ` André-Sebastian Liebe
2014-07-07 14:24 ` André-Sebastian Liebe
2014-07-07 22:34 ` Konstantinos Skarlatos
2014-07-07 15:48 ` Duncan
2014-07-07 16:40 ` Benjamin O'Connor
2014-07-07 22:31 ` Konstantinos Skarlatos
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=53BAA67D.1050101@gmail.com \
--to=k.skarlatos@gmail.com \
--cc=andre@lianse.eu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.