#39520 [Opn->Bgs]: disk_free_space uses f_frsize but it should use f_bsize
| From: | iliaa@php.net | Date: | Thu, 16 Nov 2006 15:47:11 +0000 |
| Subject: | #39520 [Opn->Bgs]: disk_free_space uses f_frsize but it should use f_bsize | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-105103@lists.php.net to get a copy of this message | ||
ID: 39520
Updated by: iliaa@php.net
Reported By: david at triax dot jp
-Status: Open
+Status: Bogus
Bug Type: Filesystem function related
Operating System: RedHat Enterprise ES 4
PHP Version: 5.2.0
New Comment:
I've checked the current behavior against other applications
and utilities that calculate free disk space and PHP's
approach is perfectly inline with what other people are doing.
Previous Comments:
------------------------------------------------------------------------
[2006-11-16 03:46:01] david at triax dot jp
Changed the subject to reflect the actual bug. From the stat(2) man
page, fr_size is "the 'preferred' block-size for efficient file system
I/O." This means that it's *not* the blocksize of the actual device and
is not useful for calculating the size of the device.
------------------------------------------------------------------------
[2006-11-16 03:42:04] david at triax dot jp
This is not a bogus bug. Please reread.
------------------------------------------------------------------------
[2006-11-16 03:41:30] david at triax dot jp
This is not a bogus bug. Please reread.
------------------------------------------------------------------------
[2006-11-15 11:35:32] david at triax dot jp
As I wrote initially, it is either using f_frsize or just using a fixed
blocksize and as you point out it's using f_frsize, and that is wrong.
It should use f_bsize when calculating free space.
------------------------------------------------------------------------
[2006-11-15 09:53:40] tony2001@php.net
No, you are wrong. See lines 365-369 here:
http://cvs.php.net/viewvc.cgi/php-src/ext/standard/filestat.c?view=annotate
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/39520
--
Edit this bug report at http://bugs.php.net/?id=39520&edit=1