xfs
[Top] [All Lists]

Re: xfs and warnquota on Debian stable: no go

To: "Ralf G. R. Bergs" <rabe@xxxxxxxxxxxxxx>
Subject: Re: xfs and warnquota on Debian stable: no go
From: Nathan Scott <nathans@xxxxxxx>
Date: Wed, 19 Jun 2002 09:59:46 +1000
Cc: Linux XFS Mailing List <linux-xfs@xxxxxxxxxxx>, Michael Meskes <meskes@xxxxxxxxxx>, Jan Kara <jack@xxxxxx>
In-reply-to: <E17KKoF-0004Ck-00@ADSL-Bergs.RZ.RWTH-Aachen.DE>
References: <20020617214113.GC469@frodo> <E17KKoF-0004Ck-00@ADSL-Bergs.RZ.RWTH-Aachen.DE>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.4i
hi Ralf,

On Tue, Jun 18, 2002 at 05:22:19PM +0200, Ralf G. R. Bergs wrote:
> On Tue, 18 Jun 2002 07:41:13 +1000, Nathan Scott wrote:
> 
> >Can you send "repquota -va" output from your system?
> 
> Sure can do. :-)
> 
> Here you are:
> 
> ====================== 8x =======================
> 
> Fileserver:~# repquota -va
> *** Report for user quotas on device /dev/sdc5
> Block grace time: 7days; Inode grace time: 7days
>                         Block limits                File limits
> User            used    soft    hard  grace    used  soft  hard  grace
> ----------------------------------------------------------------------
> root      -- 49496204       0       0         264643     0     0       
> dummy     +- 51912012       0 3000000          16808     0     0       
> dummy     --     608        0       0             55     0     0
> dummy     --  927868        0 3000000           1141     0     0
> ...

Ahah! - I see the problem [slaps hand to forehead].

Firstly, I'll assume all these 'dummy' entries are users with
"names changed to protect the innocent" - otherwise there's
something very odd about your /etc/passwd. ;)

The reason you're not getting any mail sent is that warnquota
is _only_ looking at the soft limit field, and not at all at
the hard limit - its trying to tell people that they will be
punished soon, not that they are already being punished.  If
a user's soft limit is zero, it just ignores that entry.

So, the right workaround for you would probably be to set the
soft limit to something (less than or equal to the hard limit).
After a period of time, the soft limit becomes enforced as the
hard limit, so it's not all that "soft".  Anymore than that and
you would have to go hack at the warnquota.c source and make it
report to people above their hard limits too (I assume you got
into this state by switching quota enforcement on at some point
after people had used space).  That shouldn't be very hard to
do if you're interested in doing that - warnquota.c is quite a
simple program - start looking at the check_offence() routine,
for example, and go from there (the mail body would need changes
too as it makes references to soft limits becoming enforced as
hard limits).

cheers.

-- 
Nathan


<Prev in Thread] Current Thread [Next in Thread>