HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Using split command to transfer files
Operating System - HP-UX
1833294
Members
2999
Online
110051
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
07-14-2003 03:12 AM
07-14-2003 03:12 AM
Using split command to transfer files
Hi,
I have a file(not a filesystem) which is about 3GB in size. I would like to transfer this huge file over the WAN.
However, when I tried using rsync as tool to transfer this file over the WAN, it just hangs indefinitely.
Hence I tried breaking up the file into smaller equal sized chunks using:
# split -b 100000K bigFile.tar.gz
Once using split on the file above, I obtain the files with names beginning with xa i.e.
xaa
xab
xac
(list continues ...)
I'm able to regroup this file into back into its original file(after transferring each one of them), by doing:
#!/bin/sh
cat xaa xab xac xad xae xaf xag > join
However, I do have several other files of such enormity. I noticed that whenever a file is split using the split command, it will always produce files beginning with names xa[a...], no matter if the files are different.
This would be difficult to track if I were to transfer several of those files simultaneously.
Could anyone kindly show me a better way of solving this problem?
Thanks.
I have a file(not a filesystem) which is about 3GB in size. I would like to transfer this huge file over the WAN.
However, when I tried using rsync as tool to transfer this file over the WAN, it just hangs indefinitely.
Hence I tried breaking up the file into smaller equal sized chunks using:
# split -b 100000K bigFile.tar.gz
Once using split on the file above, I obtain the files with names beginning with xa i.e.
xaa
xab
xac
(list continues ...)
I'm able to regroup this file into back into its original file(after transferring each one of them), by doing:
#!/bin/sh
cat xaa xab xac xad xae xaf xag > join
However, I do have several other files of such enormity. I noticed that whenever a file is split using the split command, it will always produce files beginning with names xa[a...], no matter if the files are different.
This would be difficult to track if I were to transfer several of those files simultaneously.
Could anyone kindly show me a better way of solving this problem?
Thanks.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2003 03:16 AM
07-14-2003 03:16 AM
Re: Using split command to transfer files
split -b 100000K bigfile.tar.gz bigfile
now you will get like bigfileaa, bigfileab ....
Regards,
Karthik S S
now you will get like bigfileaa, bigfileab ....
Regards,
Karthik S S
For a list of all the ways technology has failed to improve the quality of life, please press three. - Alice Kahn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2003 03:18 AM
07-14-2003 03:18 AM
Re: Using split command to transfer files
Peter,
According to the man page, "The name of the first output file is name with
aa appended, and so on lexicographically, up to zz (only ASCII letters
are used, a maximum of 676 files). If no output name is given, x is
the default."
So, if you add the optional 'name' paramter, you can control the output file naming to your liking.
"split [-b n[k|m]] [-a suffix_length] [file [name]]"
Pete
Pete
According to the man page, "The name of the first output file is name with
aa appended, and so on lexicographically, up to zz (only ASCII letters
are used, a maximum of 676 files). If no output name is given, x is
the default."
So, if you add the optional 'name' paramter, you can control the output file naming to your liking.
"split [-b n[k|m]] [-a suffix_length] [file [name]]"
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2003 03:21 AM
07-14-2003 03:21 AM
Re: Using split command to transfer files
Hi,
from "man split"
The name of the first output file is name with
aa appended, and so on lexicographically, up to zz (only ASCII letters
are used, a maximum of 676 files). If no output name is given, x is
the default.
So, if you want a different beginning, just specify a name !
HTH,
Massimo
from "man split"
The name of the first output file is name with
aa appended, and so on lexicographically, up to zz (only ASCII letters
are used, a maximum of 676 files). If no output name is given, x is
the default.
So, if you want a different beginning, just specify a name !
HTH,
Massimo
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP