Date: Thu, 18 May 2000 23:43:58 +0200 From: "Niels Chr. Bank-Pedersen" <ncbp@bank-pedersen.dk> To: Bernd Walter <ticso@cicely.de> Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_valloc: dup alloc Message-ID: <20000518234358.B28600@bank-pedersen.dk> In-Reply-To: <20000518232151.A30272@cicely5.cicely.de>; from ticso@cicely.de on Thu, May 18, 2000 at 11:21:51PM %2B0200 References: <20000518161343.G26090@bank-pedersen.dk> <20000518232151.A30272@cicely5.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 18, 2000 at 11:21:51PM +0200, Bernd Walter wrote:
> 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?
No:
5 drives:
D raid5-00 State: up Device /dev/da1s1e Avail: 0/4133 MB (0%)
D raid5-01 State: up Device /dev/da3s1e Avail: 0/4133 MB (0%)
D raid5-02 State: up Device /dev/da5s1e Avail: 0/4133 MB (0%)
D raid5-03 State: up Device /dev/da6s1e Avail: 0/4133 MB (0%)
D raid5-04 State: up Device /dev/da7s1e Avail: 0/4133 MB (0%)
1 volumes:
V raid5 State: up Plexes: 1 Size: 16 GB
1 plexes:
P raid5.p0 R5 State: up Subdisks: 5 Size: 16 GB
5 subdisks:
S raid5.p0.s0 State: up PO: 0 B Size: 4133 MB
S raid5.p0.s1 State: up PO: 768 kB Size: 4133 MB
S raid5.p0.s2 State: up PO: 1536 kB Size: 4133 MB
S raid5.p0.s3 State: up PO: 2304 kB Size: 4133 MB
S raid5.p0.s4 State: up PO: 3072 kB Size: 4133 MB
- But since my first attempt to initialize the plex crashed the
box while only da5se1 was missing, I did a "verify media" from
the SCSI ctrl. BIOS, and did find errors. They were all successfully
remapped, though.
> If yes with which version did you last initialized the plex?
Newly created plex, so that would be the currently installed version.
> Are you using softupdates?
Yup. I am unable to try without SU right now (well, I could, but if it
doesnt work, my foot will be blown of), but I'll try that later when I
get home.
> B.Walter COSMO-Project http://www.cosmo-project.de
Thnx.
/Niels Chr.
--
Niels Christian Bank-Pedersen, NCB1-RIPE.
Network Manager, Tele Danmark NET, IP-section.
"Hey, are any of you guys out there actually *using* RFC 2549?"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000518234358.B28600>