Error when backing up. Error: rsync: [generator] chgrp "..." failed: Invalid argument (22) #1373
Assignees
Comments
|
Dear @mdjojm , thank you for your report. I have an idea what the problem could be. Before you try something please explain to us ""reinstalled and compiled from source". Which distribution you are using? Please try this commands and show us the output. Maybe not all of them will work. Don't worry.
Depending on your error my assumption is you are using BIT 1.3.2 or earlier with rsync 2.3.4 or newer. If that is the case you can use a workaround. Look in the Expert Options of your snapshot and add The background of your problem is described in |
buhtz
added
Bug
Feedback
buhtz
changed the title
This could be shell globbing issue (eg. @mdjojm Please also show us the output of
Edit: The output |
I cloned the GitHub repo.
I am using linux Mint Cinnamon version 5.4.12.
WARNING: Failed to connect to Udev serviceHelper daemon via D-Bus: org.freedesktop.DBus.Error.Spawn.ChildExited
backintime 1.3.3-dev
rsync version 3.2.3 protocol version 31
|
|
Thanks for your report. What type of snapshot profile is this?
If you can reproduce the problem, please start After that I would ask if you could install the last stable release EDIT:
A shot into the blue |
I think this is not the root problem here since it affects only |
|
Regarding
I assume that the installation from Github is correct (configure/make/make install) for both Q1: What does the The best guess so far is missing dependencies (we had some undocumented dependencies in the past). Q2: Co could you please check if all of the documented packages are installed and check if the warning still appears with https://github.com/bit-team/backintime#from-sources esp. the D-Bus-relevant ones
|
I have it as local at the moment
DEBUG: [common/backintime.py:589 argParse] Arguments: {'debug': True} | unknownArgs: [] Back In Time Back In Time comes with ABSOLUTELY NO WARRANTY.
It is a couple of months old I dont remember if I made a new one identical to this one on the fresh install.
I am copying off of an ipod that has been flashed with rockbox but I have tried off of my base linux ssd with the same errors. The destination is a nas that I have running with truenas installed mounted with nfs to my linux install.
To mount my ipod I just plug it in I dont have a manual way to mount it but my nas is manually mounted through the terminal using nfs.
I will be trying to rename it for the next while and see if that works I will report back if it does. |
|
After renaming my ipod to |
I am busy going through them although with chron-daemon I am getting this install error I am not sure which one to choose.
|
Please ignore this dependency, you have found another documentation bug ;-)
OK, unit tests look good enough so please do just install above two packages if they are missing This should fix the D-Bus warnings... (at least on my Mint 21 VM it works) |
TrueNAS seems to use
Could you please show the mount arguments of your local computer for the TrueNAS (corresponding line in the output of Edit: A good summary about NFS limitations can be found here (incl. some workarounds):
|
I installed them and the warnings are gone, but the errors are still happening. |
IP partially redacted.
It is super weird as I have used BIT many times to back up stuff to my server using NFS. |
This was just a hint. I'm still not sure which direction to go. Can you please try the last stable release |
Me too and it worked very well with BiT. What I wanted to point out is that a) a change TrueNAS NFS settings as well as may cause this problem and it is important to find out what is different now. I stopped using NFS many years ago so I am no specialist here but I will try to find my old internal setup documentation and compare it to your mount attributes... |
I will give it a shot right now. |
How do I choose what version to install? |
So I got BIT 1.3.2 from linux Mint's software manager and this is what the debug is showing. |
|
Thanks for that. The error also appears in the latest stable release The second good news are that this further narrows down the possible causes. 😄 You can try to run |
I used cat and got this from /etc/exports
|
You are right after running rsync I had the same issues! |
|
THX for testing v1.3.2, so this is no regression in the current dev version. To rule out (or identify) NFS as problem the simplest way would be to use one file from the error list and
If this throws an error it is a strong indication for a NFS or TrueNAS file system issue... What we didn't discuss so far: It seems to happen only on hidden files starting with a dot in the file name. |
|
So I sent it from my ipod to my ssd and it did it flawlessly. (except for a font file but I have always had issues with that and don't really care lol.) So it is an issue with the nas. |
Folder on nas. Original folder.
Looking back at the errors it seems like there are some files without dots also having issues. |
Perfect, same error message :-) My old nfs settings were using NFS3 not 4, and these settings:
In the exports file on the NAS I had these attributes:
"*squash*" and and the "anon*" attributes were tricky (you have to find out existing group and user id on user NAS) Edit: I guess the group ID for "joe" on your client is different on the NAS (if "joe" exists - anyhow the NAS does not have the group ID so you have to map/translate the group id somehow via the attributes...) |
You said you moved from nfs is there a better system to use? |
Very good question 👍 Not really. I am using CIFS now since the NAS has better UI-support to configure this but I never cared about user rights I created different mounts for different purposes with different access restrictions and backup plans. AFAIR "all or nothing" was the reason to use |
|
I think this is no BiT bug and I leave the issue open until @mdjojm can confirm this (please post the solution here if you find one. THX!) |
|
I will be messing around with the nas until I find a solution and I will keep you guys posted! I love this software as it is the only open source one I have found to reliably work with a nas. |
|
I also use NFS to mount volumes/shares from the NAS (running Debian 11). But with Back In Time I use "SSH snapshot profiles" only. In that case you don't need to take care of mounting. |
Good hint, we should document this as a best practice somewhere |
I will definitely look into this. |
|
I got it working! I messed around with the truenas /Sharing/smb/edit filesystem acl settings changed user, group, and everyone permissions and checked the box under "Apply permissions recursively". I also changed the NFS map all user and group to joe (I made a group and user for joe). I set up smb to my pc which I will probably change to as it uses a password. After doing that and sleeping on it BIT works with smb if I run the root version. |
|
Great to hear it works now!
Did BiT work then with NFS or was all this without success?
SMB is definitely easier but why do you need to run BiT as root (or asked differently: What went wrong when using BiT as normal user)? |
aryoda
removed
the
Feedback
When I run BIT with root then it works with nfs and smb. (Although I am getting some chown errors with nfs right now but as far as I can tell all the files are making their way over.)
As of now for some reason on Linux it isn't giving me write access to my nas using smb just read unless I use root.(It works fine on windows. Not a big problem for me as I don't mind running BIT as root.) |
Have you created a credentials file for the non-root user? Your mount line in The credentials file has a content like this and must be |
Yeah I have
I have tried a lot of things in the fstab file most of them didn't work
So far I have tried.
Just in the terminal not in fstab.
Yep my file does look like that. |
Don't forget to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is the full error
[E] Error: rsync: [generator] chgrp "/mnt/truenas/backups/jojm Backups/ipod backup/backintime/joe-System-Product-Name/joe/2/new_snapshot/backup/media/joe/JOJM'S BASE/.battery_bench.txt.gqpOxS" failed: Invalid argument (22)
It seems to happen with every file in a folder that starts with a ".".
This is weird to me because this has never happened till now I have uninstalled and reinstalled and compiled from source and the problem remains.
I am backing up to my nas running truenas using nfs from my pc running linux Mint Cinnamon version 5.4.12.
The text was updated successfully, but these errors were encountered: