Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Subject: Re: Deadlocks! help, please!
Date: Tue, 22 Jan 2008 12:02:00 +0900	[thread overview]
Message-ID: <1200970920.2844.59.camel@localhost.localdomain> (raw)
In-Reply-To: <20080122000052.215084db@vosztok>

Hi,

On Tue, 2008-01-22 at 00:00 +0100, Gergely Gábor wrote:
> > Here I attach a test patch to fix the problem.
> > Could you try the patch ?
> > 
> > So, if rtorrent (or something else) hang again, then
> > send me a copy of /proc/slabinfo, please.
> It hang again,

Ugh! OK, I'll continue to work on it.

> but i have to note, that i had to respin kernel, 
> as I used SLUB before (some make oldconfig possibly 
> defaulted to that or suggested that), and had no /proc/slabinfo.
> With SLUB even with the patch in place, the machine froze,
>  and with SLAB i did a fine ~6 hour uptime, and was just telling
>  a friend that nilfs is just right now, when it stuck :)
> the hang occured when epiphany ( based on gecko. memleaker :( ) 
> eat up a lot of ram, and I was just about to close it. 
> some massive swapping happened, and the fs hang.
> I attach many stuff, might they help: a log with call trace, 
> a copy of slabinfo and the kernel config, might that be of any use.

Thanks a lot for providing various information.
Actually I have a machine with a SLUB configured kernel,
but it's not so problematic. I wonder why NILFS hangs so offten 
in your environment :)
Joking aside, one of key differences that my colleague 
pointed out, is that your kernel is non-smp one.
We'll try your config to get better environment to debug.

Best regards,
-- 
Ryusuke Konishi
NILFS team NTT
http://www.nilfs.org/

  reply	other threads:[~2008-01-22  3:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 21:25 Deadlocks! help, please! Gergely Gábor
2008-01-17  7:58 ` Ryusuke Konishi
     [not found]   ` <1200556717.3085.94.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-01-17  9:14     ` Ryusuke Konishi
     [not found]       ` <1200561294.3085.131.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-01-17 17:33         ` Gergely Gábor
2008-01-18  3:58           ` Ryusuke Konishi
     [not found]             ` <1200628693.2931.54.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-01-18 10:11               ` Ryusuke Konishi
     [not found]                 ` <1200651072.2931.112.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-01-21  5:01                   ` Ryusuke Konishi
     [not found]                     ` <20080121.140129.01311807.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-01-21 23:00                       ` Gergely Gábor
2008-01-22  3:02                         ` Ryusuke Konishi [this message]
     [not found]                           ` <1200970920.2844.59.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-02-05  9:28                             ` Ryusuke Konishi
     [not found]                               ` <20080205.182829.44149266.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-02-05 12:18                                 ` Gergely Gábor
2008-02-07 10:09                                 ` Gergely Gábor
2008-02-12 12:57                                   ` Ryusuke Konishi
     [not found]                                     ` <1202821077.9432.99.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-02-19 12:54                                       ` NILFS2 git repositories Ryusuke Konishi
2008-01-17 19:10         ` Deadlocks! help, please! Gergely Gábor
2008-01-25 11:46           ` Other strange things Gergely Gábor
2008-01-29  7:53             ` Ryusuke Konishi

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=1200970920.2844.59.camel@localhost.localdomain \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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