The qs was regarding mkfs not fsck.
On 03/01/2011 11:41 PM, Thomas Lau wrote:
Does it means OCFS2 don't require to be offline to do fsck ?
On 02/03/2011 2:43 PM, Sunil Mushran wrote:
The real error should be in dmesg. Guessing it was unable to connect to all
nodes.
On Mar 1, 2011, at 9:23 PM
This is not a coherent shared disk environment. The iscsi target
has no idea that the device is also being updated from another
source.
On 03/02/2011 04:30 PM, Nikola Savic wrote:
Hello,
I have 3 node setup using CentOS 5.5 and OCFS2 1.4. Disks from two nodes
(node1 and node2) are connect
Hello,
I have 3 node setup using CentOS 5.5 and OCFS2 1.4. Disks from two
nodes (node1 and node2) are connected using DRBD (primary/primary mode)
and this shared storage should be accessable from all three nodes.
Because of that, node1 has the iSCSI target setup on top the /dev/drbd1
devi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sunil Mushran [01.03.2011 17:48]:
> Note that EL5 is _not_ 2.6.18. That version was merely the starting
> point. The kernel versions listed in mkfs manpage refer to pure
> unadulterated mainline kernel versions.
My colleage had a complete run of up2d
