Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I never really pay block size much attention but obviously there can be benefits to choosing something other than the default. I am looking for a good "best practices" paper on choosing block size. Also, when used on top of LVM is it's performance payoffs or importance negated in any way? TIA

share|improve this question
This needs way more votes. – Prof. Falken Oct 26 '11 at 15:07
up vote 7 down vote accepted

Short answer:


Longer answer:

Larger block sizes reduce fragmentation, at the cost of some wasted space at the end of the block. Having said that, give the size of most hard drives these days, unless you are storing something like a mail or news spool you should use 4096 as it matches the page size (in memory) with the block size on disk.

If you are storing a mail spool, then you should look at using something like XFS which is more efficient at storing large numbers of small files.

share|improve this answer
As far as ext3 with LVM do I need to conern myself with the underlying physical volume extents? Do I need to coordinate between them or anything like that? – CarpeNoctem Feb 28 '10 at 8:56
For a single PV inside a VG probably not, if you add extra PV's to an existing VG, then you'll have to manually rebalance the data across the new volume – Dave Cheney Feb 28 '10 at 8:58
+1 for mem page == sector size. really affects performance. – rytis Feb 28 '10 at 10:21

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.