rsync from remote host "failed: No space left on device (28)" even with --inplace

[Adam Funk]

On 2024-11-07, Ian Bruntlett wrote:

> Hi
>
> On Thu, 7 Nov 2024 at 18:10, Nils Kassube via ubuntu-users <
> ubuntu-users at lists.ubuntu.com> wrote:
>
>> On 07.11.24 Adam Funk wrote:
>> > I'm trying to copy a lot of data from a high-performance computing
>> > server to a USB hard drive.
>>
><snip>
>
>> > I added the --inplace option after googling the error message, but
>> > it's still producing the same error. I assume the inode 0 count is
>> > because the drive is formatted in fat32.
>> >
>> > Is the drive format the problem?
>>
>> Yes, maybe FAT32 is the culprit - at least it is the reason for the inode
>> count of 0. Remember the max. file size for FAT32 is 4 GiB, so maybe you
>> just can't copy a huge file. OTOH, I'm not familiar with rsync problems
>> though, so maybe there is another reason.
>>
>
> I am not familiar with rsync. I am very familiar with putting large files
> on both USB hard drives and USB memory sticks.
>
> The advantage of FAT32 is it can be read by more systems than an ext4 drive
> can.
>
> The advantage of having an ext4 drive is that big files are not a problem.
>
> However, there is something to be aware of with ext4 partitions. Simply
> put, they reserve a certain number of blocks for superuser use. Those
> parameters can be viewed by running the command:
> # tune2fs -l device
> The "reserved blocks count" can be set to 0 with this command
> # tune2fs -r 0 device # best done only on external drives.
> where device is the device name of the ext4 partition.
>
> I tend to find running the df command with the additional "T" parameter
> useful so, if I was you, I'd take a look at the output of @:
> $ df -Th

Some useful tips, thanks.