deja-dup attempts to backup "lost+found"

Bug #953194 reported by Ben Howard
66
This bug affects 15 people
Affects Status Importance Assigned to Milestone
Déjà Dup
Fix Released
Medium
Unassigned
deja-dup (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Deja-Dup attempts to backup */lost+found when it is present in one of the backup directories even if it is included in the exclusion list.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: deja-dup 21.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Mon Mar 12 11:02:45 2012
EcryptfsInUse: Yes
SourcePackage: deja-dup
UpgradeStatus: Upgraded to precise on 2012-01-09 (63 days ago)

Revision history for this message
Ben Howard (darkmuggle-deactivatedaccount) wrote :
Revision history for this message
Michael Terry (mterry) wrote :

I can't reproduce this. I did a test with:

Layout:
/tmp/ddtest/source/hello
/tmp/ddtest/source/lost+found

Included:
/tmp/ddtest/source

Excluded:
/tmp/ddtest/source/lost+found

After a backup & restore, only hello was backed up and restored, as I would expect.

Can you give more info about your setup, so I can try and reproduce?

Changed in deja-dup (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for deja-dup (Ubuntu) because there has been no activity for 60 days.]

Changed in deja-dup (Ubuntu):
status: Incomplete → Expired
Revision history for this message
AdlerHorst (adlerhorst) wrote :

This dialog I get after every Backup. And I excluded this directories.

Revision history for this message
gpagnon (gpagnoni) wrote :

I have exactly the same problem, with the file "/media/DATA/lost+found" is on a mounted hard drive. As the previous poster, I excluded this file from the back up list but to no avail.

thanks for any suggestions

gpagnon (gpagnoni)
Changed in deja-dup (Ubuntu):
status: Expired → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in deja-dup (Ubuntu):
status: New → Confirmed
Revision history for this message
Nick Fenwick (neek-w) wrote :

This affects me too, though I'm not on Ubuntu this is the only bug report I could find for this issue. Added /mydocs to the backup list. In the past I have had this mounted as an external NTFS partition and accessed from Linux and Windows systems, but it's currently the same set of files copied into a root directory on my filesystem. So, it seems the lost+found directory isn't useful in my situation, yet it still causes an error report during the backup. The backup does seem to proceed normally, I got a 52Gb backup with this one message about /mydocs/lost+found output at the end.

neek@uberneek ~$ mount | grep mydocs
neek@uberneek ~$ ls -ld /mydocs
drwxr-xr-x. 23 neek neek 4096 Apr 17 10:10 /mydocs
neek@uberneek ~$ ls -ld /mydocs/lost+found/
drwx------. 2 root root 4096 Jun 10 2011 /mydocs/lost+found/

Added /mydocs to the inclusion list and /mydocs/lost+found to the exclusion list using the "Backup" frontend in Fedora 18.

deja-dup-26.0-1.fc18.x86_64

I have to presume dejadup is scanning the root dir of a directory in the list of included locations without considering the exclusion list, which is only used later when doing a deep scan for files to actually backup. My user 'neek' cannot read or list the lost+found directory so the scan fails.

Revision history for this message
Brian Thompson (briankt) wrote :

Confirming.
Ubuntu 12.04
Folders to back up
/media/MyData
Folders to ignore
/media/MyData/lost+found

Window with message pops up daily.

Revision history for this message
Mikko Ruohola (polarfox) wrote :

Mounted $HOME/tmp ext4 produces this even if path is excluded.

Vej (vej)
Changed in deja-dup (Ubuntu):
importance: Undecided → Low
Changed in deja-dup:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Michael Terry (mterry) wrote :

OK, I *finally* got around to fixing this.

Fix should be released with version 42.3.
https://gitlab.gnome.org/World/deja-dup/-/commit/791acc6fdbe42d6851ecf64ad29ee41ce6ed0d58

Changed in deja-dup:
status: Confirmed → Fix Committed
Changed in deja-dup (Ubuntu):
status: Confirmed → Fix Committed
Michael Terry (mterry)
Changed in deja-dup:
status: Fix Committed → Fix Released
Michael Terry (mterry)
Changed in deja-dup (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.