Dan Martin wrote:

| XeniXman wrote:
| > I appologize if this has already been covered, but I couldn've find it.
| > Ruinning OSR6.0 with VxFS filesystem.
| >
| > I made a file that SHOULD BE over 3 Gig in size via:
| >
| > find /usr/data -print | lone-tar cvf - >filename.ltar
| >
| > I watched the file size of filename.ltar grow to 2 gig. At that point,
| > the size stopped growing even though the lone-tar continued to output
| > to stdout..
| >
| > I then tried to verify the data and got a broken pipe in the middle of
| > the file (approx the 2 gig point)
| >
| > I thought the VxFS could handle files larger than 2 gig? I don't
| > believe the problem is with lone-tar because the shell is creating the
| > file ">filename.ltar". Is the Bourne shell causing this??
| >
| > thanks ever so much...
|
| HI Xenixman,
|
| Start here:
| http://tinyurl.com/l9y8n
|
| Good luck,
| Dan Martin

Thanks for that link, Dan.

And following the link to the URL on that page leads to a page
that specifically notes that the shells have not been made aware
of file sizes larger than 2 Gb, so they can't be created by
redirection as Xenixman was attempting to do.

So the answere to his question is, yes - the Bourne shell is
causing that.

Bob

--
Bob Stockler +-+ bob@trebor.iglou.com +-+ http://members.iglou.com/trebor