Re: DBA_TEMP_FILES.MAXBYTES is wrong

Hi,

Sorry for late answer, but I wrote about ls -ls not ls -l in my earlier post.
ls -ls shows the *real* filesystem space usage of a file, in filesystem blocks.

Note that newer cp and tar commands can handle sparse files the way that they remain sparse after copying to different location, so if you want to force a tempfile to actually use all of the space allowed for it, you could either use dd or cp special option to disable sparsity (like --sparse=never on redhat linux)

Tanel.

----- Original Message ----- From: "zhu chao" <zhuchao@xxxxxxxxx>
To: <tanel.poder.003@xxxxxxx>
Cc: "ORACLE-L" <oracle-l@xxxxxxxxxxxxx>
Sent: Tuesday, May 31, 2005 1:32 AM
Subject: Re: DBA_TEMP_FILES.MAXBYTES is wrong


Tanel,
For sparse file, ls -l will not show the actual file. as oracle tempfiles.
For example, in solaris 10/redhat 3.
In linux redhat as3:

SQL> create temporary tablespace tmp tempfile '/tmp/a.dbf' size 20001m
autoextend on maxsize 40001m;

Tablespace created.


SQL> ! ls -l /tmp/a.dbf
-rw-r----- 1 oracle dba 20972584960 May 31 08:24 /tmp/a.dbf

SQL> ! df -k /tmp
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda5 2055600 32996 1918184 2% /tmp
On 5/31/05, Tanel Põder <tanel.poder.003@xxxxxxx> wrote:

'ls -ls' shows the real size of file in filesystem blocks on most modern
unixes as well...

Tanel. 

--
http://www.freelists.org/webpage/oracle-l

Other related posts: