Issue 35: Error in selecting inodes for relocation
Status:  Fixed
Owner:
Closed:  Jan 2009
Reported by postri...@gmail.com, Jan 23, 2009
Hello everyone,

In selecting the qualifying inodes for relocation there is an error

1. The file system is not getting unmounted even after forcing it to do so

2. The inodes (files) which are deleted are also scanned for qualification.
This gets verified as you unmount( in this case reboot) the system

otherwise,

if you want to know wether any specific inode e.g. 12 is qualifying for
relocation or not then it is working fine

How to proceed ??
Jan 23, 2009
Project Member #1 sandeepksinha
What do you mean by the inodes which are deleted are also qualified for relocation ?
Do you mean that you create a FS and create two files X and Y and then you delete X.
Later when you run your code it also gets the inode bit set in the inode bitmap and
hence it goes for checking if it qualifies.

Can you provide me the logs or steps how you are doing and also point me to the
source code on the SVN ?

If its not there on the SVN you can upload and provide me with the path.
Labels: OpSys-Linux Milestone-Release1.0 Component-Logic
Jan 23, 2009
#2 postri...@gmail.com
The code seems to be working fine now. 
Jan 27, 2009
#3 postri...@gmail.com

-> The file system was busy because some path_puts were missing.

-> Due to the above error the FS crashed and thus bits were not UNSET hence old
inodes were also SET
Status: Fixed
Labels: -Priority-High -OpSys-Linux -Component-Logic Priority-Critical