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 questi...
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
Read more