search for: guestfs_umount_local

| 08:49 < oberonc> hi | 08:49 < oberonc> I have a problem with libguesfs 1.20.6 | 08:50 < oberonc> on fedora 18 | 08:50 < oberonc> with fuse 2.9.2 | 08:50 < oberonc> when I call guestfs_umount_local() I get the following | error: | 08:50 < oberonc> libguestfs: error: umount_local: unknown option | 1069642336 (this can happen if a program is compiled | against a newer version of libguestfs, then | dynamically linked to an...

...in program. > > Rich. > Thank you very much! I've rewritten this script in C, and it works just as expected. The only problem is that for unmount, we cannot reuse the same handle, and have to call guestunmount. There's a dim place: what is the difference between guestunmount and guestfs_umount_local? As I understood, guestunmount does need guestfs handle, launch etc. Does umount_local need it? If yes, how should this command be used (assumed that the handle is already used in mount_local_run)? These questions confuse me a little :-s -- Your sincerely, Maxim Perevedentsev

[These two patches are for discussion only] Allow FUSE support to be used directly through the API. This is the second commit. In order to make this usable from guestfish, we have to also bind the events API in guestfish. This is the first commit. Rich.

...(EXIT_SUCCESS); + } + + const char *dir = argv[optind]; + char system_arg[BUFSIZ]; + sprintf (system_arg, "diff -urN %s%s %s%s", stempdir, dir, + dtempdir, dir); + sleep (5); + if (system (system_arg) == -1) + exit (EXIT_FAILURE); + + guestfs_umount_local (sg, GUESTFS_UMOUNT_LOCAL_RETRY, 1, -1); + waitpid (spid, NULL, 0); + guestfs_umount_local (dg, GUESTFS_UMOUNT_LOCAL_RETRY, 1, -1); + waitpid (dpid, NULL, 0); + + if (guestfs_shutdown (sg) == -1) + exit (EXIT_FAILURE); + if (guestfs_shutdown (dg) == -1) + exit (EXIT_FAILURE); + + free_d...

From: Maros Zatko <mzatko@redhat.com> Patch adds recursive mutex around C calls, which tries to fix potential race condition in guestfs_umount_local (see [1]). [1] - https://bugzilla.redhat.com/show_bug.cgi?id=917706 Maros Zatko (1): generator: c.ml - wrap non deamon function with recursive mutex generator/c.ml | 12 ++++++++++++ 1 file changed, 12 insertions(+) -- 1.8.5.3

The existing mechanism was clunky, slow and used ~ 10 MB of local disk. Rich.

Hello everyone! I have to implement the functionality of mounting all VM disks/partitions. E.g. if a VM has 2 disks of 2 partitions each (I get it from virt-filesystems), I want to get the following structure on host node after mount: mnt/ ------hdd0/ -------------volume1/ -------------volume2/ ------hdd1/ -------------volume1/ -------------volume2/ I'd like to use guestmount due to

This patch is just for review. It enables FUSE support in the API via two new calls, 'guestfs_mount_local' and 'guestfs_umount_local'. FUSE turns out to be very easy to deadlock (necessitating that the machine be rebooted). Running the test from the third patch is usually an effective way to demonstrate this. However I have not yet managed to produce a simple reproducer that can be reported upstream and/or understand the...

...on as suggested to the guestmount program, but it tended to make the guestmount program more complex. More importantly, adding the option only to guestmount means that it cannot be used outside guestmount, specifically by programs that use the mount-local API[1] directly. (For various reasons 'guestfs_umount_local' isn't a usable API in most situations). My second implementation is the patch attached. It adds a new program called guestmount-cleanup which can be used two ways: guestmount-cleanup --fd=<FD> mountpoint where it will monitor the pipe file descriptor <FD>. (I should note...

This version doesn't crash or cause hung processes or stuck mountpoints, so that's an improvement. Rich.

This changes the proposed API slightly. Previously 'mount-local' generating a 'mounted' event when the filesystem was ready, and from the 'mounted' event you had to effectively do a fork. Now, 'mount-local' just initializes the mountpoint and you have to call 'mount-local-run' to enter the FUSE main loop. Between these calls you can do a fork or whatever