From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Error message shows when create and rmdir
Date: Thu Aug 5 20:27:39 2004 [thread overview]
Message-ID: <20040806012709.GP8008@ca-server1.us.oracle.com> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F84051672AF@pdsmsx403>
On Fri, Aug 06, 2004 at 08:59:19AM +0800, Ling, Xiaofeng wrote:
> Try this on 2.6.6 for svn 1303, this also exist on prev version.
>
> Two node with /ocfs mount to the same disk.
> 1.node 0: mkdir /ocfs/a
> 2.node 1: rmdir /ocfs/a
> after a while, when the journal commited.
> It shows:
> (18503) commit_thread: flushed 1 transactions, releasing 3 locks
> (18503) commit_thread: after optimization, 3 locks to release
> (18503) ERROR at /home/xling/ocfs/ocfs2/src/bitmap.c, 408:
> bitmap->validbits =
> 0 but start = 277 and num = 1!
Do you get the last message on node 0 or node 1? I'm guessing node 1, as it
looks like the commit thread is dropping the last reference on the inode
(which is fine in and of itself). So you're probably in delete_inode dumping
the data for the directory. Can you reproduce this at will?
--Mark
>
> see bug 115
>
> -------------------
> Intel China Software Lab.
> iNet: 8-752-1243
> 021-52574545-1243(O)
> xfling@users.sourceforge.net
> Opinions are my own and don't represent those of my employer
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel@oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-devel
--
Mark Fasheh
Software Developer, Oracle Corp
mark.fasheh@oracle.com
next prev parent reply other threads:[~2004-08-05 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 19:59 [Ocfs2-devel] Error message shows when create and rmdir Ling, Xiaofeng
2004-08-05 20:27 ` Mark Fasheh [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-05 21:17 Ling, Xiaofeng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040806012709.GP8008@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.