On Thu, 8 Feb 2007 09:30:12 -0600
"Christopher D. Clausen" <[EMAIL PROTECTED]> wrote:

> Davor Ocelic <[EMAIL PROTECTED]> wrote:
> > On Thu, 8 Feb 2007 01:51:49 -0600
> > "Christopher D. Clausen" <[EMAIL PROTECTED]> wrote:
> >
> >> Davor Ocelic <[EMAIL PROTECTED]> wrote:
> >>> On Mon, 5 Feb 2007 11:47:00 -0600
> >>> "Christopher D Clausen" <[EMAIL PROTECTED]> wrote:
> >>>> I think the only way to clear this problem is with a reboot, but
> >>>> feel free to try other things.  I doubt that the openafs client
> >>>> can be stopped though, due to the open file handles and hung ls
> >>>> processes.
> >>>
> >>> Rebooted. Please try again and see if it happens again. If it does,
> >>> reboot yourself to get the system back in usable state, while we
> >>> discuss what do to in that case.
> >>
> >> Can I ask how it was rebooted?  Did the shutdown -r command work as
> >> expected?
> >
> > The 'ls' command didn't block. I ran ls there to check it out myself,
> > and I just got an error "No such device".
> >
> > I just invoked 'sudo reboot' (the way we usually do it) and that was
> > it.
> 
> Ah, ok, cool.  I removed the volume mount point from mire, so I guess it 
> did eventally time out.
> 
> I won't have any free time today to try and break it again.  If someone 
> else wants to try, go for it.  All I did was fs mkm a mountpoint and 
> then tried to mv it to other directory (in the same volume.)

I went to  rm -rf databases.old  and got kernel error as included at the
end of this mail. (I rebooted then to get back to clean state).

So obviously this isn't gonna work. 

Now I've been thinking of two possibilities.

Either we invest more time in getting the afs setup stable, or we
rethink the use of OpenAFS altogether.

What do you folks think?





Message from [EMAIL PROTECTED] at Fri Feb  9 06:50:18 2007 ...
deleuze kernel: EIP: [may_delete+274/288] may_delete+0x112/0x120 SS:ESP 
0068:e6d0df08
Feb  9 06:50:18 deleuze kernel: ------------[ cut here ]------------
Feb  9 06:50:18 deleuze kernel: kernel BUG at fs/namei.c:1381!
Feb  9 06:50:18 deleuze kernel: invalid opcode: 0000 [#1]
Feb  9 06:50:18 deleuze kernel: SMP 
Feb  9 06:50:18 deleuze kernel: Modules linked in: openafs ipv6 ipmi_devintf 
ipmi_si ipmi_msghandler generic shpchp pci_hotplug ehci_hcd usbcore piix e1000 
ext3 jbd ide_disk ide_cd cdrom ide_core unix
Feb  9 06:50:18 deleuze kernel: CPU:    1
Feb  9 06:50:18 deleuze kernel: EIP:    0060:[may_delete+274/288]    Tainted: P 
     VLI
Feb  9 06:50:18 deleuze kernel: EFLAGS: 00010202   (2.6.18.3-doc1 #1) 
Feb  9 06:50:18 deleuze kernel: EIP is at may_delete+0x112/0x120
Feb  9 06:50:18 deleuze kernel: eax: f7dd8e94   ebx: e6828580   ecx: f704dd00   
edx: 00000104
Feb  9 06:50:18 deleuze kernel: esi: f7ea0f14   edi: f7ea0f14   ebp: f7ea0f14   
esp: e6d0df08
Feb  9 06:50:18 deleuze kernel: ds: 0068   es: 0068   ss: 0068
Feb  9 06:50:18 deleuze kernel: Process rm (pid: 18140, ti=e6d0c000 
task=c3326030 task.ti=e6d0c000)
Feb  9 06:50:18 deleuze kernel: Stack: f7841c40 e6a14094 e6a14094 00000000 
e6828580 000715fb e6828580 f7ea0f14 
Feb  9 06:50:18 deleuze kernel:        00000000 00000000 e6861000 f704dd00 
000717a4 e6828580 f7ea0f14 00000000 
Feb  9 06:50:18 deleuze kernel:        00000000 e6927214 f7841c40 1668358a 
00000007 e6861000 00000010 00000000 
Feb  9 06:50:18 deleuze kernel: Call Trace:
Feb  9 06:50:18 deleuze kernel: Code: 02 0f 44 d0 eb b6 ba fe ff ff ff eb af ba 
f0 ff ff ff eb a8 0f b7 40 28 ba eb ff ff ff 25 00 f0 00 00 3d 00 40 00 00 75 
c4 eb 91 <0f> 0b ea 04 78 5e c0 65 05 e9 0a ff ff ff 57 56 53 8b 74 24 10 
Feb  9 06:50:18 deleuze kernel: EIP: [may_delete+274/288] 
may_delete+0x112/0x120 SS:ESP 0068:e6d0df08

_______________________________________________
HCoop-SysAdmin mailing list
[email protected]
http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin

Reply via email to