Re: [Gluster-devel] Problem with rm -rf

[Harris Landgarten]

This bug is easily reproduced by copying the Linux source tree to gluster and 
then trying to remove it with rm -rf 

Harris

----- Original Message -----
From: "Majied Najjar" <address@hidden>
To: "Harris Landgarten" <address@hidden>
Cc: "gluster-devel" <address@hidden>
Sent: Friday, June 29, 2007 4:01:09 PM (GMT-0500) America/New_York
Subject: Re: [Gluster-devel] Problem with rm -rf

I have some core file outputs for the same operations:

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Core was generated by `[glusterfsd]                                             
                     '.
Program terminated with signal 11, Segmentation fault.
#0  0xb7e50639 in ?? ()
(gdb) bt
#0  0xb7e50639 in ?? ()

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Core was generated by `[glusterfsd]                                             
                     '.
Program terminated with signal 11, Segmentation fault.
#0  0xb7e92639 in ?? ()
(gdb) bt
#0  0xb7e92639 in ?? ()

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Core was generated by `[glusterfs]                                           '.
Program terminated with signal 11, Segmentation fault.
#0  0xffffe410 in __kernel_vsyscall ()
(gdb) bt
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7f0aa8d in ?? ()


On Fri, 29 Jun 2007 13:36:27 -0400 (EDT)
Harris Landgarten <address@hidden> wrote:

> Avati,
> 
> More info on rm -rf problem
> 
> rm -rf * and find . -exec rm -rf {} \;
> 
> both begin properly and then fall into a sequence of looking for files:
> 
> find . -type f -exec rm {} \;
> 
> works fast and properly
> 
> rm -rf * then works with empty dirs.
> 
> Harris
> 
> 
> 
> 
> ----- Original Message -----
> From: "Harris Landgarten" <address@hidden>
> To: "Anand Avati" <address@hidden>
> Cc: "gluster-devel" <address@hidden>
> Sent: Thursday, June 28, 2007 9:21:46 AM (GMT-0500) America/New_York
> Subject: Re: [Gluster-devel] Problem with rm -rf
> 
> the rm -rf hangs. It looks like one or two unlinks are sent to the log. I can 
> cntl-C the client and the data is still there. The data was is the tmp dir 
> from failed backups. It is gone now. I will investigate more when I have more 
> data later today.
> 
> Harris
> 
> ----- Original Message -----
> From: "Anand Avati" <address@hidden>
> To: "Harris Landgarten" <address@hidden>
> Cc: "gluster-devel" <address@hidden>
> Sent: Thursday, June 28, 2007 9:17:41 AM (GMT-0500) America/New_York
> Subject: Re: [Gluster-devel] Problem with rm -rf
> 
> Strange, 
> what is your configuration? At the time of 'hang', is it possible for you to 
> attach gdb to glusterfs and get a backtrace (from every thread, by switching 
> as 'thr 1' 'thr 2' etc) ? 
> rm -rf seems to work fine for me, wondering how find . -exec rm would make a 
> difference. 
> thanks, 
> avati 
> 
> > I am trying to delete the contents of a tmp dir with 3 trees containing 
> > about 1.7G 
> > as root, from withint the top level tmp dir I issue 
> > 
> > rm -rf * 
> > 
> > and the command hangs are never returns. 
> > 
> > find . -exec rm -rf {} \; 
> > 
> > works as expected. 
> > 
> > 
> > Harris 
> 
> 
> 
> 
> _______________________________________________ 
> Gluster-devel mailing list 
> address@hidden 
> http://lists.nongnu.org/mailman/listinfo/gluster-devel 
> 
> 
> -- 
> Anand V. Avati 
> 
> 
> _______________________________________________
> Gluster-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/gluster-devel
> 
> 
> 
> _______________________________________________
> Gluster-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/gluster-devel