From: "Linda A. Walsh" <xfs@tlinx.org>
To: Russell Cattelan <cattelan@thebarn.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: does XFS support block sizes other than 512 bytes?
Date: Tue, 28 Jul 2009 18:31:41 -0700 [thread overview]
Message-ID: <4A6FA67D.7080800@tlinx.org> (raw)
In-Reply-To: <4A671E44.4040305@xfs.org>
Russell Cattelan wrote:
>> 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?)
> Yes
> XFS can support any power of 2 sector size up to the page size of your
> system.
> And it is recommend that on things like raid5 devices that the sector
> size be
> set to the same size as the filesystem block size.
>
>> thanks more... :-)
>> -linda
---
Just tried a 146GB-15K Seagate Cheetah SAS. It didn't like anything other than 512bytes. Any larger size ended up with a 528 byte sector size which really miffed the linux kernel so bad, it wouldn't expose it as a device
in /dev. If you don't know mknod and the correct dev num, it would
make for a very interesting time formatting it back down. ;-)
Do you know what brands might allow resizing? You say SATA might
allow...just a WAG...but maybe a Seagate SATA might not? ;^)
Also, I wonder what might happen with a HW RAID card -- if it would
deal with 4K block sizes. It deals with up to 1MB stripe sizes...so
you'd think it'd handle 4K block sizes...???
Thanks for the fun times so far...;^)
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-07-29 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 0:39 does XFS support block sizes other than 512 bytes? Linda A. Walsh
2009-07-20 11:14 ` Michael Monnerie
2009-07-22 14:12 ` Russell Cattelan
2009-07-29 1:31 ` Linda A. Walsh [this message]
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=4A6FA67D.7080800@tlinx.org \
--to=xfs@tlinx.org \
--cc=cattelan@thebarn.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