ext4 on 32GB SD card.

ext4 on 32GB SD card.

[James Courtier-Dutton]

Hi,

I wish to use an SD card in an embedded device use the ext4 filesystem on it.
How much RAM would ext4 need to support this?
I am assuming ext4 holds some sort of allocation table/metadata in RAM.

Kind Regards

James

Re: ext4 on 32GB SD card.

[Ted Ts'o]

On Fri, Nov 11, 2011 at 12:31:19PM +0000, James Courtier-Dutton wrote:
> 
> I wish to use an SD card in an embedded device use the ext4 filesystem on it.
> How much RAM would ext4 need to support this?
> I am assuming ext4 holds some sort of allocation table/metadata in RAM.

The minimum amount of space which ext4 keeps pinned in memory for a
32G file system is 3 4k blocks, plus an in-core memory.  If you
include things like the root directory that always have to be there,
we're talking maybe 24k or so.  Of course, the moment you actually
*do* something with the file system more metadata will get paged in,
and if you are running with very little memory, blocks will get pushed
out of memory, and then will have to read back into memory, and things
like delayed allocation won't work as well.

So you have to distinguish between "the bare minimum so you can mount
a file system", and "what you need so that you have acceptably good
performance for your workload" --- and that's going to be very
dependent on your workload.

Also, note that with performance, it's highly dependant on the SD
card; some SD cards are crap, and only support one write window at a
time, and others may support 8 or more write windows.

The other question is making sure you have enough memory so that you
can run e2fsck on a 32GB file system.

In general, the best thing to do is to try it, and see if it works.

Regards,

						- Ted

Re: ext4 on 32GB SD card.

[Andreas Dilger]

On 2011-11-11, at 6:20 PM, Ted Ts'o wrote:
> On Fri, Nov 11, 2011 at 12:31:19PM +0000, James Courtier-Dutton wrote:
>> 
>> I wish to use an SD card in an embedded device use the ext4 filesystem on it.
>> How much RAM would ext4 need to support this?
>> I am assuming ext4 holds some sort of allocation table/metadata in RAM.
> 
> The minimum amount of space which ext4 keeps pinned in memory for a
> 32G file system is 3 4k blocks, plus an in-core memory.  If you
> include things like the root directory that always have to be there,
> we're talking maybe 24k or so.  Of course, the moment you actually
> *do* something with the file system more metadata will get paged in,
> and if you are running with very little memory, blocks will get pushed
> out of memory, and then will have to read back into memory, and things
> like delayed allocation won't work as well.

Also, if you are running with a journal (which most ext4 users are),
the memory of the journal can be pinned in RAM as well.  The minimum
journal size is 1024 blocks, or 4MB with 4kB blocksize.  If your IO
or metadata rate is relatively low, then having a small journal is not
a serious impact to the performance.

> So you have to distinguish between "the bare minimum so you can mount
> a file system", and "what you need so that you have acceptably good
> performance for your workload" --- and that's going to be very
> dependent on your workload.
> 
> Also, note that with performance, it's highly dependant on the SD
> card; some SD cards are crap, and only support one write window at a
> time, and others may support 8 or more write windows.
> 
> The other question is making sure you have enough memory so that you
> can run e2fsck on a 32GB file system.
> 
> In general, the best thing to do is to try it, and see if it works.
> 
> Regards,
> 
> 						- Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


Cheers, Andreas