Displaying 2 results from an estimated 2 matches for "ocfs2_journal_wipe".
2006 Jun 25
1
Error while Mounting
..._node_info:1019 I am node 0
(3575,0):__dlm_print_nodes:377 Nodes in my domain
("E09A0D90C8454749B81E9754438611B8"):
(3575,0):__dlm_print_nodes:381 node 0
(3575,0):__dlm_print_nodes:381 node 1
(3575,0):ocfs2_find_slot:267 taking node slot 1
JBD: no valid journal superblock found
(3575,0):ocfs2_journal_wipe:814 ERROR: status = -22
(3575,0):ocfs2_check_volume:1581 ERROR: status = -22
(3575,0):ocfs2_mount_volume:1087 ERROR: status = -22
ocfs2: Unmounting device (8,16) on (node 0)
(3577,0):o2net_set_nn_state:400 no longer connected to node bsp (num 1) at
10.1.1.11:7777
-------------- next part ----------...
2008 Sep 04
4
[PATCH 0/3] ocfs2: Switch over to JBD2.
ocfs2 currently uses the Journaled Block Device (JBD) for its
journaling. This is a very stable and tested codebase. However, JBD
is limited by architecture to 32bit block numbers. This means an ocfs2
filesystem is limited to 2^32 blocks. With a 4K blocksize, that's 16TB.
People want larger volumes.
Fortunately, there is now JBD2. JBD2 adds 64bit block number support
and some other