Re: csplit reports No space left on device

[Mike Jonkmans]

On Thu, Aug 18, 2022 at 07:19:38PM +0100, Pádraig Brady wrote:
> On 18/08/2022 17:53, Rodolfo Aramayo wrote:
> > The result of df -T is:
> > Type       1K-blocks       Used   Available Use% Mounted on
> > ext4        60782776   10993500    49772892  19% /
> > ext4     10401954720 4945781880  4931868456  51% /media/volume/sdb
> > 
> > I am able to create more files in the same directory and in any other 
> > directory on that drive
> 
> Interesting.
> 
> > 
> > And again, the result of the df -i is:
> > 
> > Inodes     IUsed     IFree      IUse%   Mounted on
> >    7741440    312627    7428813  5%      /
> > 327680000  23300224  304379776  8%      /media/volume/sdb
> > 
> > I do not see any evidence of having run out of inodes on 
> > '/media/volume/sdb' where the process was run
> > Unless csplit requires the 'root' partition inodes??
> 
> I'm fairly sure the issue is not in csplit,
> as it's just doing open(), write(), close().
> 
> I would do an `ef2sck -f` on the unmounted file system if possible.
> 
> I would do the run on another (file) system if possible.
> 
> cheers,
> Pádraig.

Maybe run the various df's periodically alongside in another terminal.
So you can see what grows.

You could use 'watch' for that or write a simple script.

Include a 'date' command in this. And also put a 'date' after the csplit.
This might help correlate the output.

Include both filesystems in the df's.

Succes!

-- 
Regards, Mike Jonkmans
It was all so different before everything changed.