File system deadlock. GBDE(4) and/or MD(4) related.
Poul-Henning Kamp
phk at phk.freebsd.dk
Thu Jul 24 11:38:06 PDT 2003
In message <20030724182836.GY43543 at garage.freebsd.pl>, 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 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 before with vnode backed MD(4) devices
(and vn(4) devices before that).
One way or another: It is _not_ a GBDE problem.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
More information about the freebsd-current
mailing list