>
>
> I'm attempting to create a 3GB file on an XFS filesystem using Oracle 8i
> running on RedHat 7.1 with a generic 2.4.10 kernel and I'm getting some
> errors. Here's the command and output I'm getting:
>
> CREATE TABLESPACE ALTUSER DATAFILE
> '/export/4/oracle/oradata/alt/data01.dbf' SIZE 3000M REUSE AUTOEXTEND ON
> NEXT 1280K
> MINIMUM EXTENT 128K DEFAULT STORAGE ( INITIAL 128K NEXT 128K MINEXTENTS
> 1 MAXEXTENTS 4096 PCTINCREASE 0);
>
> CREATE TABLESPACE ALTUSER DATAFILE
> '/export/4/oracle/oradata/alt/data01.dbf' SIZE 3000M REUSE
> *
> ORA-01119: error in creating database file
> '/export/4/oracle/oradata/alt/data01.dbf'
> ORA-27037: unable to obtain file status
> Linux Error: 75: Value too large for defined data type
>
> =========================================
>
> Any ideas as to what could be causing this? I thought the file size
> limit is 4GB which is why I made the file 3GB. Is this correct or am I
> missing something?? Many thanks!!
>
>
> --
> Jesse W. Asher jasher1@xxxxxxxxxxxxxxx
>
Hi,
First of all, please try not to use html mail on the xfs mailing list,
it gets pulled out by mailing filters (not really sure why, but
we do not control this).
Secondly, 2.4.10 is not the best version of linux in the world, 2.4.14
is the current revision, and we also have 2.4.9 based redhat 7.1 & 7.2
kernel rpms available.
Finally the file size issue, for files larger than 2Gbytes, an
application needs to open files with O_LARGEFILE to be able to
access data beyond the 2 Gbyte boundary. XFS itself will happily
go into the multi Tbyte file size, the linux system call layer will
not unless you tell it you want to.
Error 75 is EOVERFLOW, and is not returned by xfs itself on files (it is
on directories), the only places which can return it are file locking
stat and lseek calls, but only when the application uses the 32 bit
versions of these. Which makes me think that the problem may be in the
way Oracle has built their product.
Steve
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@xxxxxxx
|