From: "Linda A. Walsh" <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>
Subject: does XFS support block sizes other than 512 bytes?
Date: Fri, 17 Jul 2009 17:39:17 -0700 [thread overview]
Message-ID: <4A6119B5.6000706@tlinx.org> (raw)
This one's a bit more specific than the last. If memory serves me,
XFS supported differing block sizes (which you could do on a hardware format
of a SCSI drive) back on IRIX. But when first ported to Linux it didn't
work. Was that ever fixed? I seem to remember that going to 1-2K block sizes
gave and extra 10%, and it almost seems logical that going to a 4kK block size
would be ideal for xfs (presuming your disk doesn't start getting errors,
then it might get harder to remap sectors and you'd hit hard disk failure
(w/o remappable sectors) sooner.
But at least 1K might be a reasonable tradeoff? Been quite a while since
I tried it and don't even know if the SAS drives allow it (if they do, I wonder
if the newer SATA drives do?)
thanks more... :-)
-linda
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-07-18 0:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 0:39 Linda A. Walsh [this message]
2009-07-20 11:14 ` does XFS support block sizes other than 512 bytes? Michael Monnerie
2009-07-22 14:12 ` Russell Cattelan
2009-07-29 1:31 ` Linda A. Walsh
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=4A6119B5.6000706@tlinx.org \
--to=xfs@tlinx.org \
--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