|Summary:||mod_webdav ignores quota|
|Component:||mod_dav||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
Description waldemar.brodkorb 2013-02-15 10:32:27 UTC
Hi *, I am using a Debian 6.0.6 system with Apache 2.2.16. # apache2 -v Server version: Apache/2.2.16 (Debian) Server built: Nov 30 2012 08:33:45 I like to use webdav and configured it correctly. It works fine so far. Now the problem: The data for the webdav share is physical located on a Windows CIFS share with NTFS as filesystem and configured quota to limit data to 50 MB. On Linux I get a correct message, when I try to copy a file on a "full" share: www-data@Skolerouter:~$ env LANG=c cp rules.png /var/davmnt/Lehrer/Lehrer1/ cp: closing `/var/davmnt/Lehrer/Lehrer1/rules.png': No space left on device www-data@Skolerouter:~$ mount .. //172.16.0.2/Lehrer1$/ on /UNIONFS/var/davmnt/Lehrer/Lehrer1 type cifs (rw,mand,relatime,vers=1.0,sec=ntlmi,cache=loose,unc=\z.16.0.2\Lehrer1$,username=Lehrer1,uid=0,noforceuid,gid=0,noforcegid,addr=172.16.0.2,file_mode=0666,dir_mode=0777,nounix,serverino,rsize=61440,wsize=16580,actimeo=1) When I upload a file with Linux and cadaver or with Windows 7, I get no error message, but a NULL byte file is created: dav:/Lehrer1/> put qemu.bz2 Uploading qemu.bz2 to `/Lehrer1/qemu.bz2': Progress: [=============================>] 100,0% of 9865186 bytes succeeded. dav:/Lehrer1/> ls Listing collection `/Lehrer1/': succeeded. Coll: Eigene Dateien 0 Feb 14 15:28 Coll: Favoriten 0 Feb 14 14:21 7z920-x64.msi 0 Feb 14 16:39 foo 51179520 Feb 15 11:10 foo.png 1231977 Feb 14 16:47 http.so 0 Feb 15 11:11 index.php 940 Feb 15 11:11 qemu.bz2 0 Feb 15 11:27 rules.png 0 Feb 15 11:25 dav:/Lehrer1/> When there is some space left on the device, data is filled up to the quota limit and the uploaded file is broken. Shouldn't mod_webdav tell the user that the underlying operating system can not write the file? Thanks for any hints or fixes. best regards Waldemar Brodkorb
Comment 1 William A. Rowe Jr. 2018-11-07 21:07:59 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.