Bug #65446 [Fbk->NoF]: disk_total_space doesn't work with LVM
Edit report at https://bugs.php.net/bug.php?id=65446&edit=1
ID: 65446
Updated by: remi@php.net
Reported by: puciek at gmail dot com
Summary: disk_total_space doesn't work with LVM
-Status: Feedback
+Status: No Feedback
Type: Bug
Package: Filesystem function related
Operating System: Centos, Gentoo, Ubuntu
PHP Version: 5.4.17
Block user comment: N
Private report: N
New Comment:
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.
Previous Comments:
------------------------------------------------------------------------
[2013-08-27 11:25:19] remi@php.net
I means which "exact" value for directory option.
If you use "/dev/mapper/batty-root" which is only a file (ok, a special one) it will
report about space in /dev (so 4G)
If you use "/" it will report about space in /
------------------------------------------------------------------------
[2013-08-27 10:29:08] puciek at gmail dot com
Director inside LVM share which we want to measure
------------------------------------------------------------------------
[2013-08-27 09:30:06] remi@php.net
I was asking for the option given to the disk_total_space call.
------------------------------------------------------------------------
[2013-08-27 08:29:57] puciek at gmail dot com
df with parameter "-h" changes the output data from bytes to more human readable
format
-h, --human-readable
print sizes in human readable format (e.g., 1K 234M 2G)
------------------------------------------------------------------------
[2013-08-27 08:26:32] remi@php.net
I cannot reproduce, tested with
PHP 5.4.19 / RHEL-6
PHP 5.5.3 / Fedora 19
As this function is a simple wrapper other the statvfs (or statfs), I don't think of a PHP bug.
What is the option used in the test call ?
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=65446
--
Edit this bug report at https://bugs.php.net/bug.php?id=65446&edit=1
Thread (8 messages)