From: Omar Sandoval <osandov@osandov.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>, agruenba@redhat.com
Subject: Re: read-only fs, kernel 4.9.0, fs/btrfs/delayed-inode.c:1170 __btrfs_run_delayed_items,
Date: Tue, 24 Jan 2017 09:49:07 -0800 [thread overview]
Message-ID: <20170124174907.GA27340@vader> (raw)
In-Reply-To: <CAJCQCtSHx8cEanC7e71akLiRKzi+Rt96CSAoK11Ngud9=n1U-Q@mail.gmail.com>
On Mon, Jan 23, 2017 at 08:51:24PM -0700, Chris Murphy wrote:
> On Mon, Jan 23, 2017 at 5:05 PM, Omar Sandoval <osandov@osandov.com> wrote:
> > Thanks! Hmm, okay, so it's coming from btrfs_update_delayed_inode()...
> > That's probably us failing btrfs_lookup_inode(), but just to make sure,
> > could you apply the updated diff at the same link as before
> > (https://gist.github.com/osandov/9f223bda27f3e1cd1ab9c1bd634c51a4)? If
> > that's the case, I'm even more confused about what xattrs have to do
> > with it.
>
> [ 35.015363] __btrfs_update_delayed_inode(): inode is missing
Okay, like I expected...
> [ 35.015372] btrfs_update_delayed_inode(ino=2) -> -2
Wtf? Inode numbers should be >=256. I updated the diff a third time to
catch where that came from. If we're lucky, the backtrace should have
the exact culprit. If we're unlucky, there might be memory corruption
involved.
> osandov-9f223b_2-dmesg.log
> https://drive.google.com/open?id=0B_2Asp8DGjJ9UnNSRXpualprWHM
>
>
> --
> Chris Murphy
next prev parent reply other threads:[~2017-01-24 17:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 18:50 read-only fs, kernel 4.9.0, fs/btrfs/delayed-inode.c:1170 __btrfs_run_delayed_items, Chris Murphy
2017-01-11 1:07 ` Chris Murphy
2017-01-11 23:13 ` Chris Murphy
2017-01-18 21:27 ` Chris Murphy
2017-01-19 18:05 ` Imran Geriskovan
2017-01-23 21:31 ` Omar Sandoval
2017-01-23 21:50 ` Chris Murphy
2017-01-23 21:55 ` Chris Murphy
2017-01-23 22:04 ` Omar Sandoval
2017-01-23 23:48 ` Chris Murphy
2017-01-24 0:05 ` Omar Sandoval
2017-01-24 3:51 ` Chris Murphy
2017-01-24 17:49 ` Omar Sandoval [this message]
2017-01-24 18:37 ` Chris Murphy
2017-01-24 18:56 ` Omar Sandoval
2017-01-24 19:06 ` Chris Murphy
2017-01-24 19:19 ` Chris Murphy
2017-01-24 20:10 ` Omar Sandoval
2017-01-24 20:24 ` Chris Murphy
2017-01-24 20:27 ` Omar Sandoval
2017-01-24 20:33 ` Chris Murphy
2017-01-24 20:48 ` Chris Murphy
2017-01-24 22:50 ` Omar Sandoval
2017-01-25 2:53 ` Chris Murphy
2017-01-25 4:42 ` Omar Sandoval
2017-01-25 22:55 ` Chris Murphy
2017-01-25 22:58 ` Omar Sandoval
2017-01-25 23:07 ` Chris Murphy
2017-01-24 20:13 ` Chris Murphy
2017-01-24 20:17 ` Omar Sandoval
2017-01-24 18:59 ` Chris Murphy
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=20170124174907.GA27340@vader \
--to=osandov@osandov.com \
--cc=agruenba@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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.