From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vladimir Saveliev Subject: Re: Bug report Date: Mon, 11 Apr 2005 19:30:28 +0400 Message-ID: <1113233427.4420.221.camel@tribesman.namesys.com> References: <5a59ce530504110707e0a4791@mail.gmail.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <5a59ce530504110707e0a4791@mail.gmail.com> List-Id: Content-Type: text/plain; charset="us-ascii" To: studdugie Cc: reiserfs-mailing-list Hello On Mon, 2005-04-11 at 18:07, studdugie wrote: > Hello. I've just joined the reiserfs mailing list today because I need > to report a bug in reiser4. If this list is not the appropriate place > to report bugs, firstly, my apologies. Finally, I would appreciate > some guidance about the appropriate outlet. > > I'm in quasi testing of reiser4 mode insofar as this box is concerned > and the specific app that trigged the failure but eventually I'm going > to need the app to complete w/o failure. If you (the reiser gurus) > think this is the sort of thing that has already been solved or can be > wrapped up in a short amount of time I would be glad to continue > pounding reiser4 and giving feedback. > Can you describe how to reproduce this problem? This looks like a problem we encounter from time to time. > > ------------[ cut here ]------------ > kernel BUG at fs/reiser4/plugin/file/tail_conversion.c:32! > invalid operand: 0000 [#1] > SMP > Modules linked in: > CPU: 0 > EIP: 0060:[] Not tainted VLI > EFLAGS: 00010282 (2.6.11-mm2) > EIP is at get_exclusive_access+0x2f/0x40 > eax: f2d5035c ebx: f2d503c4 ecx: f73c3c98 edx: e5946e80 > esi: f2d5035c edi: f7df1d68 ebp: f7df1f3c esp: f7df1d34 > ds: 007b es: 007b ss: 0068 > Process pdflush (pid: 111, threadinfo=f7df0000 task=c43a3020) > Stack: c0210be1 f2d5035c f7df1f3c c0208148 c04c8ba0 f2d503c4 c01ea5b1 f2d503c4 > f7344c00 f7df1e6c 00000000 00000000 00000008 00000000 00000000 00000000 > 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > Call Trace: > [] pre_delete_unix_file+0x21/0x50 > [] kill_cursors+0x18/0x20 > [] delete_inode_common+0x191/0x200 > [] drop_common+0x49/0x50 > [] reiser4_drop_inode+0x20/0x40 > [] iput+0x63/0x90 > [] generic_sync_sb_inodes+0x217/0x2d0 > [] pdflush+0x0/0x30 > [] reiser4_sync_inodes+0x4c/0xa0 > [] sync_sb_inodes+0x2e/0x40 > [] writeback_inodes+0xec/0x100 > [] wb_kupdate+0x96/0x110 > [] __pdflush+0xbb/0x190 > [] pdflush+0x26/0x30 > [] wb_kupdate+0x0/0x110 > [] pdflush+0x0/0x30 > [] kthread+0xba/0xc0 > [] kthread+0x0/0xc0 > [] kernel_thread_helper+0x5/0x10 > Code: ff 8b 44 24 04 21 e2 8b 12 8b 92 b8 04 00 00 8b 52 44 8b 52 0c > 85 d2 75 12 ba 01 00 ff ff f0 0f c1 10 85 d2 0f 85 0c 11 00 00 c3 <0f> > 0b 20 00 c0 81 47 c0 eb e4 8d b4 26 00 00 00 00 8b 44 24 04 > > > Here is some miscellaneous output from the dmesg command that > may/maynot have a bearing on the issue. > > reiser4[java(7213)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 16384 > reiser4[java(7213)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 32768 > reiser4[java(7213)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 65536 > reiser4[java(7599)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 16384 > reiser4[java(7599)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 32768 > reiser4[java(7599)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 65536 > reiser4[ent:dm-0!(4791)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 16384 > reiser4[ent:dm-0!(4791)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 32768 > reiser4[ent:dm-0!(4791)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 65536 > reiser4[ktxnmgrd:dm-0:r(4790)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 16384 > reiser4[ent:dm-0!(4791)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 16384 > reiser4[ent:dm-0!(4791)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 32768 > reiser4[java(7858)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 16384 > reiser4[java(7858)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 32768 > reiser4[java(7858)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 65536 > reiser4[java(10888)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 16384 > reiser4[java(10888)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 32768 > reiser4[java(10888)]: commit_current_atom > (fs/reiser4/txnmgr.c:1147)[nikita-3176]: > WARNING: Flushing like mad: 65536 > > These are harmless. > Below are some miscellaneous stuff that may be usefull > > mount flags: rw,noatime,nodiratime,trace=0x0,log=0x0,debug=0x0,atom_max_size=0x5f1fb > 0 0 > > io scheduler/elevator: as > . > > > Linux cavasa 2.6.11-mm2 #4 SMP Fri Apr 8 20:26:21 EDT 2005 i686 > Intel(R) Xeon(TM) CPU 3.06GHz GenuineIntel GNU/Linux > > GCC 3.3.5 > > GNU C Library 20040808 release version 2.3.4, by Roland McGrath et al. > Compiled by GNU CC version 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, > pie-8.7.7.1). > Compiled on a Linux 2.6.8 system on 2005-02-26. > Available extensions: > GNU libio by Per Bothner > crypt add-on version 2.1 by Michael Glad and others > Native POSIX Threads Library by Ulrich Drepper et al > BIND-8.2.3-T5B > NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk > Thread-local storage support included. > > > Dane >