Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО08-03-2005 06:32 AM
тАО08-03-2005 06:32 AM
What about the latest version of Pax for 11.0/11.11, does the same rule apply?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-03-2005 07:58 AM
тАО08-03-2005 07:58 AM
Re: pax
/long/path/99/101
it got recorded by pax as
/long/path/99101
and then on restore there is an error about
the file not being found.
This has been fixed in the latest pax patches.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-03-2005 11:46 PM
тАО08-03-2005 11:46 PM
SolutionPHCO_30150 is the last 11.00 pax patch.
Neither of these patches mention any changes.
pax can handle a /dir/subdirectory/longfilename where the longfilename is 100 characters or less and the total length of /dir/subdirectory/ is 155 characters or less.
If you can point me to the post where you got the original information I posted, I can verify we are talking about the same issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2005 12:57 AM
тАО08-04-2005 12:57 AM
Re: pax
I believe you've answered my question. Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2005 06:27 AM
тАО08-04-2005 06:27 AM
Re: pax
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2005 07:36 AM
тАО08-04-2005 07:36 AM
Re: pax
Long symlink error:
pax: pax_test/0/one4567890/two4567890/three67890/four567890/five567890/six456789
0/seven67890/1234/s1 : Link name is longer than 100 chars.
Long hardlink error:
pax: pax_test/0/one4567890/two4567890/three67890/four567890/five567890/six456789
0/seven67890/eight67890/nine567890/bar : Link name is longer than 100 chars.
File name too long error:
pax: pax_test/012345678901234567890123456789012345678901234567890123456789012345
67890123456789012345678901234567890 : Path name element too long - skipped
Long directory path ( 178 characters ) seemed to work OK:
pax_test/0123456789/0123456789/0123456789/0123456789/0123456789/0123456789/01234
56789/0123456789/0123456789/0123456789/0123456789/0123456789/0123456789/01234567
89/0123456789/0123456789/0123456789/end