From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: "Karsai, Gabor" <gabor.karsai@Vanderbilt.Edu>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs quota exceeded notifications through netlink sockets
Date: Sun, 7 Jan 2018 14:21:36 +0800 [thread overview]
Message-ID: <f67fafee-fac3-21fa-d89f-a830da646ea5@gmx.com> (raw)
In-Reply-To: <660251B721353E428446B0F99FE510A2A508D507@ITS-HCWNEM102.ds.vanderbilt.edu>
[-- Attachment #1.1: Type: text/plain, Size: 1178 bytes --]
On 2018年01月06日 09:34, Karsai, Gabor wrote:
> I created a subvolume on a btrfs, set a limit and the quota is enforced - dumping too much data into the subvolume results in a 'quota exceeded' message (from dd, for example). But when I am trying to get netlink socket notifications, nothing arrives on the socket (I am using pyroute2 which is supposedly able to receive disk quota notifications)
>
> $ uname -a
> Linux riaps-dev 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
>
> btrfs: whatever Ubuntu 16.04 has
>
> Kconfig:
> CONFIG_QUOTA_NETLINK_INTERFACE=y
This quota netlink support is for generic quota (implemented by
fs/quota/*), while btrfs is not using the generic quota for several
reasons (mostly related to subvolume quota).
So that's why quota netlink gets nothing to report.
Thanks,
Qu
>
> Any advice would be appreciated.
> Thanks,
> -- Gabor Karsai
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
prev parent reply other threads:[~2018-01-07 6:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 1:34 btrfs quota exceeded notifications through netlink sockets Karsai, Gabor
2018-01-06 9:39 ` Duncan
2018-01-07 6:21 ` Qu Wenruo [this message]
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=f67fafee-fac3-21fa-d89f-a830da646ea5@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=gabor.karsai@Vanderbilt.Edu \
--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).