What is maximum number of files you can store in a tar archive under Solaris 11?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I need to store a large number of files (> 100,000) in a tar archive and have run into the error: /bin/sh: /bin/tar: cannot execute [Arg list too long].



Are there limits with UNIX Solaris tar or GNU tar? Or, is this a ZFS issue? I am running Solaris 11.3 with ZFS.




solaris tar zfs limit gnu




share|improve this question


















  • 1




    How do you make the archive?
    – NickD
    Nov 20 '17 at 1:35






  • 2




    Appearances are a limit to tar’s argument list, not contents.
    – Jeff Schaller
    Nov 20 '17 at 1:38










  • As the error seems to be related to the number of arguments that have been passed on the command line, I think it would be useful to see what was the command you used for this purpose.
    – Scantlight
    Nov 20 '17 at 1:57










  • The error message is from /bin/sh (failing on execve), not from tar (as you can guess). If you replace tar by ls -l you'll get the same error
    – Basile Starynkevitch
    Nov 20 '17 at 12:01















up vote
1
down vote

favorite












I need to store a large number of files (> 100,000) in a tar archive and have run into the error: /bin/sh: /bin/tar: cannot execute [Arg list too long].



Are there limits with UNIX Solaris tar or GNU tar? Or, is this a ZFS issue? I am running Solaris 11.3 with ZFS.




solaris tar zfs limit gnu




share|improve this question


















  • 1




    How do you make the archive?
    – NickD
    Nov 20 '17 at 1:35






  • 2




    Appearances are a limit to tar’s argument list, not contents.
    – Jeff Schaller
    Nov 20 '17 at 1:38










  • As the error seems to be related to the number of arguments that have been passed on the command line, I think it would be useful to see what was the command you used for this purpose.
    – Scantlight
    Nov 20 '17 at 1:57










  • The error message is from /bin/sh (failing on execve), not from tar (as you can guess). If you replace tar by ls -l you'll get the same error
    – Basile Starynkevitch
    Nov 20 '17 at 12:01













up vote
1
down vote

favorite









up vote
1
down vote

favorite











I need to store a large number of files (> 100,000) in a tar archive and have run into the error: /bin/sh: /bin/tar: cannot execute [Arg list too long].



Are there limits with UNIX Solaris tar or GNU tar? Or, is this a ZFS issue? I am running Solaris 11.3 with ZFS.




solaris tar zfs limit gnu




share|improve this question














I need to store a large number of files (> 100,000) in a tar archive and have run into the error: /bin/sh: /bin/tar: cannot execute [Arg list too long].



Are there limits with UNIX Solaris tar or GNU tar? Or, is this a ZFS issue? I am running Solaris 11.3 with ZFS.





solaris tar zfs limit gnu





share|improve this question













share|improve this question




share|improve this question








edited Nov 20 '17 at 1:33









Jeff Schaller

32.1k849109




32.1k849109










asked Nov 20 '17 at 1:22









Matt Holliday

113




113







  • 1




    How do you make the archive?
    – NickD
    Nov 20 '17 at 1:35






  • 2




    Appearances are a limit to tar’s argument list, not contents.
    – Jeff Schaller
    Nov 20 '17 at 1:38










  • As the error seems to be related to the number of arguments that have been passed on the command line, I think it would be useful to see what was the command you used for this purpose.
    – Scantlight
    Nov 20 '17 at 1:57










  • The error message is from /bin/sh (failing on execve), not from tar (as you can guess). If you replace tar by ls -l you'll get the same error
    – Basile Starynkevitch
    Nov 20 '17 at 12:01













  • 1




    How do you make the archive?
    – NickD
    Nov 20 '17 at 1:35






  • 2




    Appearances are a limit to tar’s argument list, not contents.
    – Jeff Schaller
    Nov 20 '17 at 1:38










  • As the error seems to be related to the number of arguments that have been passed on the command line, I think it would be useful to see what was the command you used for this purpose.
    – Scantlight
    Nov 20 '17 at 1:57










  • The error message is from /bin/sh (failing on execve), not from tar (as you can guess). If you replace tar by ls -l you'll get the same error
    – Basile Starynkevitch
    Nov 20 '17 at 12:01








1




1




How do you make the archive?
– NickD
Nov 20 '17 at 1:35




How do you make the archive?
– NickD
Nov 20 '17 at 1:35




2




2




Appearances are a limit to tar’s argument list, not contents.
– Jeff Schaller
Nov 20 '17 at 1:38




Appearances are a limit to tar’s argument list, not contents.
– Jeff Schaller
Nov 20 '17 at 1:38












As the error seems to be related to the number of arguments that have been passed on the command line, I think it would be useful to see what was the command you used for this purpose.
– Scantlight
Nov 20 '17 at 1:57




