- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- System stalls at 4 gigs
Operating System - HP-UX
1755647
Members
3162
Online
108837
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2010 05:42 AM
тАО11-24-2010 05:42 AM
Re: System stalls at 4 gigs
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?
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?
Hakuna Matata.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2010 05:58 AM
тАО11-24-2010 05:58 AM
Re: System stalls at 4 gigs
> 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.
I've been waiting for an answer to that
question for about a week. I'm not holding
my breath.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2010 07:40 AM
тАО11-24-2010 07:40 AM
Re: System stalls at 4 gigs
> >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.
> (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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2010 04:29 PM
тАО11-24-2010 04:29 PM
Re: System stalls at 4 gigs
>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.
Except that limit is 2 Gb, not 4.
- « Previous
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP