deja-dup attempts to backup "lost+found"

Bug #953194 reported by Ben Howard on 2012-03-12
56
This bug affects 12 people
Affects Status Importance Assigned to Milestone
Déjà Dup
Medium
Unassigned
deja-dup (Ubuntu)
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)

Ben Howard (utlemming) wrote :
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
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
AdlerHorst (adlerhorst) wrote :

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

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) on 2012-09-26
Changed in deja-dup (Ubuntu):
status: Expired → New
Launchpad Janitor (janitor) wrote :

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

Changed in deja-dup (Ubuntu):
status: New → Confirmed
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.

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.

Mikko Ruohola (polarfox) wrote :

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

Vej (vej) on 2017-10-10
Changed in deja-dup (Ubuntu):
importance: Undecided → Low
Changed in deja-dup:
importance: Undecided → Medium
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers