On 01/25/2012 08:44 PM, Lutz Vieweg wrote:
diff --git a/drbd/drbd_req.c b/drbd/drbd_req.c
+ part_round_stats(cpu,&mdev->vdisk->part0);
Does it look more useful now?
Yes, this works for me (applyied to linux-3.2.1).
I should add that I could only test situations where the
storage is the bottle
On 01/21/2012 04:48 PM, Lars Ellenberg wrote:
Yet, it would be nice if the "utilization percentage" reported
for drbd device was meaningful.
Thanks for the reminder...
besides these stats not being very useful for "virtual" block devices
that do not have any queue anyways, it looks like our sta
On Fri, Jan 20, 2012 at 08:40:02PM +0100, Lutz Vieweg wrote:
> On 01/19/2012 02:17 PM, Andreas Kurz wrote:
> >>I don't understand why my drbd device is at 100 %util.
> >
> >So think you should get higher write??
>
> I think he's just wondering why the drbd device reports
> near 100% utilization wh
On 01/19/2012 02:17 PM, Andreas Kurz wrote:
I don't understand why my drbd device is at 100 %util.
>
So think you should get higher write??
I think he's just wondering why the drbd device reports
near 100% utilization while the underlying physical device
seems much less utilized.
I've been w
sorry if that might get double-posted ... I used wrong sender address on
initial reply ...
--
Hello,
On 01/19/2012 07:56 AM, Matthieu Lejeune wrote:
> Hello,
>
> I have a primary/secondary node with 2 ressources.
> When I watch the i/O performance i look some think like this :
>
> When I w
Hello,
I have a primary/secondary node with 2 ressources.
When I watch the i/O performance i look some think like this :
When I watch the physical drive utilisation :
root@relax:~# iostat -x /dev/sda 1
Linux 2.6.32-5-amd64 (relax) 01/19/2012 _x86_64_(16 CPU)
avg-cpu: %user %nice
