On Fri, Feb 02, 2007 at 08:19:50PM +0530, Kalpak Shah wrote:
Index: linux-2.6.19/fs/ext3/super.c
===
--- linux-2.6.19.orig/fs/ext3/super.c
+++ linux-2.6.19/fs/ext3/super.c
@@ -1770,6 +1772,32 @@ static int ext3_fill_super (struct
On Tue, 16 Jan 2007 21:05:20 +0900
[EMAIL PROTECTED] wrote:
Move the blocks on the temporary inode to the original inode
by a page.
1. Read the file data from the old blocks to the page
2. Move the block on the temporary inode to the original inode
3. Write the file data on the page into the
On Mon, 5 Feb 2007 14:12:04 +0100
Jan Kara [EMAIL PROTECTED] wrote:
Move the blocks on the temporary inode to the original inode
by a page.
1. Read the file data from the old blocks to the page
2. Move the block on the temporary inode to the original inode
3. Write the file data on the
On Tue, 06 Feb 2007 11:33:46 +0300
Dmitriy Monakhov [EMAIL PROTECTED] wrote:
Almost all read/write operation handles data with chunks(segments or pages)
and result has integral behaviour for folowing scenario:
for_each_chunk() {
res = op();
if(IS_ERROR(res))
return
I plan to test the persistent preallocation patches on a huge sparse
device, to know if 32 bit physical block numbers (upto 48bit) behave as
expected. I have following questions for this and will appreciate
suggestions here:
a) What should be the sparse device size which I should use for testing?