As the error seems to be related to the number of arguments that have been passed on the command line, I think it would be useful to see what was the command you used for this purpose.
– Scantlight
Nov 20 '17 at 1:57












The error message is from /bin/sh (failing on execve), not from tar (as you can guess). If you replace tar by ls -l you'll get the same error
– Basile Starynkevitch
Nov 20 '17 at 12:01





The error message is from /bin/sh (failing on execve), not from tar (as you can guess). If you replace tar by ls -l you'll get the same error
– Basile Starynkevitch
Nov 20 '17 at 12:01











2 Answers
2






active

oldest

votes

















up vote
3
down vote













This is not a limitation of tar. You are exceeding the maximum size of arguments that can be passed to a program. If the list of file names is available in a file, then you can use GNU tar's -T option:



tar -c -f output.tar -T filelist.txt


Tar can also receive the file list from standard input by using - as the file name. For example, if you want to create an archive containing all files and subdirectories of mydir, you can pass the output of find to tar:



find mydir | tar -c -f output.tar -T -





share|improve this answer
















  • 1




    You are exceeding the maximum size of arguments that can be passed to a program. To be specific, that's likely a sh limit. csh has a much larger limit. Running csh<enter>host% tar -cvf tarfile.tar * can work when running the same command under sh fails with an arg list is too long error.
    – Andrew Henle
    Nov 20 '17 at 12:58










  • I've usually had the issue with the csh and better luck with the sh shell for this. But in this case I think creating an include file with the -I option would work better than passing the files as args.
    – sleepyweasel
    Nov 20 '17 at 19:04










  • Please read the tar man page before answerig questions, the -T option switches on Trusted Extensions and this is definitely not what you like. You probably ment the -I option...or did you refer to GNU tar? Then you should know that the official name for GNU tar is gtar,
    – schily
    Jun 28 at 7:48


















up vote
1
down vote













As others have said, the issue is (probably) the length of the command
and not the size of the archive. 
You should be able to do


tar cf tarfile file001 file002 … file100
tar uf tarfile file101 file102 … file200
tar uf tarfile file201 file202 … file300
 ︙

Alternatively, do
tar cf tarfile file001
to create the archive,
and then
tar cf tarfile file002 … file100
tar uf tarfile file101 file102 … file200
tar uf tarfile file201 file202 … file300
 ︙
(possibly with xargs) to add to it.




share|improve this answer




















  • Just be aware that updating a tar file with the number of entries in question can be excruciatingly slow.
    – Andrew Henle
    Nov 27 '17 at 17:17











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f405692%2fwhat-is-maximum-number-of-files-you-can-store-in-a-tar-archive-under-solaris-11%23new-answer', 'question_page');

);

Post as a guest

















2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
3
down vote













This is not a limitation of tar. You are exceeding the maximum size of arguments that can be passed to a program. If the list of file names is available in a file, then you can use GNU tar's -T option:



tar -c -f output.tar -T filelist.txt


Tar can also receive the file list from standard input by using - as the file name. For example, if you want to create an archive containing all files and subdirectories of mydir, you can pass the output of find to tar:



find mydir | tar -c -f output.tar -T -





share|improve this answer
















  • 1




    You are exceeding the maximum size of arguments that can be passed to a program. To be specific, that's likely a sh limit. csh has a much larger limit. Running csh<enter>host% tar -cvf tarfile.tar * can work when running the same command under sh fails with an arg list is too long error.
    – Andrew Henle
    Nov 20 '17 at 12:58










  • I've usually had the issue with the csh and better luck with the sh shell for this. But in this case I think creating an include file with the -I option would work better than passing the files as args.
    – sleepyweasel
    Nov 20 '17 at 19:04










  • Please read the tar man page before answerig questions, the -T option switches on Trusted Extensions and this is definitely not what you like. You probably ment the -I option...or did you refer to GNU tar? Then you should know that the official name for GNU tar is gtar,
    – schily
    Jun 28 at 7:48















up vote
3
down vote













This is not a limitation of tar. You are exceeding the maximum size of arguments that can be passed to a program. If the list of file names is available in a file, then you can use GNU tar's -T option:



tar -c -f output.tar -T filelist.txt


Tar can also receive the file list from standard input by using - as the file name. For example, if you want to create an archive containing all files and subdirectories of mydir, you can pass the output of find to tar:



find mydir | tar -c -f output.tar -T -





share|improve this answer
















  • 1




    You are exceeding the maximum size of arguments that can be passed to a program. To be specific, that's likely a sh limit. csh has a much larger limit. Running csh<enter>host% tar -cvf tarfile.tar * can work when running the same command under sh fails with an arg list is too long error.
    – Andrew Henle
    Nov 20 '17 at 12:58










  • I've usually had the issue with the csh and better luck with the sh shell for this. But in this case I think creating an include file with the -I option would work better than passing the files as args.
    – sleepyweasel
    Nov 20 '17 at 19:04










  • Please read the tar man page before answerig questions, the -T option switches on Trusted Extensions and this is definitely not what you like. You probably ment the -I option...or did you refer to GNU tar? Then you should know that the official name for GNU tar is gtar,
    – schily
    Jun 28 at 7:48













