[SOLVED]borgbackup extract … fails with 'No space left on device'

keepitsimpleengineer · 2018-01-23 02:09:59

A 201 GB backup for two simple Windows 10 system to a USB drive extract always fails with...

OSError: [Errno 28] No space left on device

All on local system
Source partition:797.6 GB free (USB3)
Cache partition:66.6 GB free (SSD)
Destination partition: 976.6 GB free (HDD)
System memory: 15.6 GB
borg (borgbackup) 1.1.4-1
encryption none
compression zlib,5
python 3.6.4-1

tried this as suggested in Borg Docs:

borg config /run/media/ljohnson/Win10aBU/borgBU additional_free_space 8G

Terminal output from last run at https://pastebin.com/arH7Pjbu

Found nothing in borg mailing list archive

Anybody have any ideas..?

Last edited by keepitsimpleengineer (2018-01-23 21:08:00)

dom0 · 2018-01-23 14:24:24

Is that the only bit of error message or does it give you more details?

seth · 2018-01-23 15:41:20

The message sounds rather clear ... unlike

to a USB drive

Source partition:797.6 GB free (USB3)
Cache partition:66.6 GB free (SSD)
Destination partition: 976.6 GB free (HDD)

Let's see

df -h
lsblk -f

dom0 · 2018-01-23 15:46:08

seth wrote:

The message sounds rather clear ...

Since I wrote approximately half of Borg I'm fairly sure it either gives you a trace back or an error message with some extra detail. Hence I asked (in a friendly manner) to post the entire error message and not just parts of it.

Edit: I didn't see the link to the pastebin containing the full error message before. At least part of this is a bug in Borg's error handling, if you don't mind, please open an issue at https://github.com/borgbackup/borg/issues with your traceback.

It is possible that the root cause is a bug too, since the files in "System Volume Information" may possess some strange properties not handled correctly by Borg. Try to --exclude them and see if that helps.

Last edited by dom0 (2018-01-23 15:55:52)

seth · 2018-01-23 15:50:27

His pastebin contains a trace. I assume he's trying to extract to that "cache" device or onto sth. he lacks write permissions (eg. ntfs, no 3g or so)

keepitsimpleengineer · 2018-01-23 21:06:45

dom0 wrote:

At least part of this is a bug in Borg's error handling, if you don't mind, please open an issue at https://github.com/borgbackup/borg/issues with your traceback.

☝ ☛ https://github.com/borgbackup/borg/issues/3574

keepitsimpleengineer · 2018-01-23 21:15:51

Thanks for all the help.

Adding a few hundred GBs to ~/.cache/borg allowed the job to complete w/o the "No space left on device" message.

Arch Linux

#1 2018-01-23 02:09:59

[SOLVED]borgbackup extract … fails with 'No space left on device'

#2 2018-01-23 14:24:24

Re: [SOLVED]borgbackup extract … fails with 'No space left on device'

#3 2018-01-23 15:41:20

Re: [SOLVED]borgbackup extract … fails with 'No space left on device'

#4 2018-01-23 15:46:08

Re: [SOLVED]borgbackup extract … fails with 'No space left on device'

#5 2018-01-23 15:50:27

Re: [SOLVED]borgbackup extract … fails with 'No space left on device'

#6 2018-01-23 21:06:45

Re: [SOLVED]borgbackup extract … fails with 'No space left on device'

#7 2018-01-23 21:15:51

Re: [SOLVED]borgbackup extract … fails with 'No space left on device'

Board footer