Hello,
I don't think this is a bug, look at this:
[EMAIL PROTECTED]:~/bla$ ls -lh
total 0
-rw-r--r-- 1 henry henry 512M Sep 28 10:29 a.img
-rw-r--r-- 1 henry henry 512M Sep 28 10:29 b.img
-rw-r--r-- 1 henry henry 512M Sep 28 10:29 c.img
-rw-r--r-- 1 henry henry 512M Sep 28 10:29 d.img
[EMAIL PROTECTED]:~/bla$ du -h
4.0K .
[EMAIL PROTECTED]:~/bla$ ls -lhs
total 0
0 -rw-r--r-- 1 henry henry 512M Sep 28 10:29 a.img
0 -rw-r--r-- 1 henry henry 512M Sep 28 10:29 b.img
0 -rw-r--r-- 1 henry henry 512M Sep 28 10:29 c.img
0 -rw-r--r-- 1 henry henry 512M Sep 28 10:29 d.img
The files were created with qemu-img. Note, that the first column in the ls
-lhs command
prints the disk allocation of each file which can differ from the file size. du
prints
also the disk allocation, and so does df.
info coreutils ls says about this:
`--size'
Print the disk allocation of each file to the left of the file
name. This is the amount of disk space used by the file, which is
usually a bit more than the file's size, but it can be less if the
file has holes.
I'm no filesystem expert, but I think this may be the reason of the "bug" you
discovered.
Just do a ls -lhs and compare the first column with the "total" statement of ls.
Regards,
Henry
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
