From: Chris Mason <chris.mason@oracle.com>
To: Sage Weil <sage@newdream.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: WARNING: at fs/btrfs/inode.c:2222
Date: Fri, 27 Jan 2012 12:40:42 -0500 [thread overview]
Message-ID: <20120127174042.GF991@shiny> (raw)
In-Reply-To: <Pine.LNX.4.64.1201270912570.5607@cobra.newdream.net>
On Fri, Jan 27, 2012 at 09:31:46AM -0800, Sage Weil wrote:
> Has anyone see this one before? We've been hitting it sporatically for a
> while now, although recently we've been able to trigger pretty easily.
> The result is EINVAL from the snap create ioctl.
>
> The kernel is v3.2 + some ceph stuff.
>
> The code in question is
>
> /* if we have links, this was a truncate, lets do that */
> if (inode->i_nlink) {
> if (!S_ISREG(inode->i_mode)) {
> WARN_ON(1);
> iput(inode);
> continue;
> }
>
> Is this something obvious, or should we spend some time chasing it down?
This doesn't seem right, we've got an orphan on a directory for a
truncate? The link count is probably 1, but no I haven't seen this.
-chris
next prev parent reply other threads:[~2012-01-27 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 17:31 WARNING: at fs/btrfs/inode.c:2222 Sage Weil
2012-01-27 17:40 ` Chris Mason [this message]
2012-01-27 17:52 ` Sage Weil
2012-02-09 2:18 ` Sage Weil
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=20120127174042.GF991@shiny \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sage@newdream.net \
/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.