uutils / uutils/coreutils

"split --number 2 <file>" fails when provided with large file.

Open
#10,250 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

U - split
Dominant language
Rust
Stars
24.1k
Forks
2k
Avg merge
1d 5h
Merged PRs (30d)
365

Description

Operating system: Ubuntu 25.10, up-to-date.
Package: Ubuntu coreutils-from-uutils package.

Task: Provided split with a 75.1Gb tar archive to split into two.

Expected behavior: Create xaa with the first 37.6Gb, then create xab with the last 37.6Gb.
What happened: Created both xaa and xab at once, both with 0 bytes, followed by GNOME force-stopping Ptyxis because it was using too much memory.

Comparison to GNU coreutils behaviour: GNU coreutils' split does the job as expected.
Additional tests: When provided with a small file (e.g a "Hello, World!" text file), the command executes with no problem.

uutils split version on the system: 0.2.2

thedreamer123@thedreamer123 /files> ls -lh
total 70G
-rw-rw-r-- 1 thedreamer123 thedreamer123 70G Jan 14 19:33 data.tar
-rw-rw-r-- 1 thedreamer123 thedreamer123   0 Jan 14 20:48 xaa
-rw-rw-r-- 1 thedreamer123 thedreamer123   0 Jan 14 20:48 xab
Error obtained after execution

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the split command entry point and reproduce the issue using split --number 2 data.tar on a large file, comparing the result with a small input. Investigate why the large-file case creates empty outputs and consumes excessive memory. Done means splitting the archive produces two correctly sized output files without excessive memory use, while the existing small-file behavior remains intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.