processes freezing when writing to gstripe'd device
Pawel Jakub Dawidek
pjd at FreeBSD.org
Sun Aug 1 23:53:54 PDT 2004
On Mon, Aug 02, 2004 at 08:38:51AM +0200, Pawel Jakub Dawidek wrote:
+> +> What's the best way to look in to this? I can't attach to rm with gdb
+> +> (it just ends up waiting for something). I can drop to kdb, but have no
+> +> idea where to go from there.
+> You could use 'ps' command from DDB to which processes are alseep.
+> Then you can run 'tr <PID>' where <PID> is PID of sleeping process.
+> Look for processes related somehow to this problem.
+> It'll be also great if you can provide exact procedure which will also
+> me to reproduce this problem.
+> PS. If you plan to upgrade your machine, remember than naming has changed
+> in gstripe from /dev/<name>.stripe to /dev/stripe/<name>.
One more note. I'm quite sure it is not related to gstripe, because its
implementation is very simple: it doesn't use [mt]sleep(9) (so there is no
missing wakeup()), it doesn't use any mutexes, so while debugging you may
want also look at other components.
Pawel Jakub Dawidek http://www.FreeBSD.org
pjd at FreeBSD.org http://garage.freebsd.pl
FreeBSD committer Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040802/a2fa2ee1/attachment.bin
More information about the freebsd-current