System stalls at 4 gigs

[Alzhy]

It is not a Veritas Issue.

AS Matti had mentioned.. whatever utility the Boss is using to extract data and write toa "text file" is likely facing the 32 bit challenge/limit.

Largefiles top out at 2GB for the VxFS (aka OJFS) filesystem

May we know what "tool" the Boss is using?

[Steven Schweda]

> May we know what "tool" the Boss is using?

I've been waiting for an answer to that
question for about a week. I'm not holding
my breath.

[Laurent Menase]

> >Laurent: cat is useless

> (Perhaps you meant unnecessary?)
yes : you are right, my English lack of nuances and accuracy. cat is unnecessary there, but of course still very useful.- in French the same word is used for useless and unnecessary


> I thought about that but I'm pretty sure
> I've gotten errors in the past?
are you sure it was not with fbackup/frestore? or with tar xf or tar tf
indeed it is possible that tar xf/tf uses lseek() but tar cf doesn't need it because only using write.

I'm thinking that it's the write or lseek that will fail because they aren't the 64 bit version?
in fact only lseek is different. write() don't mind if the O_LARGEFILE is set or not, the problem is with the API, lseek() API only get a 32bits offset.

> I just tested it and you're right,
> tar doesn't fail and doesn't use lseek(2).
Indeed

> But you can also solve it by using pax(1)
> instead of tar.
of course, but my purpose here was just to give an example when we reach that 4gb limit with opened files, and how to workaround it using fd inheritence.

[Dennis Handly]

>Laurent: but my purpose here was just to give an example when we reach that 4gb limit

Except that limit is 2 Gb, not 4.