> > When you speak of pre-allocation, do you suggest using
> > ioctl interface to explicitly reserve blocks in advance?
> Yes, thats the one.
> > Can it guarantee contiguous chunk allocation?
> No, but it does the best it can under the circumstances,
> which is usually pretty good.
> > management, isn't it? Basically you pay for unfragmented contiguous
> > block layout with extra disk space reserved for unwritten data.
> But its not really "extra" if you know you're going to use it,
> > If so, why offer custom extent size in the first place?
> Its a different concept, solving different problems really. One is
> at the extent level, the other is at (typically large) ranges of
> bytes that can be more than an extent.
> One is a "harder" guarantee than the the other of getting contiguous
> space, as they call into the allocator in different ways.
I think that I'll go for the custom extent size as the harder guarantee
against fragmentation. It also looks to me that custom extent is easier
for application to implement.
Are there any other reasons why NOT use custom extent size?
> > [..]
> > > > Do I have to have non-realtime regular section?
> > > Yes. All metadata is stored there.
> > Is there any way I can do sizing of the meta-data?
> I'm not sure what you're asking there...?
Provided I have 150G real-time section, how can I estimate a size of
data section that I need to allocate in order to store filesystem
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around