On Tue, Feb 28, 2006 at 10:27:42AM -0600, Bryan Penney wrote:
On the status page the pool information is reported as
Pool is 227.53GB comprising 1157013 files and 4369 directories (as of
2/28 08:33),
When I run df -h /dev/sda3 (the raid backuppc is on) I get:
FilesystemSize
On Tue, Feb 28, 2006 at 10:27:42AM -0600, Bryan Penney wrote:
On the status page the pool information is reported as
Pool is 227.53GB comprising 1157013 files and 4369 directories (as of
2/28 08:33),
When I run df -h /dev/sda3 (the raid backuppc is on) I get:
FilesystemSize
It is on reiserfs, so I guess that would make sense if backupPC gets its
usage info through du
David Brown wrote:
On Tue, Feb 28, 2006 at 10:27:42AM -0600, Bryan Penney wrote:
On the status page the pool information is reported as
Pool is 227.53GB comprising 1157013 files and 4369
Bryan Penney writes:
On the status page the pool information is reported as
Pool is 227.53GB comprising 1157013 files and 4369 directories (as of
2/28 08:33),
When I run df -h /dev/sda3 (the raid backuppc is on) I get:
FilesystemSize Used Avail Use% Mounted on
/dev/sda3
Perhaps this will help: http://physics.nist.gov/cuu/Units/binary.html
In short, it would be best to use "df -H" to get the disk storage
standard of 10^6 for "a MB", rather than "2^20" for MiB. If you want
raw numbers, the closest I think you can come is "df --block-size 1000"
or "df
Bill Hudacek wrote:
Perhaps this will help: http://physics.nist.gov/cuu/Units/binary.html
In short, it would be best to use df -H to get the disk storage
standard of 10^6 for a MB, rather than 2^20 for MiB. If you want
raw numbers, the closest I think you can come is df --block-size 1000
