If free space is not reported, Deja Dup assumes zero

Ron, I'm assuming that with your samba share that does not report free size, that it just doesn't report it, not that it reports a fake value of 0, right?

If you do:
gvfs-info -f smb://blargblarg

what is the output?

I think I know how to fix this anyway, but just want to cover my bases.

Hi Michael,

I found gvfs-info wasn't installed. When I installed it, and after
manually mounting the location, the command returned as follows:

    ron@sprite:~$ gvfs-info -f smb://ron@mew99/disks/
    attributes:
         filesystem::type: cifs
         gvfs::backend: smb-share

Also after installing gvfs-info, on the chance that it not being
installed might have had something to do with the problem, I re-tried
deja-dup on this target, with the same result as before, as follows:

    Backup location is too small. Try using one with more space.

Thanks.

Regards,
Ron

------------------------------------------------------------------------
* LTi Luminal Technologies, Inc. * * ** *
Ron McKinnon
Solutions Principal Office:
Mobile: (+1) 604.944.4775
(+1) 778.885.3562 Electronic Document
Management Solutions
<email address hidden>
<mailto:<email address hidden>> /
www.luminaltechnologies.com <http://www.luminaltechnologies.com>

On 10-10-09 06:28 PM, Michael Terry wrote:
> Ron, I'm assuming that with your samba share that does not report free
> size, that it just doesn't report it, not that it reports a fake value
> of 0, right?
>
> If you do:
> gvfs-info -f smb://blargblarg
>
> what is the output?
>
> I think I know how to fix this anyway, but just want to cover my bases.
>
> ** Changed in: deja-dup
> Status: New => Incomplete
>
>

OK, great. Then I'm confident I've fixed it. Is this a bog standard samba server, or something special? (Just curious how widespread this problem is.)

This bug was fixed in the package deja-dup - 17.2-0ubuntu1

---------------
deja-dup (17.2-0ubuntu1) natty; urgency=low

  * New upstream release
    - Fix GPG Error during restore (LP: #582720)
    - Fix backing up to devices that don't report free space (LP: #657518)
    - Don't ask for root password if it's not needed (LP: #662884)
  * debian/patches/drop-gconf.patch:
    - Drop unnecessary gconf requirement from configure
 -- Michael Terry <email address hidden> Wed, 17 Nov 2010 22:21:37 -0500

Accepted deja-dup into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Any testers of the maverick-proposed package? As this has been in -proposed for a long time already, I'll remove the proposed package soon if there is no feedback. Thank you!

This works now.

------------------------------------------------------------------------
*LTi Luminal Technologies, Inc. * ****
Ron McKinnon
Solutions Principal Office:
Mobile: (+1) 604.944.4775
(+1) 778.885.3562 Enterprise Content
Management Solutions
<email address hidden>
<mailto:<email address hidden>> /
www.luminaltechnologies.com <http://www.luminaltechnologies.com>

PGP fingerprint: 16FC 5413 9962 7A7F A4A8 144A 866A 2732 4C18 C309

On 11-01-25 01:29 AM, Martin Pitt wrote:
> Any testers of the maverick-proposed package? As this has been in
> -proposed for a long time already, I'll remove the proposed package soon
> if there is no feedback. Thank you!
>

Great. Thanks much and I will download the updated version.

On 2011-01-25, at 12:53 PM, Ron McKinnon wrote:

> This works now.
>
> ------------------------------------------------------------------------
> *LTi Luminal Technologies, Inc. * ****
> Ron McKinnon
> Solutions Principal Office:
> Mobile: (+1) 604.944.4775
> (+1) 778.885.3562 Enterprise Content
> Management Solutions
> <email address hidden>
> <mailto:<email address hidden>> /
> www.luminaltechnologies.com <http://www.luminaltechnologies.com>
>
> PGP fingerprint: 16FC 5413 9962 7A7F A4A8 144A 866A 2732 4C18 C309
>
>
> On 11-01-25 01:29 AM, Martin Pitt wrote:
>> Any testers of the maverick-proposed package? As this has been in
>> -proposed for a long time already, I'll remove the proposed package soon
>> if there is no feedback. Thank you!
>>
>
>
> ** Attachment added: "LTiLogoTexture50.jpg"
> https://bugs.launchpad.net/bugs/657518/+attachment/1806432/+files/LTiLogoTexture50.jpg
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/657518
>
> Title:
> If free space is not reported, Deja Dup assumes zero
>
> Status in Déjà Dup:
> Fix Released
> Status in Déjà Dup 16 series:
> Fix Released
> Status in “deja-dup” package in Ubuntu:
> Fix Released
> Status in “deja-dup” source package in Maverick:
> Fix Committed
>
> Bug description:
> If a filesystem does not report a size, Deja Dup should go ahead and
> try to backup rather than assuming there is no space left.
>
> Thanks to Ron McKinnon for noticing this.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/deja-dup/+bug/657518/+subscribe
>

This bug was fixed in the package deja-dup - 16.1.1-0ubuntu1

---------------
deja-dup (16.1.1-0ubuntu1) maverick-proposed; urgency=low

  * New upstream bug fix release
    - Fix GPG Error during restore (LP: #582720)
    - Fix backing up to devices that don't report free space (LP: #657518)
    - Don't ask for root password if it's not needed (LP: #662884)
 -- Michael Terry <email address hidden> Thu, 18 Nov 2010 07:55:49 -0500

Hi Michael; I have a similar problem, but different enough that your bugfix doesn't cover it.

My networked drive does report a value of available space; it's just an incorrect value (it's always 1GB). I also know for a fact how much space my drive has left, and I can manage the free space by setting deja-dup to only keep copies for a few months (I think). Is there a way to tell it to ignore the reported free space value and perform the backup nonetheless?

Thanks.

Jerry, I would normally ask you to file a new bug, as that is a different engineering problem from this one. This is worth its own discussion, though I'm doubting whether there's much Deja Dup should do in such a situation. To answer your question, there is no current workaround to ignore the free space value.

Hi all,

I am facing a similar problem with version 20.1, on Ubuntu 11.10. I am trying to set a backup on a samba server (I am not sure if it is really a samba server): I am connected to smb://user@IP via windows share in nautilus. Deja-dup beggins the scanning, but reports: Backup location is too small. Try using one with more space.
On Nautilus, the size of the folder is Unkown. I really do not get where is the problem, because this bug should have been fixed since verison 17, right?
Thanks for any help

HI, to correct my previous post. The free space of the primary_folder_to_backup_in is 0 bytes. If i try to backup in a sub-folder (that already exists, and has a free space unkown), deja-dup does not have permission, and do not proceed with the backup (Permission of "folder_to_back_up" could not be determinated). If I ask dejadup to backup in a subfolder that do not exist in the primary folder, dejadup creates the folder, start scanning (current free space = unknown) but later reports: Backup location is too small. Try using one with more space. When I checked this folder_created_by_dejadup again, it reports unkwon status for free space.
Hope that now my problem is clearer,
Thanks