At 09/01/2016 05:44 AM, Chris Murphy wrote:
On Wed, Aug 31, 2016 at 2:49 PM, Ronan Arraes Jardim Chagas
<roni...@gmail.com> wrote:
Hi guys!
And the problem happened again. This time, I was only using Mozilla
Firefox. I could get the very first message after the error. I hope it
brings more information:
[28039.672199] ------------[ cut here ]------------
[28039.672253] WARNING: CPU: 3 PID: 31800 at ../fs/btrfs/qgroup.c:2667
btrfs_qgroup_free_meta+0x88/0x90 [btrfs]
Does this file system have quota enabled?
I'm testing this right now and can't even figure out how to determine
when quota is enabled on a Btrfs file system. There's enable, disable,
and rescan. If it's enabled or disabled, I get the same message if I
rescan. If I mount the file system with quota previously enabled,
there is no mount time notification that quota is enabled.
I sincerely hope opensuse isn't enabled quota by default.
The　kernel warning is interesting.
It means qgroup is underflowing its reserved metadata space.
However although it's a warning, it won't really under flow the numbers,
but decrease it to zero.
It shows there is something wrong with metadata allocation, but won't
directly cause quota corruption.
Quota uses two isolated different system, one extent based for qgroup
numbers,
and one reserved space based for reserved space.
The latter one is only used to prevent user from exceeding qgroup limit,
and if user doesn't use limit, it won't cause any qgroup corruption or
ENOSPC.
Further more, if it's qgroup reserved space causing anything wrong, it
won't return -ENOSPC, but -EDQUOT.
So, just as Wang suspected, there is something wrong with metadata
allocation, causing the problem and triggering the qgroup warning.
Thankg,
Qu
--
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
