All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Adam Borowski <kilobyte@angband.pl>, linux-btrfs@vger.kernel.org
Subject: Re: Transaction aborted in btrfs_rename2
Date: Mon, 6 Jun 2016 10:13:01 -0400	[thread overview]
Message-ID: <bded73ce-3b5c-3ba0-0785-79d3ffaca34c@suse.com> (raw)
In-Reply-To: <20160606114732.GA30582@angband.pl>


[-- Attachment #1.1: Type: text/plain, Size: 2700 bytes --]

On 6/6/16 7:47 AM, Adam Borowski wrote:
> Hi!
> I just got this thrice, in 4.7-rc1 and 4.7-rc2:
> 
> [ 1836.672368] ------------[ cut here ]------------
> [ 1836.672382] WARNING: CPU: 1 PID: 16348 at fs/btrfs/inode.c:9820 btrfs_rename2+0xcd2/0x2a50
> [ 1836.672385] BTRFS: Transaction aborted (error -2)
> [ 1836.672387] Modules linked in: nvidia(PO) usb_storage
> [ 1836.672396] CPU: 1 PID: 16348 Comm: gcc-6 Tainted: P           O    4.7.0-rc2-debug+ #3
> [ 1836.672399] Hardware name: System manufacturer System Product Name/M4A77T, BIOS 2401    05/18/2011
> [ 1836.672402]  ffffffff81f8b504 ffff880062c47c78 ffffffff8165be6d 0000000000000007
> [ 1836.672407]  ffff880062c47cd0 0000000000000000 ffff880062c47cc0 ffffffff81110c1c
> [ 1836.672411]  ffff880062c47d20 0000265c814e8642 0000000000000000 0000000000a25ade
> [ 1836.672415] Call Trace:
> [ 1836.672423]  [<ffffffff8165be6d>] dump_stack+0x4e/0x71
> [ 1836.672429]  [<ffffffff81110c1c>] __warn+0x10c/0x150
> [ 1836.672433]  [<ffffffff81110caa>] warn_slowpath_fmt+0x4a/0x50
> [ 1836.672437]  [<ffffffff814f4842>] btrfs_rename2+0xcd2/0x2a50
> [ 1836.672443]  [<ffffffff814dfcfb>] ? btrfs_permission+0x5b/0xc0
> [ 1836.672448]  [<ffffffff81d288c8>] ? down_write+0x18/0x60
> [ 1836.672453]  [<ffffffff8133a0cc>] vfs_rename+0x7cc/0xc30
> [ 1836.672457]  [<ffffffff8133dc8b>] SyS_rename+0x32b/0x420
> [ 1836.672461]  [<ffffffff81d2ab9f>] entry_SYSCALL_64_fastpath+0x17/0x93
> [ 1836.672464] ---[ end trace 6405b6e3d0e6c945 ]---
> [ 1836.672468] BTRFS warning (device sda1): btrfs_rename:9820: Aborting unused transaction(No such entry).
> [ 1836.675505] BTRFS warning (device sda1): btrfs_rename:9820: Aborting unused transaction(No such entry).
> <repeated 1152 times>
> [ 1837.935238] BTRFS warning (device sda1): btrfs_rename:9820: Aborting unused transaction(No such entry).
> [ 1837.937602] BTRFS: error (device sda1) in btrfs_rename:9820: errno=-2 No such entry
> [ 1837.937607] BTRFS info (device sda1): forced readonly
> [ 1838.086754] BTRFS warning (device sda1): Skipping commit of aborted transaction.
> [ 1838.086762] BTRFS: error (device sda1) in cleanup_transaction:1857: errno=-2 No such entry
> [ 1838.086782] BTRFS info (device sda1): delayed_refs has NO entry
> 
> Didn't trigger during a week of other work, yet a kernel compile triggers
> this reliably.
> 
> Filesystem appears consistent (btrfs check, scrub).
> Mount options: noatime,compress=lzo,ssd,space_cache.
> 

Oh, interesting.  We're seeing this on our 4.4-based kernels as well but
only on arm64.  That it's triggering on x86_64 is a good data point.
I'm hunting this one today.

-Jeff

-- 
Jeff Mahoney
SUSE Labs


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 881 bytes --]

  reply	other threads:[~2016-06-06 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 11:47 Transaction aborted in btrfs_rename2 Adam Borowski
2016-06-06 14:13 ` Jeff Mahoney [this message]
2016-07-29 15:43   ` Jeff Mahoney
2016-07-29 16:13     ` Adam Borowski
2016-07-29 16:20       ` Jeff Mahoney

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=bded73ce-3b5c-3ba0-0785-79d3ffaca34c@suse.com \
    --to=jeffm@suse.com \
    --cc=kilobyte@angband.pl \
    --cc=linux-btrfs@vger.kernel.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 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.