beaglefs doesn't work

Bug #282410 reported by Luigi Maselli
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
beaglefs (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: beaglefs

$ beagle-query png
[a lot of results]

but with beaglefs I get an empty directory mounted

$ beaglefs png search/ -d
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56
INIT: 7.9
flags=0x0000002b
max_readahead=0x00020000
   INIT: 7.8
   flags=0x00000000
   max_readahead=0x00020000
   max_write=0x00020000
   unique: 1, error: 0 (Success), outsize: 40
unique: 2, opcode: OPENDIR (27), nodeid: 1, insize: 48
   unique: 2, error: 0 (Success), outsize: 32
unique: 3, opcode: GETATTR (3), nodeid: 1, insize: 56
   unique: 3, error: 0 (Success), outsize: 112
unique: 4, opcode: READDIR (28), nodeid: 1, insize: 80
   unique: 4, error: 0 (Success), outsize: 80
unique: 5, opcode: READDIR (28), nodeid: 1, insize: 80
   unique: 5, error: 0 (Success), outsize: 16
unique: 6, opcode: RELEASEDIR (29), nodeid: 1, insize: 64
   unique: 6, error: 0 (Success), outsize: 16
unique: 7, opcode: OPENDIR (27), nodeid: 1, insize: 48
   unique: 7, error: 0 (Success), outsize: 32
unique: 8, opcode: GETATTR (3), nodeid: 1, insize: 56
   unique: 8, error: 0 (Success), outsize: 112
unique: 9, opcode: READDIR (28), nodeid: 1, insize: 80
   unique: 9, error: 0 (Success), outsize: 80
unique: 10, opcode: READDIR (28), nodeid: 1, insize: 80
   unique: 10, error: 0 (Success), outsize: 16
unique: 11, opcode: RELEASEDIR (29), nodeid: 1, insize: 64
   unique: 11, error: 0 (Success), outsize: 16
unique: 12, opcode: OPENDIR (27), nodeid: 1, insize: 48
   unique: 12, error: 0 (Success), outsize: 32
unique: 13, opcode: GETATTR (3), nodeid: 1, insize: 56
   unique: 13, error: 0 (Success), outsize: 112
unique: 14, opcode: READDIR (28), nodeid: 1, insize: 80
   unique: 14, error: 0 (Success), outsize: 80
unique: 15, opcode: READDIR (28), nodeid: 1, insize: 80
   unique: 15, error: 0 (Success), outsize: 16
unique: 16, opcode: RELEASEDIR (29), nodeid: 1, insize: 64
   unique: 16, error: 0 (Success), outsize: 16
unique: 17, opcode: OPENDIR (27), nodeid: 1, insize: 48
   unique: 17, error: 0 (Success), outsize: 32
unique: 18, opcode: GETATTR (3), nodeid: 1, insize: 56
   unique: 18, error: 0 (Success), outsize: 112
unique: 19, opcode: READDIR (28), nodeid: 1, insize: 80
   unique: 19, error: 0 (Success), outsize: 80
unique: 20, opcode: READDIR (28), nodeid: 1, insize: 80
   unique: 20, error: 0 (Success), outsize: 16
unique: 21, opcode: RELEASEDIR (29), nodeid: 1, insize: 64
   unique: 21, error: 0 (Success), outsize: 16
unique: 22, opcode: OPENDIR (27), nodeid: 1, insize: 48
   unique: 22, error: 0 (Success), outsize: 32
unique: 23, opcode: GETATTR (3), nodeid: 1, insize: 56
   unique: 23, error: 0 (Success), outsize: 112
unique: 24, opcode: READDIR (28), nodeid: 1, insize: 80
   unique: 24, error: 0 (Success), outsize: 80
unique: 25, opcode: READDIR (28), nodeid: 1, insize: 80
   unique: 25, error: 0 (Success), outsize: 16

Revision history for this message
Guiodic (Guido Iodice) (guido-iodice) wrote :

I confirm the issue.

Changed in beaglefs (Ubuntu):
status: New → Confirmed
Revision history for this message
Guiodic (Guido Iodice) (guido-iodice) wrote :

I solved. It is a bug caused by new beagle syntax.

Please makes changes in attached files (excuse me, I'm unable to use diff properly)

Revision history for this message
lunomad (damon-metapaso) wrote :

Hi Guiodic,

I built beaglefs with your hit.c on Karmic, but still no luck -- filesystems mount blank.

I saw your blog. I'd love to get your GUI to work on my system too...what can I do to get beaglefs to work?

Revision history for this message
Guiodic (Guido Iodice) (guido-iodice) wrote :

Are you sure you used new compiled beaglefs?

Try this:

1) remove all beaglefs old version
2) download http://www.megaupload.com/?d=B2Z0HZTP in your home folder
3) sudo cp beaglefs /sbin
4) sudo chmod a+x /sbin/beaglefs

Revision history for this message
lunomad (damon-metapaso) wrote :

Thanks for the link,

I built it from deb-src, replacing the original hit.c with your hit.c, then installing the resulting .deb file.

Is your binary AMD64? I'd much rather have the source than a pre-compiled binary.

D

Revision history for this message
lunomad (damon-metapaso) wrote :

I tried your binary, but I get library errors (I suspect yours is 32-bit)?

~$ ./beaglefs "damon" ~/Recent/
./beaglefs: error while loading shared libraries: libfuse.so.2: cannot open shared object file: No such file or directory

I'm sad because I was very much hoping to use dates to be make a real "recent file list" that includes all recently changed files, but no luck.

Revision history for this message
David Futcher (bobbo) wrote :

Can anyone confirm whether on not the patch attached above actually works? If it does then we can send this upstream and get it fixed.

Marking as patch-needswork based on comment #3.

tags: added: patch-needswork
Revision history for this message
lunomad (damon-metapaso) wrote :

I'm not enough of a real programmer to see or validate what's going on here, but it didn't work for me. It's been awhile but I recall thinking at the time that the patch addressed some beagle syntax changes that were subsequently changed again, so the patch didn't work.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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