Two inits take time.
1. Cluster group init.
2. Journal init.
Considering this is a 16TB volume being formatted with
4K/4K block/cluster sizes, means it has 127074 cluster groups
to initialize. So 127074 4K blocks to initialize. But this bit
should be somewhat similar to ext3.
Journal initialization involves more work than ext3 as not only
do we have to initialize more journals (one per slot to account
for each mounting node), but the journal sizes are larger.
File an enhancement for the counter. We had a spinning wheel for
the journal init but was removed for some reason I do not recall.
Sunil
Sabuj Pattanayek wrote:> Hi,
>
> Why does mkfs.ocfs2 take so long compared to gfs2 (pretty fast iirc),
> xfs (almost instantaneous), or ext3 (slow but still ok)? I'm using:
>
> # mkfs.ocfs2 -F -b 4k -C 4k -L san1 -T mail /dev/vg/san1
> mkfs.ocfs2 1.3.9
> Overwriting existing ocfs2 partition.
> WARNING: Cluster check disabled.
> Proceed (y/N): y
> Filesystem Type of mail
> Filesystem label=san1
> Block size=4096 (bits=12)
> Cluster size=4096 (bits=12)
> Volume size=16789027160064 (4098883584 clusters) (4098883584 blocks)
> 127074 cluster groups (tail covers 16896 clusters, rest cover 32256
clusters)
> Journal size=268435456
> Initial number of node slots: 4
> Creating bitmaps: done
> Initializing superblock: done
> Writing system files: done
> Writing superblock: done
> Writing backup superblock:
>
> Perhaps some kind of inode done/total counter would be nice as is
> shown while doing mkfs.ext3?
>
> Thanks,
> Sabuj Pattanayek
>
> _______________________________________________
> Ocfs2-users mailing list
> Ocfs2-users at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-users
>