timkatje
commented
6 years ago Additional information:
Since I'm now actually home and doing this in person, I was able to do some physical interventions. So I fully ejected the USB drive from within my QNAP GUI and then rebooted the entire server. Even after a full reboot, and remounting the drive, borg reports the exact same issue when I try to run create again to continue the backup where it left off:
[/share/external/DEV3401_1] # borg create --stats --progress --show-rc --compression auto,lzma,6 media::InitialBackup-2018-07-26 /share/CACHEDEV1_DATA/media/
Enter passphrase for key /share/external/DEV3401_1/media:
Local Exceptionche transaction: Reading chunks
Traceback (most recent call last):
File "borg/archiver.py", line 4312, in main
File "borg/archiver.py", line 4244, in run
File "borg/archiver.py", line 152, in wrapper
File "borg/archiver.py", line 547, in do_create
File "borg/archiver.py", line 511, in create_inner
File "borg/archiver.py", line 621, in _process
File "borg/archiver.py", line 621, in _process
File "borg/archiver.py", line 598, in _process
File "borg/archive.py", line 1028, in process_file
File "borg/archive.py", line 956, in chunk_file
File "borg/archive.py", line 944, in chunk_processor
File "borg/cache.py", line 891, in add_chunk
File "borg/cache.py", line 550, in begin_txn
File "shutil.py", line 241, in copy
File "shutil.py", line 122, in copyfile
File "shutil.py", line 82, in copyfileobj
OSError: [Errno 28] No space left on device
Platform: Linux MemoryAlpha 4.2.8 #1 SMP Tue Jul 10 07:27:26 CST 2018 x86_64
Linux:
Borg: 1.1.6 Python: CPython 3.5.5
PID: 27229 CWD: /share/external/DEV3401_1
sys.argv: ['borg', 'create', '--stats', '--progress', '--show-rc', '--compression', 'auto,lzma,6', 'media::InitialBackup-2018-07-26', '/share/CACHEDEV1_DATA/media/']
SSH_ORIGINAL_COMMAND: None
terminating with error status, rc 2This is also why I've gotten into the habit of just reformatting the entire drive to start over fresh.
ThomasWaldmann
theChaosCoder
bettyvschmartz
Local media share backup of tv shows and movies reports OSError: [Errno 28] No space left on device on 8 TB USB drive.
Have you checked borgbackup docs, FAQ, and open Github issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
ISSUE
System information. For client/server mode post info for both machines.
Linux version 4.2.8 (root@U16BuildServer104) (gcc version 4.9.2 (toolchain config: [gcc-4.9.2 binutils-2.25 glibc-2.21])
Your borg version (borg -V).
1.1.6
Operating system (distribution) and version.
Hardware / network configuration, and filesystems used.
QNAP TS-563 w/ AMD GX-420MC SOC (amd64) and 16 GB RAM running QTS (QNAP's OS) 4.3.4.0644 Build 20180710
Backing up to Seagate Backup+ Hub 8TB via direct connect USB 3.0.
How much data is handled by borg?
~ 5TB, never make it past 600 GB though before backup errors out. Same thing has happened with smaller shares of media that I'm trying to backup, including some sub-TB shares.
Have tried smaller, sub-TB shares, encountered same thing.
Full borg commandline that lead to the problem (leave away excludes and passwords)
borg create --stats --progress --show-rc --compression auto,lzma,6 media::InitialBackup-2018-07-26 /share/CACHEDEV1_DATA/media/
borg info media
Describe the problem you're observing.
I have yet to successfully backup any of my different media shares from my QNAP NAS to a brand new 8 TB USB drive I've attached and mounted (I let QNAP mount it automatically the way that it wants to).
I've formatted the USB drive as EXT4 for best compatibility with my NAS.
At first, I was using the simplest possible commands with very few parameters, but I've since started using more features, like the auto compression.
Once this error occurs, it seems like I cannot use any borg commands, not even borg info to look at what's in the repo, just get the same error. I also don't want a bunch of stagnant data, so I usually just reformat the drive and try again.
When I check on the external device in QNAP management interface, it shows that I'm using 6.42% of my capacity after this failed backup. So it's really surprising to constantly encounter "Out of space" errors.
Once I encounter this, all subsequent borg commands, whether it be borg init to make a new repo, or borg info, reports "Out of space."
Can you reproduce the problem? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
For me, it's as simple as running the basic commands from SSH into my QNAP NAS. Create a repo, select a source share of 500 GB+ and every time it has displayed this issue. This is the furthest I've even gotten a backup of any of my big shares to get.
I originally thought that it might've had something to do with copying my .qpkg (applications) while they were running, so I gave up on backing that share up. My ultimate goal is to just pull all of the media, of all types, from multiple shares in order to redo my RAID configuration as I've reached 80% used capacity in my current array.
Include any warning/errors/backtraces from the system logs
After checking on something in my QNAP GUI, i ran the borg info media command again and received a slightly different output. I was actually about to try manually running the break-lock command, but I guess it attempted to do so automatically this time: