From: Stas O. <sta...@gm...> - 2011-06-27 23:10:26
|
This appears when mounting manually: fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option error in fuse_mount But the mounting still succeeds, and I can browse files on cluster. Any idea if this related? On Mon, Jun 27, 2011 at 10:48 PM, Stas Oskin <sta...@gm...> wrote: > This is the backtrace: > > #0 0x0000003cd8a30265 in raise () from /lib64/libc.so.6 > #1 0x0000003cd8a31d10 in abort () from /lib64/libc.so.6 > #2 0x0000003cd8a6a84b in __libc_message () from /lib64/libc.so.6 > #3 0x0000003cd8a7230f in _int_free () from /lib64/libc.so.6 > #4 0x0000003cd8a7276b in free () from /lib64/libc.so.6 > #5 0x000000000040eaba in fuse_reply_entry () > #6 0x00000000004121c9 in fuse_reply_entry () > #7 0x0000000000412580 in fuse_reply_entry () > #8 0x0000003cd8a1d994 in __libc_start_main () from /lib64/libc.so.6 > #9 0x0000000000402519 in fuse_reply_entry () > #10 0x00007fff48cb59d8 in ?? () > #11 0x0000000000000000 in ?? () > (gdb) > > On Mon, Jun 27, 2011 at 10:41 PM, Stas Oskin <sta...@gm...> wrote: > >> Hi. >> >> We found an issue where mfsmount, when mounted via the autofs script, is >> segfaults. >> >> 1) Is this a known issue? >> >> 2) What are other alternatives of mounting mfsmount? >> >> Thanks! >> > > |