6 Commits

Author	SHA1	Message	Date
Milan Broz	d396100278	Use readahead of underlying device and not default (smaller) one. ... When we are stacking LV over device, which has for some reason increased read_ahead (e.g. MD RAID), the read_ahead hint for libdevmapper is wrong (it is zero). If the calculated read_ahead hint is zero, patch uses read_ahead of underlying device (if first segment is PV) when setting DM_READ_AHEAD_MINIMUM_FLAG. Because we are using dev-cache, it also store this value to cache for future use (if several LVs are over one PV, BLKRAGET is called only once for underlying device.) This should fix all the reamining problems with readahead mismatch reported for DM over MD configurations (and similar cases).	2009-05-20 11:09:49 +00:00
Dave Wysochanski	1cbdc00ecc	Update t-read-ahead.sh to validate lv_read_ahead and lv_kernel_read_ahead. ... - check default values - check active/inactive values	2009-05-11 16:17:12 +00:00
Petr Rockai	b6f3ef938a	Minor code and documentation cleanups and changes by jstava.	2008-11-10 12:43:35 +00:00
Petr Rockai	3740ffa6e0	More test conversions by jstava. Make check still passes.	2008-10-06 16:47:07 +00:00
Zdenek Kabelac	e2ebc2a08d	* parse error output for 'auto' keyword	2008-08-04 09:15:15 +00:00
Zdenek Kabelac	5f2c195933	Improve/Fix read ahead 'auto' calculation for stripe_size ... Fix lvchange output for -r auto setting if auto is already set Add testcase for read ahead	2008-06-18 11:32:14 +00:00