processes freezing when writing to gstripe'd device
Pawel Jakub Dawidek
pjd at FreeBSD.org
Sun Aug 1 23:38:54 PDT 2004
On Mon, Aug 02, 2004 at 11:44:31AM +1000, Sam Lawrance wrote:
+> I'm running current from around the 24th of July. About to build world
+> to see if it makes any difference.
+> I am observing processes performing operations on a gstripe device
+> freeze in state 'bufwait'. An 'rm' process is stuck right now. The rest
+> of the system is fine.
+> The devices are two vnode backed md devices which I created just for
+> testing. The same thing occurred using two freebsd partitions of size
+> 15G each (not slices).
+> NAME: test_cd.stripe
+> geom name: test_cd.stripe
+> mediasize: 10231808 (9.8M)
+> sectorsize: 512
+> mode: r1w1e0
+> state: UP
+> status: total=2, online=2
+> providers: md3 md2
+> type: automatic
+> stripesize: 4096
+> id: 1411913070
+> 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>.
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/9dde73a9/attachment.bin
More information about the freebsd-current