On Mon, Mar 04, 2002 at 08:47:06AM +0100, Alexander Skwar wrote:
I don't know exactly if this is really OK, but it is probably OK,
because you can have holes in a file (open/create file, seek to X MB
and write something, close it), so file size can be large but actual
disk usage is small.
Both are correct. That file has one giant hole, it's mostly nulls and
hasn't been allocated many disk blocks. 'ls' reports the filesize as
reported in the header of the file. 'du' reports the number of disk
blocks allocated. If you were to 'cp' that file, you'll find the new
file has a much
Hi.
Watch the following:
ls -lh core.29027
-rw---1 askwar askwar 6.2M Mär 4 00:45 core.29027
du -h core.29027
396Kcore.29027
Uhm, how can it be that ls reports that the file takes 6.2 MB and du
only says 396K? What is correct?
file core.29027
core.29027: ELF 32-bit
On Mon, Mar 04, 2002 at 01:25:53AM +0100, Alexander Skwar wrote:
ls -lh core.29027
-rw---1 askwar askwar 6.2M Mr 4 00:45 core.29027
du -h core.29027
396Kcore.29027
I don't know exactly if this is really OK, but it is probably OK,
because you can have holes in a file
»Martin Ma?ok« sagte am 2002-03-04 um 01:40:46 +0100 :
I don't know exactly if this is really OK, but it is probably OK,
because you can have holes in a file (open/create file, seek to X MB
and write something, close it), so file size can be large but actual
disk usage is small. Coredump is
