Re: File system deadlock. GBDE(4) and/or MD(4) related.

2003-07-24 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Pawel Jakub Dawidek writ es: >+> One way or another: It is _not_ a GBDE problem. > >Hey, Poul! I'm not trying to show that gbde(4) is a buggy software, >I'm not trying to destroy you work, your image or FreeBSD, really. > >I believe that this isn't bug in gbde(4),

Re: File system deadlock. GBDE(4) and/or MD(4) related.

2003-07-24 Thread Pawel Jakub Dawidek
On Thu, Jul 24, 2003 at 08:38:02PM +0200, Poul-Henning Kamp wrote: +> >+> What you have found has nothing to do with GBDE, I think it is the +> >+> usual "vnode backed md(4)" deadlock. +> > +> >Hmm? So you're trying to tell that this is somehow normal behaviour? +> +> We've had problems like this

Re: File system deadlock. GBDE(4) and/or MD(4) related.

2003-07-24 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Pawel Jakub Dawidek writ es: >+> dd if=3D/dev/null of=3D/mnt/test.file bs=3D1m count=3D512 > >You mean /dev/zero? But this doesn't change anything. Yes, /dev/zero of course. >+> > # mdconfig -a -t vnode -f /mnt/test.file -s 512M -u 1 >+>=20 >+> What you have

Re: File system deadlock. GBDE(4) and/or MD(4) related.

2003-07-24 Thread Pawel Jakub Dawidek
On Thu, Jul 24, 2003 at 05:03:23PM +0200, Poul-Henning Kamp wrote: +> ># touch /mnt/test.file +> +> You are probably missing: +> +> dd if=/dev/null of=/mnt/test.file bs=1m count=512 You mean /dev/zero? But this doesn't change anything. +> ># mdconfig -a -t vnode -f /mnt/test.file -

Re: File system deadlock. GBDE(4) and/or MD(4) related.

2003-07-24 Thread Jon Disnard
Poul-Henning Kamp wrote: In message <[EMAIL PROTECTED]>, Pawel Jakub Dawidek writ es: # touch /mnt/test.file You are probably missing: dd if=/dev/null of=/mnt/test.file bs=1m count=512 # mdconfig -a -t vnode -f /mnt/test.file -s 512M -u 1 What you have found has nothing to do with GBDE,

Re: File system deadlock. GBDE(4) and/or MD(4) related.

2003-07-24 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Pawel Jakub Dawidek writ es: > # touch /mnt/test.file You are probably missing: dd if=/dev/null of=/mnt/test.file bs=1m count=512 > # mdconfig -a -t vnode -f /mnt/test.file -s 512M -u 1 What you have found has nothing to do with GBDE, I think

Re: File system deadlock. GBDE(4) and/or MD(4) related.

2003-07-24 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Pawel Jakub Dawidek writ es: > >On Thu, Jul 24, 2003 at 03:57:07PM +0200, Pawel Jakub Dawidek wrote: >+> I've found deadlock in gbde(4) and/or md(4). > >Yes, it is gbde fault: I don't know what you have found, but I can guarantee you that it is _not_ gbde that holds

Re: File system deadlock. GBDE(4) and/or MD(4) related.

2003-07-24 Thread Pawel Jakub Dawidek
On Thu, Jul 24, 2003 at 03:57:07PM +0200, Pawel Jakub Dawidek wrote: +> I've found deadlock in gbde(4) and/or md(4). Yes, it is gbde fault: db> show lockedvnods [...] 0xc3332920: tag ufs, type VREG, usecount 1, writecount 0, refcount 21, flags (VV_OBJBUF), lock type ufs: EXCL (count 1) by thread

File system deadlock. GBDE(4) and/or MD(4) related.

2003-07-24 Thread Pawel Jakub Dawidek
Hello. I've found deadlock in gbde(4) and/or md(4). Here is a complete procedure hot to repeat it: # touch /mnt/test.file # mdconfig -a -t vnode -f /mnt/test.file -s 512M -u 1 # mkdir /etc/gbde # gbde init /dev/md1 -L /etc/gbde/md1 Enter new passphrase: