[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#26318: csplit
From: |
Pádraig Brady |
Subject: |
bug#26318: csplit |
Date: |
Thu, 30 Mar 2017 22:17:03 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
On 30/03/17 19:05, Murray Collingwood wrote:
> Hello
>
> I just came across 'csplit' and thought all my problems are solved.
>
> I backup a MySQL database using a single mysqldump on the entire database.
> It's large.
> The file (with newlines on each line) is about 11.5GB
>
> I tried the following command:
>
>> csplit 2017-03-31.sql '/^DROP TABLE/' '{*}'
>
>
> It was working really well and then appeared to finish normally.
> It had created xx00 - xx48
>
> However when I started looking through the output files I was missing a
> whole bunch. Table names should range from a* through to w*, however all I
> received was table names a* through to i* - I'm missing the last half of
> the data.
>
> It would appear there is some limit as to the size of the input file the
> csplit will process.
>
> Thanks for all you do - I have been an avid Linux user for over 30 years.
What system are you on?
What version of coreutils?
csplit should support large files if your system does and it was built
appropriately
thanks,
Pádraig
- bug#26318: csplit, Murray Collingwood, 2017/03/31
- bug#26318: csplit,
Pádraig Brady <=
- Message not available