Ghost inode
tjhu opened this issue · comments
When calling dump_inode , inode 14 is not found. But when calling mkdir foo, inode 14 is fetched somewhere and later causes a DirectoryExhausted error. Need to investigate why is inode 14 not generated in mkfs and how and why is it loaded in mkdir
INodeDataGuard { node: INode { meta: INodeMeta { device: 1, inum: 14, valid: true }, data: Mutex { } }, data: MutexGuard { lock: true, data: INodeData { file_type: Directory, major: 0, minor: 0, nlink: 1, size: 0, addresses: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] } } }`
Seems fixed by correcting dirlink