reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Serkan Kaba <serkan@gentoo.org>
Cc: ReiserFS Development List <reiserfs-devel@vger.kernel.org>
Subject: Re: Reiser4 and mount times
Date: Sat, 15 Jan 2011 15:39:55 +0100	[thread overview]
Message-ID: <4D31B1BB.7000906@gmail.com> (raw)
In-Reply-To: <4D31376F.1080903@gentoo.org>

On 01/15/2011 06:58 AM, Serkan Kaba wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> After switching to dont_load_bitmap I started having freezes when
> starting pidgin (not always).


Are there any visible disk activity while freezing?


  Here's what I could find from dmesg.

Ok, I'll try to reproduce this..

Edward.

>
> Process java (pid: 6853, threadinfo ffff88014862c000, task ffff88017fc8c090)
> Stack:
>   ffff880100000020 ffffffff00000001 000000017ef577f0 0000000000008000
> <0>  0000000000000020 ffff880147249004 ffff88017ef577f0 ffff88014862dae8
> <0>  0000000000007fe0 ffff88014862da84 0000000000000001 ffff88014862dae0
> Call Trace:
>   [<ffffffff81120153>] T.635+0x7b/0xc2
>   [<ffffffff81120305>] reiser4_alloc_blocks_bitmap+0x16b/0x1ca
>   [<ffffffff810ee15f>] ? item_utmost_child_real_block+0x46/0x4d
>   [<ffffffff810ee47e>] ? coord_prev_unit+0x64/0xa9
>   [<ffffffff810ef334>] reiser4_alloc_blocks+0x8f/0x22b
>   [<ffffffff810f4305>] allocate_znode_update+0xfc/0x249
>   [<ffffffff810e59d1>] ? jload_gfp+0x3e/0x1b9
>   [<ffffffff810f4577>] allocate_znode+0x125/0x169
>   [<ffffffff810f584a>] alloc_pos_and_ancestors+0xfb/0x137
>   [<ffffffff810f6326>] flush_current_atom+0x66c/0x7ea
>   [<ffffffff810f0186>] ? txnh_get_atom+0x2a/0xa3
>   [<ffffffff810f1e62>] reiser4_txn_end+0x283/0x57b
>   [<ffffffff810f216b>] reiser4_txn_restart+0x11/0x22
>   [<ffffffff810f270d>] reiser4_txn_restart_current+0x19/0x1b
>   [<ffffffff810f2976>] force_commit_atom+0x63/0x69
>   [<ffffffff811044e7>] reiser4_sync_file_common+0x73/0x82
>   [<ffffffff810b5599>] vfs_fsync_range+0x50/0x7b
>   [<ffffffff810b561f>] vfs_fsync+0x17/0x19
>   [<ffffffff810b564a>] do_fsync+0x29/0x3e
>   [<ffffffff810b567c>] sys_fsync+0xb/0xf
>   [<ffffffff81001eab>] system_call_fastpath+0x16/0x1b
> Code: 00 00 00 48 8b 80 70 02 00 00 48 8b 40 18 48 03 18 48 89 df e8 07
> f5 ff ff 89 45 c4 85 c0 0f 85 5c 01 00 00 48 8b 43 20 41 8b 17<48>  8b
> 40 40 31 c9 48 83 c0 04 48 89 45 c8 8b 43 30 39 d0 72 04
> RIP  [<ffffffff8111ff71>] T.637+0x5d/0x1c4
>   RSP<ffff88014862d9f8>
> CR2: 0000000000000040
> - ---[ end trace d23b92e9c7b9d378 ]---

  reply	other threads:[~2011-01-15 14:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11  4:44 Reiser4 and mount times Serkan Kaba
2011-01-11 10:30 ` Edward Shishkin
2011-01-12  4:06   ` Serkan Kaba
2011-01-12 20:44     ` Edward Shishkin
2011-01-15  5:58       ` Serkan Kaba
2011-01-15 14:39         ` Edward Shishkin [this message]
2011-01-15 17:46           ` Serkan Kaba
2011-01-17  4:35           ` Serkan Kaba
2011-01-17 14:09             ` Edward Shishkin
2011-03-04 16:02             ` Serkan Kaba
2011-03-04 16:18               ` Edward Shishkin
2011-03-04 16:28                 ` Serkan Kaba

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=4D31B1BB.7000906@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=serkan@gentoo.org \
    /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).