Hi, On Thu, 4 Nov 1999 19:03:18 +0100 (CET), Rik van Riel <[EMAIL PROTECTED]> said: > The obvious solution would be to allow multiple versions of the > same disk block to be in memory. That is already possible. You can make as many buffer_heads as you want for a given disk block, as long as only one is in the buffer cache itself. > We need that anyway for journalling, so why not extend it with a flag > (or use another flag) to show that _this_ particular disk block is the > one on disk or the one supposed to be on disk (go on, flush this). That's just not the point --- even for the copy which _is_ supposed to be authoritative on disk, you can't be sure that it is in fact uptodate because there is a race between the filesystem modifying the buffer contents and the dirty bit being marked in the buffer_head. --Stephen
- Re: Raid resync changes buffer cache semantics --- not ... Ingo Molnar
- Re: Raid resync changes buffer cache semantics ---... Stephen C. Tweedie
- Re: Raid resync changes buffer cache semantics... Stephen C. Tweedie
- Re: Raid resync changes buffer cache seman... Ingo Molnar
- Re: Raid resync changes buffer cache s... Stephen C. Tweedie
- Re: Raid resync changes buffer ca... Theodore Y. Ts'o
- Re: Raid resync changes buffer ca... Ingo Molnar
- Re: (reiserfs) Re: Raid resyn... Stephen C. Tweedie
- Re: (reiserfs) Re: Raid resyn... Ingo Molnar
- Re: (reiserfs) Re: Raid resyn... Rik van Riel
- Re: (reiserfs) Re: Raid resyn... Stephen C. Tweedie
- Re: (reiserfs) Re: Raid resyn... Stephen C. Tweedie
- Buffer and page cache braam
- Re: Buffer and page cache Stephen C. Tweedie
- Re: Raid resync changes buffer cache semantics --- not ... braam
- Re: Raid resync changes buffer cache semantics ---... Stephen C. Tweedie
- Re: Raid resync changes buffer cache semantics --- not ... Matt Zinkevicius
- Re: Raid resync changes buffer cache semantics ---... Daniel Veillard