From mboxrd@z Thu Jan 1 00:00:00 1970 From: Edward Shishkin Subject: Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption Date: Fri, 19 Jan 2007 21:53:33 +0300 Message-ID: <45B113AD.5040706@namesys.com> References: <1169229490.6266.11.camel@oberon> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1169229490.6266.11.camel@oberon> Sender: linux-kernel-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Zan Lynx Cc: Linux kernel mailing list , ReiserFS List Zan Lynx wrote: >I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1 >and rc4-mm1 have been giving me these freezes. > I didn't investigate it in details yet, other file systems also freeze for me: http://marc.theaimsgroup.com/?l=linux-kernel&m=116809282829254&w=2 > They were happening >inside X and without external console it was impossible to get anything, >plus I was reluctant to test it since the freeze sometimes requires a >full fsck.reiser4 --build-fs to recover the filesystem. > > Why did you decide to recover? Got oops after mount, or? >But I finally got some output in a console session. I wasn't able to >get it all, I made some notes of what I think the problem is. I may try >again later once I get netconsole working (netconsole fails as a >built-in, I'll try it as a module next). > >1 lock held by pdflush/185: >#0: (&type->s_umount_key#15) ... writeback_inodes+0x89 > >3 locks held by realsync/12942: >#0: (&type->s_umount_key#15) at ... __sync_inodes+0x78 >#1: (&mgr->commit_mutex) ... reiser4_txn_end+0x37a >#2: (&qp->mutex) ... synchronize_qrcu+0x19 > >So, I *think* the problem is two locks on s_umount_key#15. Does that >sound likely? I also noticed QRCU may be involved. > >Perhaps someone will look at this and instantly know what the problem >is. > >If not, I'll be following up with more details like .config and perhaps >a full sysrq-T dump as soon as that fsck finishes. > >