It is most likely ClearCase. I also get these errors with my Dell 6450
dual-P3 Xeon. If I run it on a uni-processor kernel, these go away. I am
still trying to get Rational to fix this. Talk to Rational support, and
maybe together we can get a fix.
Forrest
> -----Original Message-----
> From: Toby Bluhm [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 13, 2001 8:54 AM
> To: [EMAIL PROTECTED]
> Subject: busy inodes & other stuff
>
>
> I have a dual p3 dell here with ClearCase installed on it,
> stock kernel
> 2.4.2-2 with mvfs.o module glued in. This is what i found on
> the console
> this morning:
>
>
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds.
> Have a nice
> day...
> Unable to handle kernel paging request at virtual address 00060027
> printing eip:
> f896d7fb
> pgd entry eff78000: 0000000000000000
> pmd entry eff78000: 0000000000000000
> ... pmd not present!
> Oops: 0000
> CPU: 1
> EIP: 0010:[<f896d7fb>]
> EFLAGS: 00010202
> eax: 00418ead ebx: 00000004 ecx: 00000000 edx: eed4fc94
> esi: 00060003 edi: 00060003 ebp: 00000000 esp: eed4fb64
> ds: 0018 es: 0018 ss: 0018
> Process csh (pid: 15269, stackpage=eed4f000)
> Stack: eed4fbc4 00060003 c50bb3e0 eed4fbbc f896d95c 00060003 00000000
> eed4fbc4
> eed4fbc4 f8968596 eed4fbc4 00000000 f8968479 eed4fbc4 eed4fc94
> 00000000
> eed4fbc4 c50bb3e0 00000000 00000000 c50bb3e0 eed4fbbc 00000002
> 00000000
> Call Trace: [<f896d95c>] [<f8968596>] [<f8968479>] [<f896b600>]
> [<f898fa9d>] [<f8a30819>] [<f898967d>]
> [<f8a434f9>] [<f8a3e4f8>] [<f8a3e4ea>] [<f8a587ac>]
> [<f8a29b17>]
> [<f89893f9>] [<f8a3bd4f>] [<f8a3f028>]
> [<f8a23df8>] [<f8a23fd5>] [<f8a1fc6e>] [<f8a1a751>]
> [<f8a1a730>]
> [<f8a3ceb5>] [<f8a3cfb6>] [<f8a23fd5>]
> [<f8a587ac>] [<f8a24080>] [<f8a24034>] [<f8a24020>]
> [<c014f0e6>]
> [<c0145a83>] [<c0146385>] [<c0115c66>]
> [<c0146d60>] [<c0139ae6>] [<c01456fb>] [<c0139dfa>]
> [<c01091cb>]
>
> Code: 39 47 24 79 07 57 e8 9a fe ff ff 5e f0 fe 0d 80 6f 97 f8 0f
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds.
> Have a nice
> day...
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds.
> Have a nice
> day...
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds.
> Have a nice
> day...
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds.
> Have a nice
> day...
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds.
> Have a nice
> day...
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds.
> Have a nice
> day...
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds.
> Have a nice
> day...
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds.
> Have a nice
> day...
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds.
> Have a nice
> day...
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds.
> Have a nice
> day...
>
>
> I could log in, but things like nfs & sendmail did not seem to be
> running right. When I rebooted it, nfs, xfs, amd, sendmail & a couple
> other init scripts complained "no such PID" when trying to shut down.
> When it got to "No more processes left in this level" it got stuck. I
> had to push the button. Fsck'd ok & seems okay now.
>
> Any clue as to what this might mean? Is it a hardware problem with CPU
> 1?
>
> Thanks.
>
>
>
> --
> toby
>
>
>
> _______________________________________________
> Seawolf-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/seawolf-list
>
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
