User quota problems during delete

[Thescot]

We are having an issue with user quotas that are not correct. Our
investigation has shown that there appears to be a problem with how
NetWare is adjusting user quotas during a delete operation.

Given below is a sequence of steps that reproduce the problem WITHOUT
any other software being loaded:

1. Create a user with a quota associated with a volume, and login as
that user. Quota used = 0.
2. Copy a 0.25MB file to the volume. Quota used = .25MB.
3. Delete the file. Quota used = 0.
4. Login as administrator.
5. Salvage the file. Quota used = .25MB.
6. Delete the file. Quota used = .25MB (Unexpected result)!
7. Purge the file. Quota used = .25MB

The issue is that the user's quota is not adjusted during the delete
Step(6) when logged in as an administrator. Note, however, that the
salvage in Step(5) increases the user quota as expected.

If you do the same test, but skip Step(4) of logging in as an
administrator, then you get the expected results in Steps(6 and 7) of
Quota used = 0.

This implies to us that the quota adjustment by NetWare during deletion
is dependent on who does the delete, while the salvage does not.

We have tested this with NetWare 6.5 SP4 and SP5 with the same results.

Does anyone know if there is a fix for this problem, or a workaround
that does not involve logging in as a user?

Scott

[Jeff Lawson]

Scott,

This doesn't seem like a LibC or even a developer question. What APIs are
you using? This seems like a technical support type question, have you tried
opening an incident with them?

I think you will need to let whoever works on this problem know whether the
filesystem in question is an NSS or a legacy file system.

Jeff Lawson
NetWare Core OS
LibC Engineering

>>> On 10/30/2006 at 12:46 PM, in message
<zEs1h.21866$0h7....@prv-forum2.provo.novell.com>,

[Robert Charles Mahar]

Is the volume NSS or TFS? ( Or does the same happen on BOTH? ) What
version of the clients were you using? What tool did you use to do
the delete / salvage?

When volume is remounted ( or server rebooted ) does the quota "fix"
itself? Does the quota fix itself using the procedure documented in
the TIDs to fix broken quotas?

-- Bob

- - - - - - - - - - - - - - - - -
Robert Charles Mahar
Traffic Shaping Engine for NetWare
http://www.TrafficShaper.com
- - - - - - - - - - - - - - - - -

[John Baird]

Scott

Just a quick comment. The deleted file will be owned by your user, but upon
recovery ownersip is changed to the account doing the recovery. So recovery
of the file should not contribute 0.25MB to the users quota in step 5. It
will add 0.25 MB to the administrators usage assuming they have a
restriction on the volume. The quota adjustment should be independent of the
deletor but dependent on the salvagor.

John

"Thescot" <notr...@socal.rr.com> wrote in message
news:zEs1h.21866$0h7....@prv-forum2.provo.novell.com...

[Robert Charles Mahar]

I get that part, but he indicates that even after a purge, the ordinary
user's quota does not indicate 0 usage. Nor does the file, salvaged as
Admin, reduce the user's quota usage. ( According to the post. ) So
it is pretty odd if true.

We have not heard back so perhaps he made a mistake in his testing.

-- Bob

- - - - - - - - - - - - - - - - -
Robert Charles Mahar
Traffic Shaping Engine for NetWare
http://www.TrafficShaper.com
- - - - - - - - - - - - - - - - -

[Thescot]

Yes, it is reasonable for the salvage and purge quotas to be added to
the admin account in this example. The problem is that one is and the
other isn't. As noted, the salvage adds the quota back to the user's
account, while the purge doesn't.

Thescot