All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@hist.no>
To: Olaf Hering <olh@suse.de>
Cc: DervishD <lkml@dervishd.net>,
	Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org
Subject: Re: OOM & [OT] util-linux-2.12e
Date: Mon, 20 Sep 2004 15:32:59 +0200	[thread overview]
Message-ID: <414EDC0B.3030108@hist.no> (raw)
In-Reply-To: <20040920132151.GA30175@suse.de>

Olaf Hering wrote:

> On Mon, Sep 20, Helge Hafting wrote:
>
>  
>
>>Using a mtab that is a link to /proc/mounts fails with quota too.
>>Quta tools read /etc/mtab looking for "usrquota" and or "grpquota"
>>mount options.  These appear in a normal /etc/mtab but not in /proc/mounts,
>>    
>>
>
>I have never played with quota. But: does the kernel or a userland tool
>if quota is active for a mount point? smells like a kernel bug.
>  
>
The kernel must know that quota is in use, or it'd be unable to
refuse the syscalls when someone tries to go over his quota.

 From "man mount":
       grpquota / noquota / quota / usrquota
              These  options are accepted but ignored.  (However, quota 
utili‐
              ties may react to such strings in /etc/fstab.)

quota utilities indeed react to such strings in /etc/mtab too.

Qutas aren't actually enabled when the mount options are used,
they are enabled when the "quotaon" tool runs.  I guess it uses
some special syscall or ioctl to really turn quota on.

Doing it at mount time instead, byt actually using those options,
seems saner to me.  But I guess they had their reasons. . .

Helge Hafting



  reply	other threads:[~2004-09-20 13:28 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-19 22:05 OOM & [OT] util-linux-2.12e Andries.Brouwer
2004-09-20  9:46 ` Olaf Hering
2004-09-20 10:12   ` Andreas Schwab
2004-09-20 10:54     ` DervishD
2004-09-20 11:43       ` Andreas Schwab
2004-09-20 11:51         ` Paulo Marques
2004-09-20 12:11           ` DervishD
2004-09-20 12:14           ` Andreas Schwab
2004-09-20 12:00         ` DervishD
2004-09-20 10:23   ` Roman Zippel
2004-09-20 10:56     ` Olaf Hering
2004-09-20 11:16       ` Roman Zippel
2004-09-20 11:26         ` Olaf Hering
2004-09-20 11:38           ` Roman Zippel
2004-09-20 11:50             ` Olaf Hering
2004-09-20 12:02               ` Roman Zippel
2004-09-20 12:07                 ` Olaf Hering
2004-09-20 12:14                   ` Roman Zippel
2004-09-20 12:19                     ` Olaf Hering
2004-09-20 12:34                       ` Roman Zippel
2004-09-20 12:38                         ` Olaf Hering
2004-09-20 12:51                           ` Andreas Schwab
2004-09-20 12:54                             ` Olaf Hering
2004-09-20 13:19             ` CaT
2004-09-20 13:33               ` Andreas Schwab
2004-09-20 13:15     ` CaT
2004-09-20 10:59   ` DervishD
2004-09-20 13:24     ` Helge Hafting
2004-09-20 13:21       ` Olaf Hering
2004-09-20 13:32         ` Helge Hafting [this message]
2004-09-20 14:12           ` Herbert Poetzl
2004-09-21  7:20             ` Helge Hafting
2004-09-21  9:18               ` Herbert Poetzl
2004-09-20 15:24     ` Tonnerre
2004-09-20 11:11   ` David Gómez
2004-09-20 11:06 ` DervishD
2004-09-20 11:38   ` Xavier Bestel
2004-09-20 11:59     ` DervishD
2004-09-20 12:32       ` Xavier Bestel
2004-09-20 14:16         ` Herbert Poetzl
2004-09-21 16:45 ` Jari Ruusu
2004-09-21 21:26   ` Andries Brouwer
2004-09-22 17:05     ` Jari Ruusu
2004-09-22 18:39       ` Andries Brouwer

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=414EDC0B.3030108@hist.no \
    --to=helge.hafting@hist.no \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@dervishd.net \
    --cc=olh@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.