PROTECTED]
Sent: zaterdag 4 oktober 2008 2:45
To: Christian van Barneveld
Cc: 'ocfs2-users@oss.oracle.com'
Subject: Re: [Ocfs2-users] ocfs2 kernel BUG
This is the same as issue.
http://oss.oracle.com/bugzilla/show_bug.cgi?id=1012
Is this happening frequently? We have failed to reproduce it in
our
This is the same as issue.
http://oss.oracle.com/bugzilla/show_bug.cgi?id=1012
Is this happening frequently? We have failed to reproduce it in
our test cluster.
If you can reproduce it, I could give you a potential fix for testing.
Let me know.
Sunil
Christian van Barneveld wrote:
Hi,
The
Hi,
we had this entries in /var/log/messeges a few days ago:
Jul 28 23:30:47 xxx kernel: (12268,2):ocfs2_extend_file:790 ERROR: bug
expression: i_size_read(inode) != (le64_to_cpu(fe-i_size) - *bytes_extended)
Jul 28 23:30:47 xxx kernel: (12268,2):ocfs2_extend_file:790 ERROR: Inode
8323098
Hi,
Please provide the detail info of ocfs2 version which may be helpful
for diagnose.
Peter Selzner wrote:
Hi,
we had this entries in /var/log/messeges a few days ago:
Jul 28 23:30:47 xxx kernel: (12268,2):ocfs2_extend_file:790 ERROR: bug
expression: i_size_read(inode) !=
* Tao Ma [EMAIL PROTECTED] [01.08.08 10:58]
Hi,
hanks for your quick reply.
Here the details:
xxx:/ # SPident
CONCLUSION: System is up-to-date!
foundSLE-10-i386-SP1 + online updates
xxx:/ # uname -r
2.6.16.46-0.12-bigsmp
xxx:/ # cat /proc/fs/ocfs2/version
OCFS2 1.2.5-SLES-r2997 Tue
On 1/25/07, Sunil Mushran [EMAIL PROTECTED] wrote:
This is not a fs issue. As in the file must be alright. This is a dlm
issue.
The fs is asking the dlm to free the lock and the dlm is stuck. How many
nodes do you have? We've fixed a bunch of dlm bugs since what you appear
to be running.
I rebooted the two faulty nodes.
now, I can't access anymore the file which was involved in the crash:
/mi11/simma/ghmc/m24/JOB.log
using the faq document, I'm trying to check the situation:
Lockres: M003d60c63da894d788 Mode: No Lock
Flags: Initialized Attached Busy
RO Holders: 0
On 1/23/07, Sunil Mushran [EMAIL PROTECTED] wrote:
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
This is not a fs issue. As in the file must be alright. This is a dlm issue.
The fs is asking the dlm to free the lock and the dlm is stuck. How many
nodes do you have? We've fixed a bunch of dlm bugs since what you appear
to be running.
davide rossetti wrote:
I rebooted the two faulty nodes.
OS: Fedora Core release 4 (Stentz)
KERNEL: Linux rack1.ape 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:57:02 EDT
2006 i686 i686 i386 GNU/Linux
CLUSTER: 11 Linux kernels, mixed environment FC4,FC5,FC6
SAN: FC Infortrend storage, QLogic16 port FC switch, FC adapter LSI FC929X
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.
davide rossetti wrote:
OS: Fedora Core release 4 (Stentz)
KERNEL: Linux rack1.ape 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11
22:57:02 EDT 2006 i686 i686 i386
On 1/23/07, Sunil Mushran [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
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
13 matches
Mail list logo
