Not really. The mainline tree is labeled 1.3.x because it is the tree
we add new features too. But bug fixes are applied to both 1.2 and
1.3 separately so it is hard to tell by the version# alone.

This is the fix in the git tree:

commit 4b1af774451bbc8440719e3fe441934a337c3b63
Author: Kurt Hackel <[EMAIL PROTECTED]>
Date:   Mon Jun 26 15:17:47 2006 -0700

   ocfs2: Fix lvb corruption

Properly ignore LVB flags during a PR downconvert. This avoids an illegal
   lvb update.

   Signed-off-by: Kurt Hackel <[EMAIL PROTECTED]>
   Signed-off-by: Mark Fasheh <[EMAIL PROTECTED]>

davide rossetti wrote:


On 1/23/07, *Sunil Mushran* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    This was the lvb issue that was fixed long ago. In the 1.2 tree,
    it was
    fixed in 1.2.2.
    2.6.18 should definitely have the fix for this.


it seems it's even more recent:

/var/log/messages.4:Dec 27 19:40:40 rack1 kernel: OCFS2 Node Manager 1.3.3
/var/log/messages.4:Dec 27 19:40:40 rack1 kernel: OCFS2 DLM 1.3.3
/var/log/messages.4:Dec 27 19:40:40 rack1 kernel: OCFS2 DLMFS 1.3.3
/var/log/messages.4:Dec 27 19:40:40 rack1 kernel: OCFS2 User DLM kernel interface loaded /var/log/messages.4:Dec 27 19:40:40 rack1 kernel: SELinux: initialized (dev ocfs2_dlmfs, type ocfs2_dlmfs), not configured for labeling
/var/log/messages.4:Dec 27 19:40:44 rack1 kernel: OCFS2 1.3.3


--
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ICQ:290677265 SKYPE:d.rossetti

_______________________________________________
Ocfs2-users mailing list
Ocfs2-users@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-users

Reply via email to