Kernel warning - not sure if this is important

[Peter Chant]

I got this kernel warning overnight.  Possibly during or after a dedup
using duperemove.  I'm not sure if that is relevent.  Seems to relate to
fs/btrfs/backref.c line 1266.

Don't know if it is important.  Thought I'd post it just in case.

I'm afraid this is a screen-shot in the old fashioned sense:
https://drive.google.com/file/d/1NelZV2ld9Yqqt8b2y2sg6aAwgevgMy4X/view?usp=sharing

Pete
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Kernel warning - not sure if this is important

[Nikolay Borisov]

On 19.03.2018 10:21, Peter Chant wrote:
> I got this kernel warning overnight.  Possibly during or after a dedup
> using duperemove.  I'm not sure if that is relevent.  Seems to relate to
> fs/btrfs/backref.c line 1266.
> 
> Don't know if it is important.  Thought I'd post it just in case.
> 
> I'm afraid this is a screen-shot in the old fashioned sense:
> https://drive.google.com/file/d/1NelZV2ld9Yqqt8b2y2sg6aAwgevgMy4X/view?usp=sharing

You are hitting a warning that was removed in : c8195a7b1ad5 ("btrfs:
remove spurious WARN_ON(ref->count < 0) in find_parent_nodes")


In short - you can disregard it. However, it's likely you will continue
seeing it in the future unless you update to 4.16 (the commit is not
tagged for stable ))



> 
> Pete
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Kernel warning - not sure if this is important

[Pete]

On 03/19/2018 08:34 AM, Nikolay Borisov wrote:

> You are hitting a warning that was removed in : c8195a7b1ad5 ("btrfs:
> remove spurious WARN_ON(ref->count < 0) in find_parent_nodes")
> 
> 
> In short - you can disregard it. However, it's likely you will continue
> seeing it in the future unless you update to 4.16 (the commit is not
> tagged for stable ))
> 

Thank you, much appreciated.  I think I can manage to wait for 4.16!

Pete
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html