linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: apt taints kernel - btrfs destroys inode
Date: Mon, 2 May 2016 00:38:08 +0000 (UTC)	[thread overview]
Message-ID: <pan$a8e59$e73b6bd3$47d0e1e7$4518553f@cox.net> (raw)
In-Reply-To: efdhvc-3p8.ln1@aldebaran.xundeenergie.at

Jakob Schürz posted on Sun, 01 May 2016 15:38:22 +0200 as excerpted:

> What does this mean???
> 
> Mai 01 15:36:42 aldebaran kernel: ------------[ cut here ]------------
> Mai 01 15:36:42 aldebaran kernel: WARNING: CPU: 3 PID: 8937 at
> /build/linux-aGlcVo/linux-4.6~rc3/fs/btrfs/inode.c:9261
> btrfs_destroy_inode+0x234/0x2a0 [btrfs]


That's a known apparent false-positive warning on current 4.6-rc kernel 
btrfs.  The destroy-inode bit is related to a file deletion happening in 
the normal order of things, where this warning code is run, and 
apparently triggers even under normal operations.

It's related to some btrfs feature (I think either snapshotting or 
quotas, but don't recall which) I don't use here so I don't seem the 
warnings, but there's several threads where people have reported the 
warnings, so it's apparently quite commonly triggered, but nobody has 
reported any further problems even where the warnings are coming in the 
hundreds due to their use-case, so as I said, apparently a false-positive 
induced by normal operations.

I'd expect the warning to be either fixed to only warn when there's an 
actual issue, or be silenced, by 4.6 release.

If you want further details, as I said, there's at least two other 
threads with people reporting and discussing it, so read the last week or 
two of the list archive (or even just the non-patch original thread 
starter posts) and you'll find them.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2016-05-02  0:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-01 13:38 apt taints kernel - btrfs destroys inode Jakob Schürz
2016-05-02  0:38 ` Duncan [this message]
2016-05-07 23:11   ` Adam Borowski
2016-05-08  6:31     ` Duncan

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='pan$a8e59$e73b6bd3$47d0e1e7$4518553f@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).