[lvm-devel] LVM2 test script failed, is it a read_ahead bug?
Zdenek Kabelac
zkabelac at redhat.com
Tue Aug 27 10:42:32 UTC 2013
Dne 27.8.2013 12:00, Dongmao Zhang napsal(a):
> Dear mail-list,
> I met this in running the test case for lvm:
> sh shell/read-ahead.sh FAILED:
>
>
> - if (current_read_ahead >= read_ahead) {
> + if (current_read_ahead <= read_ahead) {
> log_debug_activation("%s: retaining kernel read
> ahead of %" PRIu32
> " (requested %" PRIu32 ")",
> dev_name, current_read_ahead, read_ahead);
>
> If I am wrong, please correct me:)
>
Basic rules for 'auto'mated read_ahead setting is simple: never set smaller
value then the one which has been already set by kernel when device has been
initialized.
If you need any specific more 'clever' value - simply use direct value for
lvcreate/lvchange --readahead.
There is no thing like 'minimal' RA estimation in lvm2.
It's quite tricky to estimate the ideal RA for devices and it mostly depends
on the type of use.
Zdenek
More information about the lvm-devel
mailing list