Linux NILFS development
 help / color / mirror / Atom feed
From: Alexander Schier <alex-W0ZHf6uU1cg@public.gmane.org>
To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Subject: Re: Resolved? Was: Kernel Bug while deleting files (with rsync)
Date: Sun, 30 Mar 2008 11:29:55 +0200	[thread overview]
Message-ID: <20080330092955.GA11598@laxu.de> (raw)
In-Reply-To: <20080330.140417.27795318.ryusuke-sG5X7nlA6pw@public.gmane.org>

Hi!
On Sun, Mar 30, 2008 at 02:04:17PM +0900, Ryusuke Konishi wrote:
> Hi Alex,
> 
> > OK, it seems to work for me, after ...
> > -using a debian 2.6.24 kernel instead of a selfcompiled 2.6.22
> > -maybe the 2.6.22 had a different compiler than the nilfs2 module
No BUG since this.
> > at the moment rsync works perfectly.
> > 
> > I'll mail again, if it has the BUG again. Until then, it seems resolved.
> > ;)
> I see. I'll wait for your next report breathlessly. :)
Sorry, seems it was my mistake.

> So far, we haven't been able to reproduce the problem by tests
> in a similar fashion.
You must know, if this can be caused by wrong compiler only, or if the
bug may exist hidden in the Source, and was only triggered by this.
Another option may be, that my self-compiled kernel missed some option,
which nilfs uses, but does not depend on in Makefile?

You're the Coders, i can only guess and be happy it works fine with current
configuration.

> This might be caused by a defect of exclusion control.
> If so, it's hard to track it by phenomena.
> So, I'll think reviewing the source code of related parts
> during making kernel patches of NILFS.
keep improving ;)

Alex

      parent reply	other threads:[~2008-03-30  9:29 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
     [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 [this message]

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=20080330092955.GA11598@laxu.de \
    --to=alex-w0zhf6uu1cg@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