[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] buffer/cache: Underlying device vs. mapper device
- From: Alasdair G Kergon <agk redhat com>
- To: device-mapper development <dm-devel redhat com>
- Subject: Re: [dm-devel] buffer/cache: Underlying device vs. mapper device
- Date: Sat, 18 Dec 2004 19:23:56 +0000
On Fri, Dec 17, 2004 at 10:17:15PM +0100, Arno Wagner wrote:
> The data read from /dev/hdX does not reflect the write to /dev/mapper/xx
> or only after a lot of data ( > main memory) has been written. Waiting
> does not help. (After 1 hour still no change.)
I've seen similar issues in 2.6 for a long time with loop devices
I use for testing needing to be flushed explicitly.
(blockdev --flushbufs)
I've not managed to find time to investigate yet.
Alasdair
--
agk redhat com
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]