[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#17904: issue with split command
From: |
jayaprakash.vambara |
Subject: |
bug#17904: issue with split command |
Date: |
Wed, 9 Jul 2014 14:46:49 +0000 |
Hi All,
After some investigation, I found that inspite of me giving a size
specification as +1000, it is taking 500 as default and in this due course, it
has deleted some files which were over 500KB.
I am able to resolve the issue now.
Thank You,
V. Jayaprakash
-----Original Message-----
From: Bernhard Voelker [mailto:address@hidden
Sent: 03 July 2014 08:13
To: Vambara, Jayaprakash; address@hidden
Subject: Re: bug#17904: issue with split command
tags 17904 + moreinfo
stop
On 07/02/2014 11:16 PM, address@hidden wrote:
> Hello,
>
> I am using split command to split a large file and later I am renaming file.
> PFB command.
>
> find . -size +1000 -exec split -l 10000 {\} {}-new \; find . -type f
> -name "*new*" -exec mv "{}" "{}".list \;
>
> However, this is giving correct result sometimes and other times :
> while creating files, the file with name ending newaa is missing
> .(This would be the first file output while splitting)
Thanks for the bug report.
However, TBH I don't see a problem here (... other than later file names
possibly clashing the earlier produced "*new*" files; I reported that to the
main coreutils list separately).
> For ex:
> If I split a file named "sample" of size 1100 KB and with 25000 lines. If I
> run the above query:
>
> Sometimes the result is:
Can you please explain what you mean by "sometimes" here?
Is this related to certain files (where you could reproduce with a standalone
"split -l 10000 file file-new" run)?
> Samplenewaa.list
> Samplenewab.list
> Samplenewac.list
>
> But other times,only:
> Samplenewab.list
> Samplenewac.list
>
> Can you please look into this and let me know if this is a bug or if I am
> doing something wrong.
>
> Thank You,
Can you please try to narrow the test case down to the file where the "aa" file
is missing? Both split(1) and mv(1) have the --verbose option which could help
finding the cause.
Thanks & have a nice day,
Berny