Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Lars Ellenberg wrote: > / 2004-04-26 13:37:04 +0200 > \ Andreas Semt: > >>Another question: I have a directory on a partition on top of a drbd >>device. The load average was very high for that machine (around 6). >>When i tried to do a "ls -l" in that directory, nothing happens, the "ls >>-l" command hangs. However there was no drbd traffic at all on the drbd >>device for the specific partition. Could it be that some drbd process >>was responsible for the "hang"? How can I detect which process access >>the drbd device at a particular time? > > > in normal operation, with drbd 0.6, you should have > drbd_receiver, drbd_asender on both nodes. > when sync is in progress, you have additionally the drbd_syncer. > > in 0.7, you have regardless of sync, on both nodes: > drbd_receiver, drbd_asender, drbd_worker. > Oh my ... drbd_receiver is not on one of the nodes! Here the output (i have four drbd devices): node1:~# ps aux | grep drbd root 255 0.8 0.0 0 0 ? SW 10:01 2:55 [drbdd_0] root 301 0.8 0.0 0 0 ? SW 10:01 2:44 [drbdd_1] root 347 0.0 0.0 0 0 ? SW 10:01 0:02 [drbdd_2] root 393 1.3 0.0 0 0 ? SW 10:01 4:19 [drbdd_3] root 4230 0.0 0.0 0 0 ? SW 10:17 0:00 [drbd_asender_0] root 6514 0.0 0.0 0 0 ? SW 10:32 0:00 [drbd_asender_1] root 8732 0.0 0.0 0 0 ? SW 10:48 0:00 [drbd_asender_2] root 11290 0.0 0.0 0 0 ? SW 11:04 0:00 [drbd_asender_3] node2:~# ps aux | grep drbd root 247 2.4 0.0 0 0 ? SW 10:01 8:15 [drbdd_0] root 292 2.4 0.0 0 0 ? SW 10:01 8:17 [drbdd_1] root 337 0.0 0.0 0 0 ? SW 10:01 0:10 [drbdd_2] root 382 5.2 0.0 0 0 ? SW 10:01 17:35 [drbdd_3] root 3915 0.2 0.0 0 0 ? SW 10:17 0:43 [drbd_asender_0] root 5786 0.2 0.0 0 0 ? SW 10:32 0:44 [drbd_asender_1] root 7666 0.0 0.0 0 0 ? SW 10:48 0:01 [drbd_asender_2] root 9563 0.5 0.0 0 0 ? SW 11:04 1:32 [drbd_asender_3] What does that mean? -- Best regards, Andreas Semt