FUSE hanging

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

FUSE hanging

Franco Broi

Seen this same error a few times in the past couple of days, not sure
why it's suddenly starting to happen, nothings changed for yonks.

OS is Red Hat 8, with Linux 2.4.26
FUSE is 2.2.1

(gdb) where
#0  0x420cdb44 in read () from /lib/i686/libc.so.6
#1  0x40049b44 in __JCR_LIST__ () from /lib/i686/libpthread.so.0
#2  0x40035482 in fuse_read_cmd (f=0x804cc28) at fuse.c:1965
#3  0x40035d35 in do_work (data=0x8068470) at fuse_mt.c:61
#4  0x400360ca in fuse_loop_mt_proc (f=0x804cc28, proc=0xfffffe00,
data=0xfffffe00)
    at fuse_mt.c:179
#5  0x40036188 in fuse_loop_mt (f=0x2000) at fuse_mt.c:196
#6  0x40036aff in fuse_main_common (argc=5, argv=0xbffff3a4,
op=0x804c040,
    op_size=124, compat=0) at helper.c:383
#7  0x40036b49 in fuse_main_real (argc=5, argv=0xbffff3a4, op=0x804c040,
op_size=124)
    at helper.c:397
#8  0x0804a9ef in main (argc=5, argv=0xbffff3a4) at squirrel.c:965
#9  0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6

(gdb) p *f
$2 = {flags = 0, fd = 3, op = {getattr = 0x8049620 <sfs_getattr>,
    readlink = 0x804973c <sfs_readlink>, getdir = 0x80497b8
<sfs_getdir>,
    mknod = 0x804988c <sfs_mknod>, mkdir = 0x8049a1c <sfs_mknod+400>,
    unlink = 0x8049a84 <sfs_mkdir+80>, rmdir = 0x8049b14 <sfs_unlink
+120>,
    symlink = 0x8049bc0 <sfs_rmdir+148>, rename = 0x8049c64 <sfs_symlink
+140>,
    link = 0x8049ef8 <sfs_rename+620>, chmod = 0x8049f40 <sfs_link+12>,
    chown = 0x8049fa4 <sfs_chmod+40>, truncate = 0x804a008 <sfs_chown
+40>,
    utime = 0x804a074 <sfs_truncate+48>, open = 0x804a0d8 <sfs_utime
+40>,
    read = 0x804a1a0 <sfs_open+140>, write = 0x804a2c0 <sfs_read+228>,
    statfs = 0x804a32c <sfs_write+48>, flush = 0,
    release = 0x804a528 <sfs_statfs+448>, fsync = 0x804a590 <sfs_release
+44>,
    setxattr = 0, getxattr = 0x804a598 <sfs_release+52>, listxattr = 0,
    removexattr = 0, opendir = 0, readdir = 0, releasedir = 0, fsyncdir
= 0,
    init = 0, destroy = 0}, compat = 0, name_table = 0x804cd20,
  name_table_size = 14057, id_table = 0x805a8c8, id_table_size = 14057,
  ctr = 6018051, generation = 0, hidectr = 0, lock = {__m_reserved = 0,
    __m_count = 0, __m_owner = 0x0, __m_kind = 0, __m_lock = {__status =
0,
      __spinlock = 0}}, worker_lock = {__m_reserved = 0, __m_count = 0,
    __m_owner = 0x0, __m_kind = 0, __m_lock = {__status = 0, __spinlock
= 0}},
  numworker = 10, numavail = 9, exited = 0, got_init = 1, user_data =
0x0,
  major = 7, minor = 1, owner = 201}

fd 3 -> /tmp/.fuse_devKFhV7u/fuse (deleted)




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
fuse-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fuse-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: FUSE hanging

Miklos Szeredi

> Seen this same error a few times in the past couple of days, not sure
> why it's suddenly starting to happen, nothings changed for yonks.
>
> OS is Red Hat 8, with Linux 2.4.26
> FUSE is 2.2.1

The treace is normal:  it's waiting for a command.

What is hanging?  Are there any Oopses in dmesg?

It would be more interesting to see the hanging process' wchan (ps lax),
or better yet it's call trace (SysRq-t, or 'echo t > /proc/sysrq-trigger')

Thanks,
Miklos


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
fuse-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fuse-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: FUSE hanging

Franco Broi
On Thu, 2005-07-21 at 08:38 +0200, Miklos Szeredi wrote:

> The treace is normal:  it's waiting for a command.

>From the kernel module? Other fuse partitions on the same machine are
working fine.

>
> What is hanging?  Are there any Oopses in dmesg?

All the processes currently accessing the FUSE partition hang, plus
anything doing a df, ls etc.

>
> It would be more interesting to see the hanging process' wchan (ps lax),
> or better yet it's call trace (SysRq-t, or 'echo t > /proc/sysrq-trigger')

OK next time it happens I'll be better prepared. When I exited the
debugger and tried to restart it it wouldn't attach (said there was
already a debugger attached) so I killed it.




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
fuse-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fuse-devel
Loading...