From: Boaz Harrosh <bharrosh@panasas.com>
To: Idan Kedar <idank@tonian.com>
Cc: Johannes Schild <JSchild@gmx.de>, <osd-dev@open-osd.org>,
<linux-nfs@vger.kernel.org>
Subject: Re: Questions about Exofs
Date: Wed, 16 May 2012 15:15:32 +0300 [thread overview]
Message-ID: <4FB39A64.1040909@panasas.com> (raw)
In-Reply-To: <CABpMAy+OWcp7VAOGK4nYWfcY4iZ9a1WQHPUbh5pxotYL9yy+KA@mail.gmail.com>
On 05/15/2012 07:21 PM, Idan Kedar wrote:
>>> By the way, several weeks I have tried setting up a RAID 5 environment
>>> >> with 8 OSDs, 1 mirror and RAID nesting. I then tried cloning and
>>> >> compiling the kernel tree over this pNFS-OSD-RAID. The result was that
>>> >> otgtd died, and I don't know why. It didn't dump core anywhere I could
>>> >> find and the only "log" it has - stdout - didn't give any useful info.
>>> >> I was going to inquire about this in a couple of weeks when I need to
>>> >> get this environment working, but since this issue came up, maybe we
>>> >> can somehow resolve it sooner.
>> >
>> >
>> > 8 OSDs with a mirror ? what was the mkfs.exofs command line you used?
> Something along the lines of
> # LD_LIBRARY_PATH=lib ./usr/mkfs.exofs --pid=0x10000 --format
> --mirrors=1 --group_width=2 --group_depth=2 --dev=/dev/osd0
> --osdname=$(uuid) --dev=/dev/osd1 --osdname=$(uuid) --dev=/dev/osd2
> --osdname=$(uuid) ...
>
> I don't remember exactly at the moment, but I will bump this thread
> when I'll start using RAID again.
>> >
BTW I don't see a --raid=5 above but a raid5 of --group_width=2 is just
a mirror. The minimum for --raid=5 is 3. (I'm not sure if
the system checks and optimizes for this)
So the above should probably be:
# LD_LIBRARY_PATH=lib ./usr/mkfs.exofs --pid=0x10000 \
--mirrors=2 --group_width=2 --group_depth=1000 \
--dev=/dev/osd0 --format --osdname=$(uuid) \
--dev=/dev/osd1 --format --osdname=$(uuid) \
--dev=/dev/osd2 --format --osdname=$(uuid) \
...
group_depth is how many times to repeat this group until
advancing to the next group.
The group_count is:
group_count = int( (total_devices / mirrors+1) / group_width )
an interesting raid5 configuration with 8 devices mirrors and groups
can be:
# LD_LIBRARY_PATH=lib ./usr/mkfs.exofs --pid=0x10000 \
--mirrors=1 --raid=5 --group_width=3 --group_depth=1000 \
--dev=/dev/osd0 --format --osdname=$(uuid) \
--dev=/dev/osd1 --format --osdname=$(uuid) \
--dev=/dev/osd2 --format --osdname=$(uuid) \
Which means each file will have only a single group - 3-out-of-4.
but the next file will use another set of 3 devices out of the 4.
And I think you need a --stripe_pages= right?
Cheers
Boaz
next prev parent reply other threads:[~2012-05-16 12:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 9:03 Questions about Exofs Johannes Schild
2012-05-15 9:48 ` Boaz Harrosh
2012-05-15 12:19 ` Johannes Schild
2012-05-15 13:09 ` Idan Kedar
2012-05-15 13:42 ` Boaz Harrosh
2012-05-15 14:22 ` Idan Kedar
2012-05-15 15:06 ` Boaz Harrosh
2012-05-15 16:21 ` Idan Kedar
2012-05-15 17:20 ` Boaz Harrosh
2012-05-16 8:07 ` Idan Kedar
2012-05-16 12:15 ` Boaz Harrosh [this message]
2012-05-16 15:18 ` Idan Kedar
2012-05-15 13:18 ` Boaz Harrosh
2012-05-16 9:00 ` Johannes Schild
2012-05-16 10:30 ` Boaz Harrosh
2012-05-21 13:07 ` Johannes Schild
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=4FB39A64.1040909@panasas.com \
--to=bharrosh@panasas.com \
--cc=JSchild@gmx.de \
--cc=idank@tonian.com \
--cc=linux-nfs@vger.kernel.org \
--cc=osd-dev@open-osd.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).