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: Sat, 13 Jul 2013 11:06:50 -0400 [thread overview]
Message-ID: <20130713150650.GA31035@redhat.com> (raw)
In-Reply-To: <20130713020030.GG3438@dastard>
On Sat, Jul 13, 2013 at 12:00:30PM +1000, Dave Chinner wrote:
> On Thu, Jul 11, 2013 at 10:39:30PM -0400, Dave Jones wrote:
> > Just saw this during boot after an unclean shutdown. It hung afterwards.
> >
> > [ 97.162665] XFS: Assertion failed: xfs_dir2_sf_lookup(args) == ENOENT, file: fs/xfs/xfs_dir2_sf.c, line: 358
> ....
> > [ 97.173730] [<ffffffffa0076953>] xfs_dir2_sf_addname+0x43/0x760 [xfs]
> > [ 97.173743] [<ffffffffa0067cfc>] xfs_dir_createname+0x15c/0x1b0 [xfs]
> > [ 97.173754] [<ffffffffa002f2dc>] xfs_create+0x4cc/0x710 [xfs]
> > [ 97.173764] [<ffffffffa00278ca>] xfs_vn_mknod+0x9a/0x1c0 [xfs]
> > [ 97.173773] [<ffffffffa0027a03>] xfs_vn_create+0x13/0x20 [xfs]
> > [ 97.173776] [<ffffffff811d100d>] vfs_create+0x9d/0x100
> > [ 97.173778] [<ffffffff811d1995>] do_last+0x925/0xe00
> > [ 97.173780] [<ffffffff811d1f2e>] path_openat+0xbe/0x6f0
> > [ 97.173783] [<ffffffff8109e33f>] ? local_clock+0x3f/0x50
> > [ 97.173785] [<ffffffff811e1b5f>] ? __alloc_fd+0xaf/0x200
> > [ 97.173787] [<ffffffff811d2c3a>] do_filp_open+0x3a/0x90
> > [ 97.173789] [<ffffffff811e1b5f>] ? __alloc_fd+0xaf/0x200
> > [ 97.173790] [<ffffffff811c0ddb>] do_sys_open+0x10b/0x200
> > [ 97.173792] [<ffffffff81010578>] ? syscall_trace_enter+0x18/0x290
> > [ 97.173794] [<ffffffff811c0eee>] SyS_open+0x1e/0x20
> >
> > This trace repeated a few times, then the same assertion was triggered from sys_renameat.
>
> That's rather curious. What this means is that there is either an
> EIO or EEXIST error being returned from xfs_dir2_sf_lookup() when a
> we're about to add the new entry. There are two things here - EIO
> can only be returned if a shutdown has occurred - are there any
> signs of a shutdown in the logs?
not that I recall (machine is off, and remote right now).
1st time it was during boot (above), and 2nd time I hit it
the machine kept fuzzing for a while afterwards.
I'll see if I can reproduce it again on monday, and if so I'll
grab an xfsdump for you to stare at.
Dave
next prev parent reply other threads:[~2013-07-13 15:07 UTC|newest]
Thread overview: 10+ 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-13 2:00 ` Dave Chinner
2013-07-13 15:06 ` Dave Jones [this message]
2013-07-15 19:58 ` Dave Jones
2013-07-16 0:27 ` Dave Chinner
2013-07-16 1:42 ` Dave Jones
2013-07-16 2:01 ` Dave Chinner
2013-07-25 4:15 ` Dave Chinner
2013-07-30 20:26 ` XFS undeletable files. (3.11rc3) Dave Jones
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=20130713150650.GA31035@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox