> > can some please explain what is exactly an orphaned inode, so i can trace > > my implementation for bugs?? > > You are probably doing the reference-counting wrong. You should check, > that when you delete a dentry, the inode's nlink count is decremented > and the inode is properly marked dirty (so the nlink count makes it to > disk). i have come across this and have no idea if it might be helpful but hth http://www.coda.cs.cmu.edu/doc/talks/linuxvfs/tsld021.htm or http://www.coda.cs.cmu.edu/doc/talks/linuxvfs/index.htm and answer to subject... one way to get orphaned inodes probably is: one process opens file and keeps sleeping forever or cycling while still having the file opened another process deletes/unlinks file ()and on exit immediatly powers off or reboots or you switch the power off... some side effects probably included -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
