Hello there !
Well I've implemented ext2 fs and I have no problems regarding that !
But I got stucked when I tried to use my ext2 driver for ext3 filesystem !
Most of the things are similiar and the driver works for most of stuff
EXCEPT for the stranger BLOCK numbers (32bit numbers much higher then the number of blocks available for the partition) that appear in the INODES.
EXT3 -> INODE -> Direct Block Pointer 0 = instead of a normal block number it's a strage 32bit number looking like 0xF12AB132 !!! this is not a block number !
Couldn't find an answer for this !
Do you folks know about this ?
Best regards !
Happy coding !
EXT3 -> INODE -> Direct Block Pointer 0
Re: EXT3 -> INODE -> Direct Block Pointer 0
Hi,
I'm not sure this helps, but IIRC it may be the case that the file is small enough that its data is being placed inside the block pointer fields.There may be an Inode flag that is set when this happens. Hope this helps.
JVFF
I'm not sure this helps, but IIRC it may be the case that the file is small enough that its data is being placed inside the block pointer fields.There may be an Inode flag that is set when this happens. Hope this helps.
JVFF
Re: EXT3 -> INODE -> Direct Block Pointer 0
This is useful ! ... but not in all cases ... For small enough files this is the reasonjvff wrote:Hi,
I'm not sure this helps, but IIRC it may be the case that the file is small enough that its data is being placed inside the block pointer fields.There may be an Inode flag that is set when this happens. Hope this helps.
JVFF
But I've encountered the same problem with big files ... Don't know why ....