Pawel Jakub Dawidek wrote: > On Wed, Sep 09, 2009 at 10:07:08AM -0700, Matthew Ahrens wrote: >> Unfortunately, I don't think that the send stream would help us diagnose it >> further. What we really need is a way to reproduce how to get into this >> situation in the first place. > > Yes and we unfortunatelly cannot provide a way to reproduce it. > > I'm still looking at it and this is what I found: > > When I delete duplicated entries, export&import the pool to flush the > cache I can see the covered entries. They are almost exactly the same > (same name, same size, same md5 sum), the only thing that is different > are inodes - those duplicates have different inode number that the ones > I removed.
That's an interesting piece of information. And can you tell if all the inode numbers referenced are valid files still? Their zp_parent should point to this directory. --matt
