Anand Avati wrote:
On Thu, Jan 7, 2010 at 4:51 AM, Gordan Bobic <gordan@xxxxxxxxxx> wrote:
I'm seeing something peculiar. lsof is showing glusterfs as having deleted
file handles open in the backing store. That's fine, those file handles are
open by the process running on top of it. But the process running on top of
glusterfs isn't showing the same file handle as deleted. That seems odd. Is
that normal?
The deleted files in question were prelink files. Restarting the processes
having those handles open cleared them. I'd still like to know, though, why
they were showing as deleted in the backing store but this wasn't being
passed up to the mounted level.
Are you using release 2.x? In 2.x we sometimes keep an open file
descriptor after a file deletion for sometime to prevent inode number
collisions. In 3.x we do not have this problem+workaround as all inode
numbers are stamped with a generation number.
Yes, I'm using 2.0.9. The thing that puzzles me is why does the file
show up as deleted (using lsof) on the backing store, but the program
that has it open in the mount point doesn't have it listed as deleted.
Surely it should show up as deleted in both places, should it not?
Gordan
