* Aw: Re: Defining quota on /home
@ 2018-12-23 12:46 c.monty
2018-12-23 16:31 ` Remi Gauvin
0 siblings, 1 reply; 2+ messages in thread
From: c.monty @ 2018-12-23 12:46 UTC (permalink / raw)
To: Andrei Borzenkov; +Cc: linux-btrfs
I'm sorry.
Of course the line
0/279 1.79GiB 1.79GiB 150.00GiB none
is correct.
The issue is with this line:
255/279 1.79GiB 1.79GiB none none
I didn't define a quota like this.
THX
Gesendet: Samstag, 22. Dezember 2018 um 05:07 Uhr
Von: "Andrei Borzenkov" <arvidjaar@gmail.com>
An: c.monty@web.de, linux-btrfs@vger.kernel.org
Betreff: Re: Defining quota on /home
21.12.2018 17:22, c.monty@web.de пишет:
> Hi,
>
> I have defined a quota on home with these steps:
> 1. btrfs quota enable /home
> 2. btrfs qgroup limit 150G /home
>
> Now I can verify the corresponding setting:
> btrfs qgroup show -reF /home
> WARNING: Qgroup data inconsistent, rescan recommended
> qgroupid rfer excl max_rfer max_excl
> -------- ---- ---- -------- --------
> 0/279 1.79GiB 1.79GiB 150.00GiB none
> 255/279 1.79GiB 1.79GiB none none
>
> However I don't understand the line with qgroupid 0/279?!?
>
This is default quota group created automatically for each subvolume. Or
do you mean 255/279?
> I have created another quota earlier for /var/log, and there's no second line in output of btrfs qgroup show:
> btrfs qgroup show -reF /var/log
> WARNING: Qgroup data inconsistent, rescan recommended
> qgroupid rfer excl max_rfer max_excl
> -------- ---- ---- -------- --------
> 0/275 56.52MiB 56.52MiB 5.00GiB none
>
> The following subvolumes do exist:
> btrfs su li /
> ID 257 gen 134 top level 5 path @
> ID 258 gen 36271 top level 257 path @/.snapshots
> ID 259 gen 36312 top level 258 path @/.snapshots/1/snapshot
> ID 260 gen 33772 top level 257 path @/boot/grub2/i386-pc
> ID 261 gen 33772 top level 257 path @/boot/grub2/x86_64-efi
> ID 262 gen 36311 top level 257 path @/opt
> ID 263 gen 33772 top level 257 path @/srv
> ID 264 gen 36312 top level 257 path @/tmp
> ID 265 gen 35961 top level 257 path @/usr/local
> ID 266 gen 36310 top level 257 path @/var/cache
> ID 267 gen 33772 top level 257 path @/var/crash
> ID 268 gen 33772 top level 257 path @/var/lib/libvirt/images
> ID 269 gen 33772 top level 257 path @/var/lib/machines
> ID 270 gen 33772 top level 257 path @/var/lib/mailman
> ID 271 gen 33772 top level 257 path @/var/lib/mariadb
> ID 272 gen 33772 top level 257 path @/var/lib/mysql
> ID 273 gen 33772 top level 257 path @/var/lib/named
> ID 274 gen 33772 top level 257 path @/var/lib/pgsql
> ID 275 gen 36312 top level 257 path @/var/log
> ID 276 gen 33772 top level 257 path @/var/opt
> ID 277 gen 36312 top level 257 path @/var/spool
> ID 278 gen 36309 top level 257 path @/var/tmp
> ID 279 gen 36311 top level 257 path @/home
> ID 280 gen 36311 top level 257 path @/usr/sap
> ID 308 gen 17373 top level 258 path @/.snapshots/19/snapshot
> ID 309 gen 17373 top level 258 path @/.snapshots/20/snapshot
> ID 315 gen 17373 top level 258 path @/.snapshots/25/snapshot
>
> This is the additional information demanded when asking a support question:
>
> lvevm117:~ # uname -a
> Linux lvevm117 4.4.162-94.72-default #1 SMP Mon Nov 12 18:57:45 UTC 2018 (9de753f) x86_64 x86_64 x86_64 GNU/Linux
>
> lvevm117:~ # btrfs --version
> btrfs-progs v4.5.3+20160729
>
> lvevm117:~ # btrfs fi show
> Label: none uuid: fbe2e4f1-2ccd-44df-bc35-790c5e019d66
> Total devices 1 FS bytes used 8.78GiB
> devid 1 size 198.84GiB used 23.07GiB path /dev/sda3
>
> lvevm117:~ # btrfs fi df /
> Data, single: total=20.01GiB, used=8.37GiB
> System, DUP: total=32.00MiB, used=16.00KiB
> Metadata, DUP: total=1.50GiB, used=414.19MiB
> GlobalReserve, single: total=27.38MiB, used=0.00B
>
>
> THX
>
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Aw: Re: Defining quota on /home
2018-12-23 12:46 Aw: Re: Defining quota on /home c.monty
@ 2018-12-23 16:31 ` Remi Gauvin
0 siblings, 0 replies; 2+ messages in thread
From: Remi Gauvin @ 2018-12-23 16:31 UTC (permalink / raw)
To: c.monty; +Cc: linux-btrfs
[-- Attachment #1.1.1: Type: text/plain, Size: 691 bytes --]
On 2018-12-23 7:46 a.m., c.monty@web.de wrote:
>
>
> I'm sorry.
> Of course the line
> 0/279 1.79GiB 1.79GiB 150.00GiB none
> is correct.
>
> The issue is with this line:
> 255/279 1.79GiB 1.79GiB none none
> I didn't define a quota like this.
>
I don't know if it's the 4.4 kernel, or the tools, but I observed the
same extra quota group whenever quotas were enabled on Ubunut 16.04 system.
I didn't give it much though, as it didn't hurt anything to have an
extra higher level group. (quotas and snapshots on that kernel were
effectively mutually exclusive features in any case.)
[-- Attachment #1.1.2: remi.vcf --]
[-- Type: text/x-vcard, Size: 203 bytes --]
begin:vcard
fn:Remi Gauvin
n:Gauvin;Remi
org:Georgian Infotech
adr:;;3-51 Sykes St. N.;Meaford;ON;N4L 1X3;Canada
email;internet:remi@georgianit.com
tel;work:226-256-1545
version:2.1
end:vcard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-12-23 16:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-12-23 12:46 Aw: Re: Defining quota on /home c.monty
2018-12-23 16:31 ` Remi Gauvin
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).