From: Emmanuel Florac <eflorac@intellique.com>
To: xfs@oss.sgi.com
Subject: Re: Calculating swidth On A RAID6 Volume
Date: Tue, 20 Jul 2010 17:27:04 +0200 [thread overview]
Message-ID: <20100720172704.609477f4@harpe.intellique.com> (raw)
In-Reply-To: <201007201700.51977@zmi.at>
[-- Attachment #1.1: Type: text/plain, Size: 926 bytes --]
Le Tue, 20 Jul 2010 17:00:51 +0200
Michael Monnerie <michael.monnerie@is.it-management.at> écrivait:
> I'd say using su+sw is more future proof than swidth+sunit, as 4K
> sector drives will become standard, and then using 512B units will be
> outdated anyway, right?
Absolutely, and furthermore I'm wondering what's happening in the
case where the drives have 4096 bytes blocks; I suppose then sunit
should be expressed as a number of 4096 bytes blocks, and what about
swidth ? the hell if I know :) This is also probably a nice little nest
of coming filesystem bugs to be hatched :=)
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-07-20 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 12:06 Calculating swidth On A RAID6 Volume Andrew Debenham
2010-07-20 12:40 ` Michael Weissenbacher
2010-07-20 13:22 ` Michael Monnerie
2010-07-20 14:13 ` Michael Weissenbacher
2010-07-20 14:44 ` Emmanuel Florac
2010-07-20 15:00 ` Michael Monnerie
2010-07-20 15:27 ` Emmanuel Florac [this message]
2010-07-21 6:54 ` Dave Chinner
2010-07-20 15:04 ` Michael Monnerie
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=20100720172704.609477f4@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=xfs@oss.sgi.com \
/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