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: Kernel Bug while deleting files (with rsync)
Date: Thu, 27 Mar 2008 12:03:41 +0900	[thread overview]
Message-ID: <1206587021.3100.47.camel@localhost.localdomain> (raw)
In-Reply-To: <20080326164723.GA31518-W0ZHf6uU1cg@public.gmane.org>

Hi Alex,

On Wed, 2008-03-26 at 17:47 +0100, Alexander Schier wrote:
> Hi!
> 
> segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
> NILFS warning (device dm-3): nilfs_sync_super: barrier-based sync failed. disabling barriers
> 
> PAGE_BUG(c1328080): cnt=2 index#=0 flags=0x40000805 mapping=00000000 ino=0
>  BH[0] d66a1cd0: cnt=1 block#=0 state=0x20000
> <snip>
> with rsync again.
> 
> Alex

Thanks!
According to your log, the problem is a reference count leak of a
b-tree node buffer.

Could you tell me the concrete way to reproduce the bug with rsync ? 

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

  parent reply	other threads:[~2008-03-27  3:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25 10:25 Kernel Bug while deleting files (with rsync) Alexander Schier
     [not found] ` <20080325102553.GA10853-W0ZHf6uU1cg@public.gmane.org>
2008-03-25 11:45   ` Ryusuke Konishi
     [not found]     ` <1206445521.3131.60.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-03-26 13:05       ` Ryusuke Konishi
     [not found]         ` <20080326.220532.62697306.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-03-26 16:47           ` Alexander Schier
     [not found]             ` <20080326164723.GA31518-W0ZHf6uU1cg@public.gmane.org>
2008-03-27  3:03               ` Ryusuke Konishi [this message]
     [not found]                 ` <1206587021.3100.47.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-03-27 13:23                   ` Alexander Schier
     [not found]                     ` <20080327132327.GA3562-W0ZHf6uU1cg@public.gmane.org>
2008-03-28 18:12                       ` Alexander Schier
     [not found]                         ` <20080328181211.GA19581-W0ZHf6uU1cg@public.gmane.org>
2008-03-28 19:40                           ` Resolved? Was: " Alexander Schier
     [not found]                             ` <20080328194039.GA28685-W0ZHf6uU1cg@public.gmane.org>
2008-03-30  5:04                               ` Ryusuke Konishi
     [not found]                                 ` <20080330.140417.27795318.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-03-30  9:29                                   ` Alexander Schier

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=1206587021.3100.47.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