Hmm. I've seen several panics over the last day or so with -current where /
got corrupted (ino 2).
On Thu, 2 Nov 2000, Justin T. Gibbs wrote:
> I beleive that I've somehow corrupted my /dev on my laptop.
> An ls -l in there causes an instant panic:
>
> Copied by hand...
>
> vfinddev(ffffffff,3,c877ac84,10002,1) at vfinddev+0xc
> ^^^^^^^^<= NODEV
> addaliasu(c7dc0a00,10002,c0b04800,c33e1180,c0b149e4) at ufs_vinit+0x44
> ufs_vinit(c0b01c00,c0abe900,c0abed00,c877acec,c333f380) at ufs_vinit+0x4e
> ffs_vget(c0b01c00,1882,c877ad60,0,c7dc1900) at ffs_vget+0x267
> ufs_lookup(c877adb8,c877adcc,c018e6fa,c877adb8,c7dc1900) at ufs_lookup+0x995
> ufs_vnoperate(c877adb8,c7dc1900,c8770c03,c877aeb4,c877adc0 at ufs_vnoperate+15
> vfs_cache_lookup(c877ae10,c877ae20,c0191804,c877ae10,c7dc1900) at
>vfs_cache_lookup+0x28a
> ufs_vnoperate(c877ae10,c7dc1900,c0b1c800,c877aeb4,c77e5840) at ufs_vnoperate+0x15
> lookup(c877ae8c,c02b57d8,0,c77e5840,c77e5840) at lookup+0x290
> namei(c877ae8c,c02b57d8,0,c77e5840,80b4340) at namei+0x178
> lstat(c88e5840,c877af80,80b4348,80b5028,80b4300) at lstat+0x41
> syscall2(2f,2f,2f,80b4300,80b5028) at syscall2+0x33c
> Xint0x80_syscall() at Xint0x80_syscall+0x1f
>
> Since addaliasu doesn't bother to check for NODEV, I take it this is
> a "can't happen" situation?
>
> --
> Justin
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
