ll command show very large size for the files

[Ahmed ABDOU_1]

hi admin
when we run ll commmand it shows the files size is very large

-rw-rw---- 192 258 32 4785950777412608 Feb 11 1997
lx2.nlb
-rw-rw---- 192 258 48 4785967957281792 Mar 24 1997
lx2c.nlb
-rw-rw---- 192 259 64 4785985137150976 Mar 24 1997
lx22.nlb
-rw-rw---- 192 259 80 4786036676759040 Feb 11 1997
lx2d.nlb

Also When We tried to copy or move this files to another location We got this error message.

# mv lx28.nlb /tmp
mv: lx28.nlb: File too large root@jubail:/u01/app/oracle/product/v7.3.3/ocommon/nls/admin/data.org

# cp -p lx28.nlb /tmp
cp: lx28.nlb: File too large root@jubail:/u01/app/oracle/product/v7.3.3/ocommon/nls/admin/data.org

the disk sixe is 2GB

best regards

[Paula J Frazer-Campbell]

Hi

If you have not rebboted the server for a while then:-

If you can umount the disk/lvol and run an fsck on it.


umount /

fsck /dev/vgXX/

HTH

Paula

[John Strang]

Hi Mohammed,

Something looks wrong here - not only are your files very large (too large for the disk you mentioned!) but they are very old too.

It would be worthwhile running a file system check on your filesystem - check 'man fsck' for info.

HTH,

John

[Emiel van Grinsven]

Hi,

Could it be that someone made a strange alias for your ll command?
This looks a bit like the output of ls -luns
This doesn't tell why the files are so large.

grt, Emiel

[John Palmer]

Are these files on a CD?

If so, (they sound like Oracle files) have you mounted the CD with pfs_mount as directed by Oracle?

Regards,
John

[Tracey]

I agree with John, Looks like a CD that didn't get mounted the way it needed to.

[Ahmed ABDOU_1]

hi all

thankyou for all your answers,but i want to tall you that i dont use CD these files are on Hard Disk not on CD.

Hi Paula

what the fsck will do for the filesystem

[Frank Slootweg · Accepted solution]

The 'size' displayed is indeed very large.

What kind of files are these?

Is this a file system with "large files" (>2GB) enabled? (i.e. "fsadm /dev/vg??/rlvol?").

These could be 'sparse' files. Sparse files, mostly database files, are mostly empty. ll(1) will show them as 'big', because it displays the *offset* between the first and last *used* bytes. du(1) will show them as 'small'(er), because it only shows the number of blocks (512 bytes/block) which actually have data in them.

[Paula J Frazer-Campbell]

Hi

fsck is run on your file system every time you reboot.

If you can unmount the disk / lvol then run:-

fsck -m /dev/vgxx/

From man fsck :-

-m Perform a sanity check only. fsck will return 0
if the file system is suitable for mounting. If
the file system needs additional checking, the
return code is 32. If the file system is mounted,
the return code is 33. Error codes larger than 33
indicate that the file system is badly damaged.

If errors are reported then run:-

fsck /dev/vgxx/

It will return somthing like this:-

root@k2/avro/DATA>fsck /dev/vg04/FMS
** /dev/vg04/FMS
** Last Mounted on /FMS
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
8427 files, 0 icont, 1291003 used, 3317421 free (2797 frags, 414328 blocks)

It will report errors and may ask your permission to fix them.

If unsure plan a server reboot and let the system do it for you.

HTH

Paula