On Tue, Jan 6, 2009 at 7:42 PM, rishi agrawal <postrishi@xxxxxxxxx> wrote: > yes i suppose the donor inode is known > moreover the receiver inode's number is also known > > On Tue, Jan 6, 2009 at 6:54 PM, Manish Katiyar <mkatiyar@xxxxxxxxx> wrote: >> >> On Tue, Jan 6, 2009 at 4:06 PM, Rohit Sharma <imreckless@xxxxxxxxx> wrote: >> > I want to read data blocks from one inode >> > and copy it to other inode. >> > >> > I mean to copy data from data blocks associated with one inode >> > to the data blocks associated with other inode. >> >> Copying 4K chunk of data itself is a costly operation. and depending Yes its a costly operation, but if this can be done then we can definitely copy n blocks at a time. >> on the size of your donor inode this can be huge . Why do you want to >> do that ? Do you know the inode of the donor inode ? For physically relocating a file from one disk to other. Yes Manish, i know the donor inode and i will create the reciever inode. Can we do that in kernel space.? >> >> thanks - >> Manish >> > >> > Is that possible in kernel space.? >> > -- >> > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in >> > the body of a message to majordomo@xxxxxxxxxxxxxxx >> > More majordomo info at http://vger.kernel.org/majordomo-info.html >> > >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > -- > Regards, > Rishi B. Agrawal > > -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
