From: Maciej Marcin Piechotka <uzytkownik2@gmail.com>
To: miaox@cn.fujitsu.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/inode.c:2299
Date: Mon, 19 Sep 2011 02:44:41 +0200 [thread overview]
Message-ID: <1316393087.5713.1.camel@picard> (raw)
In-Reply-To: <4E5C82E8.9090400@cn.fujitsu.com>
On Tue, 2011-08-30 at 14:27 +0800, Miao Xie wrote:
> >
> > Unfortunately it results in freeze of system and I cannot give more
> > details. Sometimes it happens not from fcron but then it does not result
> > in freeze (???).
>
> Could you give me the method to reproduce it?
>
> Thanks
> Miao
Sorry for spamming in this thread but I'm trying to post my findings in
hope that somebody will understand what's going on.
Recent crash gave some valuable information IMHO:
1. I started the autocompletion of path in zsh
2. At some point the zsh hanged. In ps the process was listed as
runnable
3. Any access to root volume (the one that zsh was trying to readdir)
finished in hang.
4. I was able to access the child volume (/home)
5. After some time the bug is hit. At this time strange things happens
(screen freeze etc.). I guess that there is some strange interaction
between KMS, X and now-hanged composite manager
Next time it happend (also during listing root directory of volume 0) I
observed the following thing - I can log out and unmount home but the
volume 0 remains busy and cannot be unmounted.
Things to consider:
- It is not enabled/disabled by any mount option
- Is it triggered when the parent volume (say volume 0) and child
volume are both mounted?
- Which case is it failing (I've tried to add printk but I cannot find
the option in printk to print u64)
- Why it happens only during night?
Regards
next prev parent reply other threads:[~2011-09-19 0:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 1:45 kernel BUG at fs/btrfs/inode.c:2299 Maciej Marcin Piechotka
2011-08-30 6:27 ` Miao Xie
2011-08-30 8:47 ` Maciej Marcin Piechotka
2011-09-02 11:18 ` Maciej Marcin Piechotka
2011-09-05 13:47 ` Maciej Marcin Piechotka
2011-09-09 1:13 ` Maciej Marcin Piechotka
2011-09-09 3:02 ` Roman Mamedov
2011-09-09 3:29 ` Maciej Marcin Piechotka
2011-09-19 0:44 ` Maciej Marcin Piechotka [this message]
2011-09-21 2:14 ` Maciej Marcin Piechotka
2011-09-17 18:25 ` Maciej Marcin Piechotka
2011-09-17 18:30 ` Maciej Marcin Piechotka
2011-09-18 0:08 ` Maciej Marcin Piechotka
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=1316393087.5713.1.camel@picard \
--to=uzytkownik2@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.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 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).