Removal of sparse file settings



Hi there,

Does any of You how to remove the 'Sparse file' settings on a jfs2 filesystem?

I got a problem (or my sap dbs's does)
We've got a jfs2 filesystem, the sap adm user, and the oracle adm user got 'unlimited' settings, like this:

time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) unlimited
memory(kbytes) unlimited
coredump(blocks) unlimited
nofiles(descriptors) unlimited

I can see that the filesystem is using 'sparse files', but how it got that setting, I don't know..

The sap administrator is trying to do an export, but got problems:

(EXP) ERROR: DbSlExeRead failed
rc = 99, table "/BIC/EZDLV_C01"
(SQL error 1116)
error message returned by DbSl:
ORA-01116: error in opening database file 3015
ORA-01110: data file 3015: '/unicode/Q22/extratemp/extratemp_1/extra_temp.data1'
ORA-27092: size of file exceeds file size limit of the process
Additional information: 262143
Additional information: 2621441
(DB) INFO: disconnected from DB

The file ‘extra_temp.data1' has a size of 20GB. It really looks like that there any limitation on the OS level for the file size. On the S22/U22 it was not a problem to handle file in this size.


I was able, at root and as the sap adm user, to create a file at 3GB, in the same filesystem, so I can't see that I've got an OS problem - or do I ??????


Could it be because the filesystem is using 'Sparse files' ? and how do I remove this setting again from the filesystem ????


Hope anyone can help me, since I'm bombarded with this problem all day long.


Thanks,


Gitte Tøgersen
AIX system Administrator
.



Relevant Pages

  • Re: /usr/bin/cp preserving holes ?
    ... >> supports sparse files, but I don't see that it has anything to do with NFS ... >> some differences in the block count (due to differences in filesystem ... Absent a decent interface to determine hole location, ...
    (comp.unix.solaris)
  • Re: cp: I do not understand ...
    ... but did you try using backup/restore with the source filesystem ... You could try to find the sparse files on the source ... on the new filesystem instead of copying them over. ...
    (comp.unix.aix)
  • Re: 6.x loosing record of free space after filesystem fills?
    ... These settings were chosen to optimize I/O throughput for Postgresql on the theory that a 64KB block size would maximize disk throughput in the general case and an 8K frag size would match Postgresql's page size. ... I wasn't aware of any known regressions in 6.x regarding large filesystem block sizes... ... > within the filesystem code and VM code that will cause such filesystems ...
    (freebsd-stable)
  • Re: O_DIRECT question
    ... there _is_ a problem, because they don't care. ... I don't regard it as a system failing that I am allowed to shoot myself ... Suppose you have a filesystem, not at all related to databases and stuff. ... "hope that sparse files are handled right" is a high hope. ...
    (Linux-Kernel)
  • Re: Interesting speed benchmarks
    ... I don't think that cpio or pax support ACLs or file ... I thought 'star' handled sparse files and all the extra magic? ... For backups I use vbackup & venti from plan9ports. ... filesystem namespace) ...
    (freebsd-current)