From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: dave-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org
Cc: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: NIlfs panic
Date: Tue, 09 Jun 2009 02:13:16 +0900 (JST) [thread overview]
Message-ID: <20090609.021316.123404780.ryusuke@osrg.net> (raw)
In-Reply-To: <4A2CAE34.1050003-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org>
Hi Dave,
On Mon, 08 Jun 2009 10:22:44 +0400, Dave <dave-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org> wrote:
> On 06/06/09 08:32, Dave wrote:
> > Hi
> >
> > Ryusuke Konishi wrote:
> >> Hi,
> >> On Fri, 05 Jun 2009 22:44:31 +0400, Dave wrote:
> >>> Hi,
> >>>
> >>> Was running a make, find and i paniced. I know this i'm running tanited
> >>> due to nvidia closed binary, but it may be something worth looking at.
> >> I've identified the function and instruction arising the fault.
> >>
> >> Two questions:
> >>
> >> - The kernel seems 2.6.28 not 2.6.30.
> >> Which version of nilfs2-modules did you applied?
> >> 2.0.14 ? or HEAD on nilfs2-modules.git ?
> >
> > It's 2.0.14 and yes on 2.6.28 (haven't moved to 2.6.29 because of
> > forcedeth network bug).
> >
> >> - Is is reproducible?
> >
> > I'll try again today.
> >
>
> I've been unable to reproduce this so far and i've not lost any data in
> the original panic so i'll just have to wait see if it happens again in
> the future. At least we have the panic recorded in the mailing list for
> future.
Thank you. The repeatability itself is an important hint. Some kind
of (rare) timing problem likely remains around delete or truncate path
of regular files. If we can narrow down suspicious code path or
conditions, I will try to review the path. Please send us report if
you meet a successive problem.
Thanks,
Ryusuke Konishi
next prev parent reply other threads:[~2009-06-08 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 4:32 NIlfs panic Dave
[not found] ` <4A29F15F.7020804-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org>
2009-06-08 6:22 ` Dave
[not found] ` <4A2CAE34.1050003-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org>
2009-06-08 17:13 ` Ryusuke Konishi [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-05 18:44 Dave
[not found] ` <4A29678F.10306-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org>
2009-06-05 19:58 ` Ryusuke Konishi
2009-06-06 3:26 ` Ryusuke Konishi
[not found] ` <20090606.122631.12792376.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-06-06 4:29 ` Dave
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=20090609.021316.123404780.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=dave-/hCUnnzDXf0AvxtiuMwx3w@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