Hello Alphas :
My original post was :
> I've got the following situation :
> A Sybase file was crated on a file sytem named /us1/tmpdb. Tha Sybase
> aplication is reporting that file with 150 MB.
> The ls command is reporting it too, like a file of 150 MB. But, if a "df
> -k"
> is executed, the information is 146000 blocks free, and only 33750 blocks
> used.
> And a command "du -k /us1/tmpdb/tmpdb" reports 23664 blocks.
> The partition where the file system was mounted has a size of 200 MB
> (aprox.)
> The O.S. is DU 4.0D + patch kit # 2.
> The Sybase Server is reporting an error on phisics page, pointing to that
> base.
>
Thanks to all who responded, Alan, Joe, Laurent, Oisin, Ray and Rye.
Alan Nabeth pointed me at the most complete way. He wrote :
It sounds like the file was created with one or more holes; a
sparse file. This is a feature of most UNIX systems where
space needn't be allocated to all the blocks of a file. The
hole reads as NULs and has space allocated when written. One
way to verify is to use the -ls option on ls, which will print
both the byte size and allocated block size. If the two
disagree by a significant amount, you have a sparse file.
Some database systems don't like sparse files. If Sybase is
one of those, you'll want to fill in the wholes. Simply
making a copy (where you have space) will be sufficient.
Thanks to all again.
Best regards
CRV.
Received on Mon Mar 22 1999 - 13:34:23 NZST