From: John Robinson <john.robinson@anonymous.org.uk>
To: for.poige+linux@gmail.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Hi! Why having LSR's chunk size 2^n limitation?
Date: Tue, 18 Jan 2011 18:05:47 +0000 [thread overview]
Message-ID: <4D35D67B.20004@anonymous.org.uk> (raw)
In-Reply-To: <AANLkTimn9j08BPvE0hZdBk3NvqJ6_iQELQczBOA8LruO@mail.gmail.com>
On 18/01/2011 17:23, Igor Podlesny wrote:
> On 19 January 2011 00:11, John Robinson<john.robinson@anonymous.org.uk> wrote:
>> On 18/01/2011 15:59, Igor Podlesny wrote:
> [...]
>> You're slightly confusing things. Stripe size and chunk size are different
>> things, but related. Stripe size = number of data discs * chunk size. Linux
> [...]
>
> Am I? Take a look
> http://www.freebsd.org/cgi/man.cgi?query=vinum&apropos=0&sektion=0&manpath=FreeBSD+4.9-RELEASE&format=html
Why should I be reading FreeBSD man pages when this is a Linux list? I
am using the terms stripe size and chunk size in the sense I understand
them, which is I believe the Linux sense. If you and FreeBSD choose to
use the terms differently, so be it, but please don't pull me up about
my use of terms when you're the one using the wrong ones in this context.
[...]
>> Secondly, as far as I know all Linux filesystems are RAID-aware so know how
>
> You're mistaken. There're too many are not.
I'll concede, only all the major filesystems you'd ever use in a
production environment.
> Also, don't forget
> LVM-2 in middle.
Not a problem, the same mechanisms by which filesystems can be aware of
RAID means filesystems are aware of LVM and LVM is aware of RAID.
> P. S. I think now everyone can see why this letter was
> intentionally addressed to the author of LSR, not to the list.
There's absolutely no need for that. Please leave, and take your
condescension, ignorance and offensiveness with you.
Cheers,
John.
next prev parent reply other threads:[~2011-01-18 18:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 15:59 Hi! Why having LSR's chunk size 2^n limitation? Igor Podlesny
2011-01-18 16:46 ` Roberto Spadim
2011-01-18 16:48 ` Roberto Spadim
2011-01-18 16:53 ` Igor Podlesny
2011-01-18 16:59 ` Roberto Spadim
2011-01-18 17:06 ` Roberto Spadim
2011-01-18 17:11 ` John Robinson
2011-01-18 17:22 ` Roberto Spadim
2011-01-18 17:23 ` Igor Podlesny
2011-01-18 18:05 ` John Robinson [this message]
2011-01-18 18:24 ` Igor Podlesny
2011-01-18 18:53 ` Roberto Spadim
2011-01-18 19:44 ` NeilBrown
2011-01-18 20:20 ` Roberto Spadim
2011-01-19 7:41 ` Igor Podlesny
2011-01-19 9:32 ` NeilBrown
2011-01-19 9:34 ` Igor Podlesny
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=4D35D67B.20004@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=for.poige+linux@gmail.com \
--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