Reference 1 http://www.cs.nmsu.edu/~pfeiffer/fuse-tutorial/html/running.html
Reference 2 http://www.maastaar.net/fuse/linux/filesystem/c/2016/05/21/writing-a-simple-filesystem-using-fuse/
According to the reference one, you can successfully compile and mount the file system, the corresponding operation log will respond.
According to reference 2, can be compiled successfully, but mount when the deadlock occurs, if more than one parameter, then appears use:invalid argument ' y ' (Y is the second folder)
Copy the source code of reference 2 to the bbfs.c of reference one, which can be compiled successfully, but the same on Mount.
The initial inventory Reference 2 issue is not a compilation issue, but a problem with the code.
Will refer to one of the main functions of Fuse_main (ARGC, argv, &bb_oper, Bb_data); The bb_data in is changed to NULL, the mount cannot be seen through DF-HL, but the others are normal, fusermount-u can also be unloaded normally.
------can actually be seen, just in the first line, inconspicuous:
DF:/home/mei/fuse-tutorial-2016-03-25/x: Transport endpoint is not connected
Later found that reference 2 normal, no card dead, but DF can not see the mount point, but normal unloading. In fact, the Fuse_main function only needs a folder parameter.
The card-dead phenomenon only occurs when the-f parameter is added. This parameter allows the printf function to print.
In fact, is not stuck, is the Guardian process, refer to Http://stackoverflow.com/questions/30380849/why-does-fuse-seem-to-be-locking-up-all-threads
In another window, operate the mounted folder, you can see the corresponding output
Getting Started with fuse