cp -aRl "/tmp..." returns 256, can't rename "/tmp...", but failure only to one profile

[jtd]

I believe interrupted, encrypted backup occurred at time1 (or disk was full) on profile "Main" backup to "local_USB/2014". I now create space on local_USB, delete encrypted failure based on date from local_USB/2014/..., restart computer to flush /tmp, and try "Main" backup again at time2.

Each new backup to local_USB/2014 now returns one warning, lists all "take snapshot," and one error in log:
[I] Create hard-links
[I] cp -aRl "/tmp...last success"* "/tmp...new_folder"
[I] returns 256
[I] Take snapshot(... )
...
[E] Can't rename "/tmp...new_folder" to "/tmp...new success with new data"

However, a new, encrypted backup to local_USB/2015 (change "Main" profile to point to different folder on same local USB) does not have the above problems.

I would like to continue to add incremental backups to local_USB/2014 if there is a way. It needs to forget something I think. It cannot be hard-links failure because I tested for identical inodes on local_USB and local_USB/2015 does not return 256.

Thanks, any help will be appreciated!

[Germar (germar)]

Sounds like insufficient permissions. Please make sure your user has full permissions (rwx) for the folder backintime/<HOST>/<USER>/<PROFILE_ID>

If this doesn't help please run the 'cp -aRl' command reported after 'Create hard-links' manually to see why this failed.

[jtd (jtdjtdjtd-business)]

BIT user is root, owner of /tmp/backintime/root/<folder #1>/backintime/<HOST>/root/<PROFILE_ID> is "Me" (<username> instead of root) and permissions are drwx------.

Manual command: sudo cp -aRl "/tmp/backintime/root/<folder #1>/backintime/<HOST>/root/<PROFILE_ID>/<LAST DATE>/backup/"* "/tmp/backintime/root/<folder #1>/backintime/<HOST>/root/<PROFILE_ID>/new_snapshot/backup/"
cp: cannot stat ...: No such file or directory

The <folder #1> in the /tmp/backintime/root folder is actually a "Link to folder" named <folder #2>. I renamed the folder to <folder #1>, same error message (No such file or directory).

That "Link to folder" points to a folder containing my snapshots including a "new_snapshot" folder from the date of the original backup failure. I did sudo rm -Rf /tmp/.../new_snapshot on the true folder rather than hard-link. This removed all but one file. I then shut down BIT, removed newest encrypted folder from local_USB/2014, restarted BIT and "new_snapshot" folder was gone! Although I had removed newest encrypted folder from local_USB/2014 multiple times in past, this is first time "new_snapshot" fully removed!

Nonetheless, I tried to run BIT and it failed again.

[Germar (germar)]

Oh, sorry, I forgot to tell you, you need to create the new_snapshot/backup folders manually before. So please try again with

sudo mkdir -p /tmp/backintime/root/<folder #1>/backintime/<HOST>/root/<PROFILE_ID>/new_snapshot/backup/
sudo cp -aRl "/tmp/backintime/root/<folder #1>/backintime/<HOST>/root/<PROFILE_ID>/<LAST DATE>/backup/"* "/tmp/backintime/root/<folder #1>/backintime/<HOST>/root/<PROFILE_ID>/new_snapshot/backup/"

The folder shouldn't be owned by "Me". Root should be the owner if you run BIT as root. Please correct this with:

sudo chown root:root -R /tmp/backintime/root/<folder #1>/backintime/<HOST>/root

[Launchpad Janitor (janitor)]

[Expired for Back In Time because there has been no activity for 60 days.]