LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Zan Lynx <zlynx@acm.org>
Cc: reiserfs-list@namesys.com,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
Date: Sat, 20 Jan 2007 03:34:07 +0300	[thread overview]
Message-ID: <200701200334.07690.vs@namesys.com> (raw)
In-Reply-To: <1169229490.6266.11.camel@oberon>

Hello

On Friday 19 January 2007 20:58, 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.  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.
> 
> 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.
> 
yes, please provide more information. Full kernel output at time of freeze is very desirable.

  parent reply	other threads:[~2007-01-19 23:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 17:58 Zan Lynx
2007-01-19 18:53 ` Edward Shishkin
2007-01-20  0:34 ` Vladimir V. Saveliev [this message]
     [not found]   ` <1170267238.22971.1.camel@oberon>
2007-02-01 15:54     ` Edward Shishkin
2007-02-02  0:21       ` Zan Lynx
2007-01-23  7:38 ` Vince
2007-01-23 19:15   ` Vladimir V. Saveliev
2007-01-25  7:33     ` Vince

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=200701200334.07690.vs@namesys.com \
    --to=vs@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-list@namesys.com \
    --cc=zlynx@acm.org \
    --subject='Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).