up vote
3
down vote










up vote
3
down vote









This is not a limitation of tar. You are exceeding the maximum size of arguments that can be passed to a program. If the list of file names is available in a file, then you can use GNU tar's -T option:



tar -c -f output.tar -T filelist.txt


Tar can also receive the file list from standard input by using - as the file name. For example, if you want to create an archive containing all files and subdirectories of mydir, you can pass the output of find to tar:



find mydir | tar -c -f output.tar -T -





share|improve this answer












This is not a limitation of tar. You are exceeding the maximum size of arguments that can be passed to a program. If the list of file names is available in a file, then you can use GNU tar's -T option:



tar -c -f output.tar -T filelist.txt


Tar can also receive the file list from standard input by using - as the file name. For example, if you want to create an archive containing all files and subdirectories of mydir, you can pass the output of find to tar:



find mydir | tar -c -f output.tar -T -






share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 20 '17 at 7:49









Johan Myréen

6,93711322




6,93711322







  • 1




    You are exceeding the maximum size of arguments that can be passed to a program. To be specific, that's likely a sh limit. csh has a much larger limit. Running csh<enter>host% tar -cvf tarfile.tar * can work when running the same command under sh fails with an arg list is too long error.
    – Andrew Henle
    Nov 20 '17 at 12:58










  • I've usually had the issue with the csh and better luck with the sh shell for this. But in this case I think creating an include file with the -I option would work better than passing the files as args.
    – sleepyweasel
    Nov 20 '17 at 19:04










  • Please read the tar man page before answerig questions, the -T option switches on Trusted Extensions and this is definitely not what you like. You probably ment the -I option...or did you refer to GNU tar? Then you should know that the official name for GNU tar is gtar,
    – schily
    Jun 28 at 7:48













  • 1




    You are exceeding the maximum size of arguments that can be passed to a program. To be specific, that's likely a sh limit. csh has a much larger limit. Running csh<enter>host% tar -cvf tarfile.tar * can work when running the same command under sh fails with an arg list is too long error.
    – Andrew Henle
    Nov 20 '17 at 12:58










  • I've usually had the issue with the csh and better luck with the sh shell for this. But in this case I think creating an include file with the -I option would work better than passing the files as args.
    – sleepyweasel
    Nov 20 '17 at 19:04










  • Please read the tar man page before answerig questions, the -T option switches on Trusted Extensions and this is definitely not what you like. You probably ment the -I option...or did you refer to GNU tar? Then you should know that the official name for GNU tar is gtar,
    – schily
    Jun 28 at 7:48








1




1




You are exceeding the maximum size of arguments that can be passed to a program. To be specific, that's likely a sh limit. csh has a much larger limit. Running csh<enter>host% tar -cvf tarfile.tar * can work when running the same command under sh fails with an arg list is too long error.
– Andrew Henle
Nov 20 '17 at 12:58




You are exceeding the maximum size of arguments that can be passed to a program. To be specific, that's likely a sh limit. csh has a much larger limit. Running csh<enter>host% tar -cvf tarfile.tar * can work when running the same command under sh fails with an arg list is too long error.
– Andrew Henle
Nov 20 '17 at 12:58












I've usually had the issue with the csh and better luck with the sh shell for this. But in this case I think creating an include file with the -I option would work better than passing the files as args.
– sleepyweasel
Nov 20 '17 at 19:04




I've usually had the issue with the csh and better luck with the sh shell for this. But in this case I think creating an include file with the -I option would work better than passing the files as args.
– sleepyweasel
Nov 20 '17 at 19:04












Please read the tar man page before answerig questions, the -T option switches on Trusted Extensions and this is definitely not what you like. You probably ment the -I option...or did you refer to GNU tar? Then you should know that the official name for GNU tar is gtar,
– schily
Jun 28 at 7:48





Please read the tar man page before answerig questions, the -T option switches on Trusted Extensions and this is definitely not what you like. You probably ment the -I option...or did you refer to GNU tar? Then you should know that the official name for GNU tar is gtar,
– schily
Jun 28 at 7:48













up vote
1
down vote













As others have said, the issue is (probably) the length of the command
and not the size of the archive. 
You should be able to do


tar cf tarfile file001 file002 … file100
tar uf tarfile file101 file102 … file200
tar uf tarfile file201 file202 … file300
 ︙

Alternatively, do
tar cf tarfile file001
to create the archive,
and then
tar cf tarfile file002 … file100
tar uf tarfile file101 file102 … file200
tar uf tarfile file201 file202 … file300
 ︙
