From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joel Becker Date: Wed, 23 Feb 2011 13:44:45 -0800 Subject: [Ocfs2-devel] [PATCH] Treat writes as new when holes span across page boundaries In-Reply-To: <20110223213730.GK4020@noexit> References: <20110222233417.GC28774@noexit> <20110223093932.GA30720@noexit> <20110223191338.GA4020@noexit> <20110223211704.GH4020@noexit> <20110223213730.GK4020@noexit> Message-ID: <20110223214444.GM4020@noexit> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ocfs2-devel@oss.oracle.com On Wed, Feb 23, 2011 at 01:37:31PM -0800, Joel Becker wrote: > On Wed, Feb 23, 2011 at 03:35:36PM -0600, Goldwyn Rodrigues wrote: > > On Wed, Feb 23, 2011 at 3:17 PM, Joel Becker wrote: > > >> 2. ?the previous write ended in a page boundary, but not a cluster > > >> boundary. eg, clustersize=16K but pos is at the page boundary = 4k > > > > > > ? ? ? ?Must it be a page boundary? ?What about a block boundary? ;-) > > > > I am not sure of this, but I would like to stick with page boundary. I > > am too poor to afford a machine with a page size bigger than 4k to > > test this ;) > > Create a filesystem with 1K blocks and 16K clusters. Now you > have four blocks per page, and you can test block vs page boundaries. I would love to see you modify tailtest to expose this bug. You should be able to do it with one set of writes (your write(4k), write(32b), write(4K at someplace past 4K+32b)) test). It will be a lot easier to debug if it is a simple script rather than a bunch of C writes. Joel -- "In the long run...we'll all be dead." -Unknown http://www.jlbec.org/ jlbec at evilplan.org