Bug 11552 - quota's don't work on my Win2k machines
Summary: quota's don't work on my Win2k machines
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: quota   
(Show other bugs)
Version: 6.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Preston Brown
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-05-21 16:38 UTC by jan.vandesompele
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-02-01 23:32:40 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description jan.vandesompele 2000-05-21 16:38:20 UTC

I apply a quota of 1000 Kb on a user, grace period zero days. When I try
to copy a file of 2000Kb on the users share, i get the message "disk
full". But still the file is copied into the share. I can keep putting
files on the share, although I always get the "disk full" message. I tried
it under a Win98 machine, and there the file isn't copied onto the disk. I
don't know if this is a quota or win2k bug...
To be completely clear:
I've set the soft limit to 1000 blocks (1 block = 1K) and the hardlimit to
1001 blocks.(no inode limits are set). repquota -gu / reports the correct
quota's for all users and groups.

Comment 1 SB 2000-05-29 19:32:59 UTC
I've read about Win2k NTFS and problems with NT not handling
quotas correctly.  One check might be to try it on NT 4.0
though I'm not sure it suffers from an apparent quota bug like
2000.  Make sure quotas are compiled into your kernel, and make
sure your quota stuff is properly configured, though I don't know
your setup...

-Stan Bubrouski

Comment 2 Preston Brown 2001-02-01 23:32:36 UTC
have you resolved this problem yet?  We don't do interoperability testing of
quotas with Windows.

Comment 3 Preston Brown 2001-03-10 06:57:42 UTC
This is an NT issue...our testing here shows that copying between linux boxes
results in the correct behaviour.

Note You need to log in before you can comment on or make changes to this bug.