On Thu, May 18, 2000 at 04:13:43PM +0200, Niels Chr. Bank-Pedersen wrote:
> Hi,
>
> On a -current box, sources approx. 2½ days old, I'm
> having problems using a vinum raid5 volume - usually
> the box freezes totally when trying to use the filesystem
> (mkdir xxx; cd xxx -> crash), but last time it dropped
> to the debugger:
>
> mode = 040755, inum = 25344, fs = /raid5
> panic: ffs_valloc: dup alloc
> Debugger("panic")
> Stopped at Debugger+0x35: movb $0,in_Debugger.390
> db> trace
> Debugger(c0245ca3) at Debugger+0x35
> panic(c0252541,c0252520,41ed,6300,c109e0d4) at panic+0x70
> ffs_valloc(c9e7e300,41ed,c1171400,c9e69d08,c9e69e70) at ffs_valloc+0xf8
> ufs_mkdir(c9e69e70,c9e69f2c,c018d272,c9e69e70,c9e2c8e0) at ufs_mkdir+0x82
> ufs_vnoperate(c9e69e70,c9e2c8e0,2,c9e69f80,c02651e0) at ufs_vnoperate+0x15
> mkdir(c9e2c8e0,c9e69f80,bfbffc1c,1,1ff) at mkdir+0x162
> syscall2(2f,2f,2f,1ff,1) at syscall2+0x1f1
> Xint0x80_syscall() at Xint0x80_syscall+0x28
> db>
>
> I had one crash on my first attempt initialising the volume,
> but was able to newfs without any problems after initializing
> succeeded on the second attempt.
>
> Anybody able to see what could be happening here?
> (dmesg below, and dump/kernel.debug available)
I don't know what Greg thinks about but I beleave that the dup alloc is not
the reason itself.
Does vinum list saying that one subdisk of your R5 volume is down?
If yes with which version did you last initialized the plex?
Are you using softupdates?
--
B.Walter COSMO-Project http://www.cosmo-project.de
[EMAIL PROTECTED] Usergroup [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
