Issue 83 in flyback: Fuse mounted filesystems are missing from backup targets
codesite...@google.com
Owner: ----
New issue 83 by alexanderfaucher: Fuse mounted filesystems are missing from
backup targets
https://code.google.com/p/flyback/issues/detail?id=83
What steps will reproduce the problem?
1. Plug in NTFS drive and let gnome automount
2. Create new backup and try to select the backup target
3. Notice the drive list does not include Fuse partitions
What is the expected output? What do you see instead?
Expected to see the same list of drives that shows up in nautilus. Instead
only ext3 partitions showed up.
What version of the product are you using? On what operating system?
Flyback v0.64 - Ubuntu 9.10 64
Please provide any additional information below.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
codesite...@google.com
Comment #1 on issue 83 by ben.foote: Fuse mounted filesystems are missing
from backup targets
http://code.google.com/p/flyback/issues/detail?id=83
I'm having a similar problem. I have a networked file system mounted via
ftpfs, and
it doesn't show up in the backup list either.
It would probably be helpful to allow people to just choose any folder
available to
them that has the proper permissions instead of restricting the list down,
but thats
just a suggestion.
codesite...@google.com
Comment #2 on issue 83 by specopsadmin: Fuse mounted filesystems are
It isn't the file system that matters (FAT, EXT, etc.). For local disks the
only
qualifier is that Flyback has write permissions at the root of the mount.
So if you
have a USB disk mounted at /media/usbdrive, but you only have write
permission at
/media/usbdrive/myaccount/, Flyback will ignore it.
For network mapped drives, you have to make a connection with GVFS, and you
MUST be
part of the FUSE group in order for an entry to be created in ~/.gvfs. Same
rules
apply as above, you'll need write access to the root of the networked
mount. Once all
that is satisfied, Flyback will allow backups.
This information should be written up a little better and put in to a FAQ,
it would
eliminate a lot of headaches.
It would be much easier for Debian based used to have Flyback read Nautilus
connections.
--
You received this message because you are subscribed to the Google Groups "flyback-discuss" group.
To post to this group, send email to flyback...@googlegroups.com
To unsubscribe from this group, send email to flyback-discu...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/flyback-discuss?hl=en
Project homepage: http://code.google.com/p/flyback/
codesite...@google.com
Comment #3 on issue 83 by lorenzo.milesi: Fuse mounted filesystems are
http://code.google.com/p/flyback/issues/detail?id=83
Tried right now, mounted a SSH share using gnome, cannot see it in flyback.
says no backup target available... it would be great.