From: Dave Chinner <david@fromorbit.com>
To: Daniel Wagner <wagi@monom.org>
Cc: linux-fsdevel@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: Internal error xfs_trans_cancel
Date: Wed, 1 Jun 2016 17:10:47 +1000 [thread overview]
Message-ID: <20160601071047.GJ12670@dastard> (raw)
In-Reply-To: <ab487269-a423-e3dc-6f59-3dda004960c3@monom.org>
On Wed, Jun 01, 2016 at 07:52:31AM +0200, Daniel Wagner wrote:
> Hi,
>
> I got the error message below while compiling a kernel
> on that system. I can't really say if I did something
> which made the file system unhappy before the crash.
>
>
> [Jun 1 07:41] XFS (sde1): Internal error xfs_trans_cancel at line 984 of file fs/xfs/xfs_trans.c. Caller xfs_rename+0x453/0x960 [xfs]
Anything in the log before this?
> [ +0.000095] CPU: 22 PID: 8640 Comm: gcc Not tainted 4.7.0-rc1 #16
> [ +0.000035] Hardware name: Dell Inc. PowerEdge R820/066N7P, BIOS 2.0.20 01/16/2014
> [ +0.000048] 0000000000000286 00000000c8be6bc3 ffff885fa9473cb0 ffffffff813d146e
> [ +0.000056] ffff885fa9ac5ed0 0000000000000001 ffff885fa9473cc8 ffffffffa0213cdc
> [ +0.000053] ffffffffa02257b3 ffff885fa9473cf0 ffffffffa022eb36 ffff883faa502d00
> [ +0.000053] Call Trace:
> [ +0.000028] [<ffffffff813d146e>] dump_stack+0x63/0x85
> [ +0.000069] [<ffffffffa0213cdc>] xfs_error_report+0x3c/0x40 [xfs]
> [ +0.000065] [<ffffffffa02257b3>] ? xfs_rename+0x453/0x960 [xfs]
> [ +0.000064] [<ffffffffa022eb36>] xfs_trans_cancel+0xb6/0xe0 [xfs]
> [ +0.000065] [<ffffffffa02257b3>] xfs_rename+0x453/0x960 [xfs]
> [ +0.000062] [<ffffffffa021fa63>] xfs_vn_rename+0xb3/0xf0 [xfs]
> [ +0.000040] [<ffffffff8124f92c>] vfs_rename+0x58c/0x8d0
> [ +0.000032] [<ffffffff81253fb1>] SyS_rename+0x371/0x390
> [ +0.000036] [<ffffffff817d2032>] entry_SYSCALL_64_fastpath+0x1a/0xa4
> [ +0.000040] XFS (sde1): xfs_do_force_shutdown(0x8) called from line 985 of file fs/xfs/xfs_trans.c. Return address = 0xffffffffa022eb4f
> [ +0.027680] XFS (sde1): Corruption of in-memory data detected. Shutting down filesystem
> [ +0.000057] XFS (sde1): Please umount the filesystem and rectify the problem(s)
> [Jun 1 07:42] XFS (sde1): xfs_log_force: error -5 returned.
> [ +30.081016] XFS (sde1): xfs_log_force: error -5 returned.
Doesn't normally happen, and there's not a lot to go on here. Can
you provide the info listed in the link below so we have some idea
of what configuration the error occurred on?
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
You didn't run out of space or something unusual like that? Does
'xfs_repair -n <dev>' report any errors?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Daniel Wagner <wagi@monom.org>
Cc: linux-fsdevel@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: Internal error xfs_trans_cancel
Date: Wed, 1 Jun 2016 17:10:47 +1000 [thread overview]
Message-ID: <20160601071047.GJ12670@dastard> (raw)
In-Reply-To: <ab487269-a423-e3dc-6f59-3dda004960c3@monom.org>
On Wed, Jun 01, 2016 at 07:52:31AM +0200, Daniel Wagner wrote:
> Hi,
>
> I got the error message below while compiling a kernel
> on that system. I can't really say if I did something
> which made the file system unhappy before the crash.
>
>
> [Jun 1 07:41] XFS (sde1): Internal error xfs_trans_cancel at line 984 of file fs/xfs/xfs_trans.c. Caller xfs_rename+0x453/0x960 [xfs]
Anything in the log before this?
> [ +0.000095] CPU: 22 PID: 8640 Comm: gcc Not tainted 4.7.0-rc1 #16
> [ +0.000035] Hardware name: Dell Inc. PowerEdge R820/066N7P, BIOS 2.0.20 01/16/2014
> [ +0.000048] 0000000000000286 00000000c8be6bc3 ffff885fa9473cb0 ffffffff813d146e
> [ +0.000056] ffff885fa9ac5ed0 0000000000000001 ffff885fa9473cc8 ffffffffa0213cdc
> [ +0.000053] ffffffffa02257b3 ffff885fa9473cf0 ffffffffa022eb36 ffff883faa502d00
> [ +0.000053] Call Trace:
> [ +0.000028] [<ffffffff813d146e>] dump_stack+0x63/0x85
> [ +0.000069] [<ffffffffa0213cdc>] xfs_error_report+0x3c/0x40 [xfs]
> [ +0.000065] [<ffffffffa02257b3>] ? xfs_rename+0x453/0x960 [xfs]
> [ +0.000064] [<ffffffffa022eb36>] xfs_trans_cancel+0xb6/0xe0 [xfs]
> [ +0.000065] [<ffffffffa02257b3>] xfs_rename+0x453/0x960 [xfs]
> [ +0.000062] [<ffffffffa021fa63>] xfs_vn_rename+0xb3/0xf0 [xfs]
> [ +0.000040] [<ffffffff8124f92c>] vfs_rename+0x58c/0x8d0
> [ +0.000032] [<ffffffff81253fb1>] SyS_rename+0x371/0x390
> [ +0.000036] [<ffffffff817d2032>] entry_SYSCALL_64_fastpath+0x1a/0xa4
> [ +0.000040] XFS (sde1): xfs_do_force_shutdown(0x8) called from line 985 of file fs/xfs/xfs_trans.c. Return address = 0xffffffffa022eb4f
> [ +0.027680] XFS (sde1): Corruption of in-memory data detected. Shutting down filesystem
> [ +0.000057] XFS (sde1): Please umount the filesystem and rectify the problem(s)
> [Jun 1 07:42] XFS (sde1): xfs_log_force: error -5 returned.
> [ +30.081016] XFS (sde1): xfs_log_force: error -5 returned.
Doesn't normally happen, and there's not a lot to go on here. Can
you provide the info listed in the link below so we have some idea
of what configuration the error occurred on?
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
You didn't run out of space or something unusual like that? Does
'xfs_repair -n <dev>' report any errors?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-06-01 7:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 5:52 Internal error xfs_trans_cancel Daniel Wagner
2016-06-01 5:52 ` Daniel Wagner
2016-06-01 7:10 ` Dave Chinner [this message]
2016-06-01 7:10 ` Dave Chinner
2016-06-01 13:50 ` Daniel Wagner
2016-06-01 13:50 ` Daniel Wagner
2016-06-01 14:13 ` Daniel Wagner
2016-06-01 14:13 ` Daniel Wagner
2016-06-01 14:19 ` Daniel Wagner
2016-06-01 14:19 ` Daniel Wagner
2016-06-02 0:26 ` Dave Chinner
2016-06-02 0:26 ` Dave Chinner
2016-06-02 5:23 ` Daniel Wagner
2016-06-02 5:23 ` Daniel Wagner
2016-06-02 6:35 ` Dave Chinner
2016-06-02 6:35 ` Dave Chinner
2016-06-02 13:29 ` Daniel Wagner
2016-06-02 13:29 ` Daniel Wagner
2016-06-26 12:16 ` Thorsten Leemhuis
2016-06-26 12:16 ` Thorsten Leemhuis
2016-06-26 15:13 ` Daniel Wagner
2016-06-26 15:13 ` Daniel Wagner
2016-06-14 4:29 ` Josh Poimboeuf
2016-06-14 4:29 ` Josh Poimboeuf
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=20160601071047.GJ12670@dastard \
--to=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wagi@monom.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.