(possibly with xargs) to add to it.




share|improve this answer




















  • Just be aware that updating a tar file with the number of entries in question can be excruciatingly slow.
    – Andrew Henle
    Nov 27 '17 at 17:17















up vote
1
down vote













As others have said, the issue is (probably) the length of the command
and not the size of the archive. 
You should be able to do


tar cf tarfile file001 file002 … file100
tar uf tarfile file101 file102 … file200
tar uf tarfile file201 file202 … file300
 ︙

Alternatively, do
tar cf tarfile file001
to create the archive,
and then
tar cf tarfile file002 … file100
tar uf tarfile file101 file102 … file200
tar uf tarfile file201 file202 … file300
 ︙
(possibly with xargs) to add to it.




share|improve this answer




















  • Just be aware that updating a tar file with the number of entries in question can be excruciatingly slow.
    – Andrew Henle
    Nov 27 '17 at 17:17













up vote
1
down vote










up vote
1
down vote









As others have said, the issue is (probably) the length of the command
and not the size of the archive. 
You should be able to do


tar cf tarfile file001 file002 … file100
tar uf tarfile file101 file102 … file200
tar uf tarfile file201 file202 … file300
 ︙

Alternatively, do
tar cf tarfile file001
to create the archive,
and then
tar cf tarfile file002 … file100
tar uf tarfile file101 file102 … file200
tar uf tarfile file201 file202 … file300
 ︙
(possibly with xargs) to add to it.




share|improve this answer












As others have said, the issue is (probably) the length of the command
and not the size of the archive. 
You should be able to do


tar cf tarfile file001 file002 … file100
tar uf tarfile file101 file102 … file200
tar uf tarfile file201 file202 … file300
 ︙

Alternatively, do
tar cf tarfile file001
to create the archive,
and then
tar cf tarfile file002 … file100
tar uf tarfile file101 file102 … file200
tar uf tarfile file201 file202 … file300
 ︙
(possibly with xargs) to add to it.





share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 24 '17 at 20:51









G-Man

11.6k82657




11.6k82657











  • Just be aware that updating a tar file with the number of entries in question can be excruciatingly slow.
    – Andrew Henle
    Nov 27 '17 at 17:17

















  • Just be aware that updating a tar file with the number of entries in question can be excruciatingly slow.
    – Andrew Henle
    Nov 27 '17 at 17:17
















Just be aware that updating a tar file with the number of entries in question can be excruciatingly slow.
– Andrew Henle
Nov 27 '17 at 17:17





Just be aware that updating a tar file with the number of entries in question can be excruciatingly slow.
– Andrew Henle
Nov 27 '17 at 17:17


















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f405692%2fwhat-is-maximum-number-of-files-you-can-store-in-a-tar-archive-under-solaris-11%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Se
Read more

Bahrain

Image
For other uses, see Bahrain (disambiguation). Sovereign island state in the Persian Gulf Kingdom of Bahrain مملكة البحرين   (Arabic) Mamlakat al-Baḥrayn Flag Coat of arms Anthem:  نشيد البحرين الوطني Bahrainona Our Bahrain Location of   Bahrain    (circled in red) Capital and largest city Manama 26°13′N 50°35′E  /  26.217°N 50.583°E  / 26.217; 50.583 Official languages Arabic Ethnic groups (2010 [1] ) 50.7% Arab (46% Bahrani, 4.7% other Arabs) 45.5% Asian 1% European 1.2% Others Religion Islam Demonym(s) Bahraini Government Unitary constitutional monarchy • King Hamad bin Isa Al Khalifa • Crown Prince Salman bin Hamad bin Isa Al Khalifa • Prime Minister Khalifa bin Salman Al Khalifa Legislature National Assembly • Upper house Consultative Council • Lower house Council of Representatives Independence • Declared Independence [2] 14 August 1971 • from United Kingdom [1] 15 August 1971 • Admitted to the United Nations 21 September 1971 • Kingdom of Bahrain 14 February 2002
Read more

Postfix configuration issue with fips on centos 7; mailgun relay

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I am trying to setup postfix to relay all mail generated on the local machine via SMTP to a mailgun relay. I have used the mailgun relay before with success on an ubuntu server, but I am migrating to a Centos 7 server which I will be running in FIPS mode. There error log is below, slightly sanitized. I have a small enough network that I choose to have each machine reach out to mailgun individually (this the loopback-only, 127.0.0.0/8 restrictions) and no firewall open port allowing smtp in to the machine. I assume the FIPS mode (and with it disabling of MD5) is causing problems, but I don't know how to overcome it or if it is even possible for tls_fprint to use some supported hash such as sha256 or sha512. However, the relay=none is slightly concerning since I have relayhost set, but perhaps that is because the smtp process is failing? Any help would be appreciated! postconf -n: alias_database = hash:/etc/alia
Read more