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
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
On Mon, Jul 28, 2008 at 10:23:14AM -0700, Sunil Mushran wrote:
Two inits take time.
1. Cluster group init.
2. Journal init.
Also, joining the cluster takes time. You are overwriting an
existing volume. mkfs.ocfs2 will start up the cluster software to
ensure another node is not using
Hi,
We are haing some serious issues trying to configure an OCFS2 cluster on 3 SLES
10 SP2 boxes running in VMware ESX 3.0.1. Before I go into any of the detailed
errors we are experiencing I first wanted to ask everyone if they have
successfully configured this solution? We would be
We run a similar set up, SLES 10 SP1, we were ESX 3.0.x and are now 3.5.
We're running the version of ocfs2 that shipped with SLES 10 SP1.
4 nodes accessing raw mapped LUNs via ESX from an HP SAN on HP Blade
Servers. Qlogic HBAs, standard NICs; nothing special.
The biggest hurdle we ran into was
SLES10 SP2 is shipping OCFS2 1.4. We will releasing the
same for (RH)EL in the coming weeks.
-Original Message-
From Haydn Cahir [EMAIL PROTECTED]
Sent Mon 7/28/2008 8:07 PM
To ocfs2-users@oss.oracle.com
Subject Re: [Ocfs2-users] OCFS2 and VMware ESX
Hi Mark,
Thanks for your reply. How
