Le 04/04/2013 23:37, Bruce Dubbs a écrit :
> Pierre Labastie wrote:
>> Le 04/04/2013 18:08, Bruce Dubbs a écrit :
>>> Pierre Labastie wrote:
>>>> Le 03/04/2013 00:26, Bruce Dubbs a écrit :
>>>>> Pierre Labastie wrote:
>>>>>> Le 02/04/2013 19:39, Bruce Dubbs a écrit :
>>>>>>> I was meaning to bring this up again. I get
>>>>>>>
>>>>>>> Running ./pmap.test/pmap.exp ...
>>>>>>> FAIL: pmap X with unreachable process
>>>>>>> FAIL: pmap XX with unreachable process
>>>>> That means that it can't find /proc/1.  If /proc is mounted, that should
>>>>> always be there, e.g. `cat /proc/1/cmdline`.
>>>>>
>>>>>
>>>>>>> vmstat gives me:
>>>>>>>
>>>>>>> # of expected passes    6
>>>>>> I have not been able to reproduce the /proc/diskstats beginning with
>>>>>> sr0. Only in that case does the vmstat test fail.
>>>>> Isn't sr0 a cdrom?  On my system, I have:
>>>>>
>>>>>         11       0 sr0 0 0 0 0 0 0 0 0 0 0 0
>>>>>
>>>>> Major dev#, minor dev#, name, counters...
>>>>>
>>>>>
>>>> The failure in the test depends on the ordering of the the
>>>> /proc/diskstats table. This morning, I had:
>>>> -------------------------------
>>>> pierre@debian32-virt:~$ cat /proc/diskstats
>>>>         2       0 fd0 0 0 0 0 0 0 0 0 0 0 0
>>>>        11       0 sr0 19 0 152 136 0 0 0 0 0 136 136
>>>>         8       0 sda 32783 8723 2567928 84792 336771 8561249 71767606
>>>> 11478240 0 1477316 11607988
>>>>         8       1 sda1 559 2108 19320 1148 4 0 20 0 0 956 1148
>>>>         8       2 sda2 161 31 1536 172 0 0 0 0 0 172 172
>>>> [...]
>>>> -------------------------------
>>>> And the test failed with:
>>>> Running ./vmstat.test/vmstat.exp ...
>>>> FAIL: vmstat partition (using sr0)
>>>>
>>>>                      === vmstat Summary ===
>>>>
>>>> # of expected passes            5
>>>> # of unexpected failures        1
>>>> /sources/procps-ng-3.3.7/vmstat version 3.3.7
>>>> -------------------------------
>>>> The problem is that '  11       0 sr0 19 0 152 136 0 0 0 0 0 136 136'
>>>> matches
>>>> '\\s+\\d+\\s+\\d+\\s+\(\[a-z\]+\\d+\)\\s+\(\[0-9\]\[0-9\]+\)' (in
>>>> vmstat.exp).
>>> I guess they were not expecting you to have done reads from the cdrom.
>>>
>> I haven't. Of course, I could disable the CDROM on the virtual machine.
>> But when it is present, there are always a few reads, even if I boot
>> from disk. I guess the kernel makes a few reads at init time.
> That seems specific to your virtual system (which one?).
Qemu-kvm (1.1.2). Among the options I have:
-drive file=/mnt/virtualfs/aqemu/debian32.qcow2,cache=writeback \
-cdrom /mnt/virtualfs/debian-6.0.4-i386-businesscard.iso

So the virtual CDROM is always in the virtual drive, which explains the 
few reads, although I do not mount it.
>   My non-virtual
> system has:
>
>     11       0 sr0 0 0 0 0 0 0 0 0 0 0 0
>
> But it is after sd{a,b,c}, so it is a race condition also.
>
> Perhaps the search should be for [s|h]d[a-z]\s+\d\d+
Aren't there cases where the naming is different (for example SSD 
drives)? Just guessing here.

Pierre
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to