From: Dave Jones <davej@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, xfs@oss.sgi.com
Subject: Re: XFS: Assertion failed: xfs_dir2_sf_lookup(args) == ENOENT, file: fs/xfs/xfs_dir2_sf.c, line: 358
Date: Mon, 15 Jul 2013 15:58:00 -0400 [thread overview]
Message-ID: <20130715195800.GD1706@redhat.com> (raw)
In-Reply-To: <20130713020030.GG3438@dastard>
On Sat, Jul 13, 2013 at 12:00:30PM +1000, Dave Chinner wrote:
> > [ 97.162665] XFS: Assertion failed: xfs_dir2_sf_lookup(args) == ENOENT, file: fs/xfs/xfs_dir2_sf.c, line: 358
> ....
>
> So, it's not clear what has caused this yet. Is it reproducable?
Just hit it again on the same machine.
> would be good to get a trace of lookup vs addname events from XFS,
> too (i.e. all the xfs_dir* and xfs_da* events) so we can see if the
> correct lookups were done prior to the failing addname operation...
<- xfs tracing noob. Got a recipe I can cut-n-paste ?
Or a patch if that's necessary..
Dave
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, xfs@oss.sgi.com
Subject: Re: XFS: Assertion failed: xfs_dir2_sf_lookup(args) == ENOENT, file: fs/xfs/xfs_dir2_sf.c, line: 358
Date: Mon, 15 Jul 2013 15:58:00 -0400 [thread overview]
Message-ID: <20130715195800.GD1706@redhat.com> (raw)
In-Reply-To: <20130713020030.GG3438@dastard>
On Sat, Jul 13, 2013 at 12:00:30PM +1000, Dave Chinner wrote:
> > [ 97.162665] XFS: Assertion failed: xfs_dir2_sf_lookup(args) == ENOENT, file: fs/xfs/xfs_dir2_sf.c, line: 358
> ....
>
> So, it's not clear what has caused this yet. Is it reproducable?
Just hit it again on the same machine.
> would be good to get a trace of lookup vs addname events from XFS,
> too (i.e. all the xfs_dir* and xfs_da* events) so we can see if the
> correct lookups were done prior to the failing addname operation...
<- xfs tracing noob. Got a recipe I can cut-n-paste ?
Or a patch if that's necessary..
Dave
next prev parent reply other threads:[~2013-07-15 19:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 2:39 XFS: Assertion failed: xfs_dir2_sf_lookup(args) == ENOENT, file: fs/xfs/xfs_dir2_sf.c, line: 358 Dave Jones
2013-07-12 2:39 ` Dave Jones
2013-07-13 2:00 ` Dave Chinner
2013-07-13 2:00 ` Dave Chinner
2013-07-13 15:06 ` Dave Jones
2013-07-13 15:06 ` Dave Jones
2013-07-15 19:58 ` Dave Jones [this message]
2013-07-15 19:58 ` Dave Jones
2013-07-16 0:27 ` Dave Chinner
2013-07-16 0:27 ` Dave Chinner
2013-07-16 1:42 ` Dave Jones
2013-07-16 1:42 ` Dave Jones
2013-07-16 2:01 ` Dave Chinner
2013-07-16 2:01 ` Dave Chinner
2013-07-25 4:15 ` Dave Chinner
2013-07-25 4:15 ` Dave Chinner
2013-07-30 20:26 ` XFS undeletable files. (3.11rc3) Dave Jones
2013-07-30 20:26 ` Dave Jones
2013-07-31 6:11 ` Markus Trippelsdorf
2013-07-31 6:11 ` Markus Trippelsdorf
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=20130715195800.GD1706@redhat.com \
--to=davej@redhat.com \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.