Messages in this thread | | | Subject | Breaking Ext3/VFS file size limit | From | "Goldwyn Rodrigues" <> | Date | Wed, 09 Jun 2004 18:51:20 +0530 |
| |
Hi,
I am building a custom kernel which could break the max file size limit from 2TB. I found the dependancy on number of 512-byte blocks, as i_blocks.
i_blocks is a 32 bit unsigned long in structures struct inode and struct ext3_inode. I changed it to unsigned long long in struct inode (in fs.h) and used a reserved field in ext3_inode to carry the higher order bits.
Also changed a checking function which returns the maximun possible size as 2TB.
My question is: Would changing the data type of i_blocks in struct inode (in fs.h) result in any breakdowns. It could happen if the inode structure is directly mapped to some other structure.
I tested at my end with a low end PC and it seems to work fine, for the past 6 hours.
Thanks,
-- Goldwyn :o)
PS: I am posting for the first time, so please forgive me (but do tell me, personally if possible) if I commit a mistake.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |