2003 R2 and FSRM Directory-based quotas

[Guest Adam McKee]

A few days ago I implemented the FSRM quota system because I prefer the

directory-path-based quota system to the file ownership-based system.

 

Since then, and on a few occasions, I've received alerts about quota

violations for directory paths that have NOT reached their quota. Case in

point being a path (let's call it D:\User) that had a 500MB quota. With 450MB

in that directory, new files were unable to be written because of the quota.

I deleted the quota entry in FSRM and recreated it, and now the quota works

as expected again.

 

Any idea what's causing this?

 

Any help would be greatly appreciated. TIA!

[Guest Meinolf Weber]

Re: 2003 R2 and FSRM Directory-based quotas

 

Hello Adam,

 

If files are exceeding the Hard limit quota it will not be possible to copy

them, so maybe the file was to big.

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> A few days ago I implemented the FSRM quota system because I prefer

> the directory-path-based quota system to the file ownership-based

> system.

>

> Since then, and on a few occasions, I've received alerts about quota

> violations for directory paths that have NOT reached their quota. Case

> in point being a path (let's call it D:\User) that had a 500MB quota.

> With 450MB in that directory, new files were unable to be written

> because of the quota. I deleted the quota entry in FSRM and recreated

> it, and now the quota works as expected again.

>

> Any idea what's causing this?

>

> Any help would be greatly appreciated. TIA!

>

[Guest Adam McKee]

Re: 2003 R2 and FSRM Directory-based quotas

 

I have the quota template configured to send me an e-mail when someone tries

to exceed their quota, and in this example, the file was around 10KB. When I

saw that e-mail, I logged on to the webserver myself and tried to create a

new (empty) text file in their folder and was unable to because of the quota,

even though they were only using 88% of their quota.

 

Also, deleting the quota entry and recreating it fixed the problem, which

makes me wonder about corruption in whatever files store the quota data.

 

Anyone?

 

 

"Meinolf Weber" wrote:

> Hello Adam,

>

> If files are exceeding the Hard limit quota it will not be possible to copy

> them, so maybe the file was to big.

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

> > A few days ago I implemented the FSRM quota system because I prefer

> > the directory-path-based quota system to the file ownership-based

> > system.

> >

> > Since then, and on a few occasions, I've received alerts about quota

> > violations for directory paths that have NOT reached their quota. Case

> > in point being a path (let's call it D:\User) that had a 500MB quota.

> > With 450MB in that directory, new files were unable to be written

> > because of the quota. I deleted the quota entry in FSRM and recreated

> > it, and now the quota works as expected again.

> >

> > Any idea what's causing this?

> >

> > Any help would be greatly appreciated. TIA!

> >

>

>

>