Sunil, Hmm, I thought you meant the cluster size.
Regards, Luis --- On Wed, 1/28/09, Sunil Mushran <sunil.mush...@oracle.com> wrote: From: Sunil Mushran <sunil.mush...@oracle.com> Subject: Re: [Ocfs2-users] ocfs2 hangs during webserver usage To: lfreita...@yahoo.com Cc: ocfs2-users@oss.oracle.com Date: Wednesday, January 28, 2009, 1:08 AM Luis Freitas wrote: > The extent size would play a role on this also, as Sunil pointed. You could check if the extent size is different on your test environment. The mkfs tool might have defaulted a larger extent size if the total size of the filesystem is larger. (Sunil, correct me on this if I am wrong). The extend size I was referring to is not related to any ondisk size. It depends on the location the write() is issued to. Say you have a 100K sized file and you issue a write() at offset 1G. If the fs supports sparse files, it will allocate (and init) blocks only around the 1G location, leaving a hole in between. A non-sparsefile supporting fs, on the other hand, will need to allocate (and init) the entire space between 100K and 1G.
_______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users