Re: [Help-gnunet] Unable to unindex a file

[Christian Grothoff]

On Thursday 24 Jun 2004 11:51 am, Daniel Connolly wrote:
> Does any type of cleansing happen at all? E.g. expiry of content such as
> in Freenet? Not that expiry of content the way Freenet does it is
> necessarily a good thing, its one of the reasons I am looking at gnunet.

In practice GNUnet should not expire content from the local datastore that was 
inserted (or indexed) by the (local) user.  Content that migrates through the 
network can eventually face expiration due to limited disk-space.

> Assuming that the reference gets propagated out to other nodes (not sure
> if this happens, need to read more of the papers), eventually there's
> going to be a mass of invalid references pointing to deleted content or
> nodes that no longer exist, which will be a very frustrating experience
> for users.

Right, there exist such problems with the current design/code and an attempt 
for a solution is on the todo list.

> Now, I also get the warnings, so there's some bug there that I'll have
> to investigate.  Presumably some blocks are not removed from the database
> as they should be.  This will probably take a few hours... :-)

Actually, there was no 'bug' in the strict sense.  I've documented the issue 
in more detail in the FAQ (http://www.ovmj.org/GNUnet/faq.php3#delete).  
Furthermore, I've downgraded the 'WARNING's to mere 'DEBUG' messages, which 
is more appropriate since in this case everything was working just fine (with 
only some interesting corner cases happening more often than one would 
expect).

Christian

> On Wednesday 23 Jun 2004 3:18 am, Daniel Connolly wrote:
> > If I try to delete a file I have recently indexed, using this:
> >
> > gnunet-delete -f <filename>
> >
> > I get a series of error messages:
> >
> > Jun 22 23:36:06 WARNING: server could not perform unindexing
> > Jun 22 23:36:06 WARNING: child->delete failed on level 1, pos 4952064.
> > Will continue.
> > Jun 22 23:36:06 WARNING: server could not perform unindexing
> > Jun 22 23:36:06 WARNING: child->delete failed on level 1, pos 4953088.
> > Will continue.
> > Jun 22 23:36:06 WARNING: server could not perform unindexing
> > Jun 22 23:36:06 WARNING: child->delete failed on level 1, pos 4954112.
> > Will continue.
> > Jun 22 23:36:06 WARNING: server could not perform unindexing
> > Jun 22 23:36:06 WARNING: child->delete failed on level 1, pos 4955136.
> > Will continue.
> > Jun 22 23:36:06 WARNING: server could not perform unindexing
> > Jun 22 23:36:06 WARNING: child->delete failed on level 1, pos 4956160.
> > Will continue.
> > Jun 22 23:36:06 WARNING: server could not perform unindexing
> > Jun 22 23:36:06 WARNING: child->delete failed on level 1, pos 4957184.
> > Will continue.
> > Jun 22 23:36:06 WARNING: server could not perform unindexing
> > Jun 22 23:36:06 WARNING: child->delete failed on level 1, pos 4958208.
> > Will continue.
> > Jun 22 23:36:06 WARNING: server could not perform unindexing
> > Jun 22 23:36:06 WARNING: child->delete failed on level 1, pos 4959232.
> > Will continue.
> > Jun 22 23:36:06 WARNING: server could not perform unindexing
> > Jun 22 23:36:06 WARNING: child->delete failed on level 1, pos 4960256.
> > Will continue.
> > Jun 22 23:36:06 WARNING: server could not perform unindexing
> > Jun 22 23:36:06 WARNING: child->delete failed on level 1, pos 4961280.
> > Will continue.
> >
> > If I then do a search, it still returns the file, with the same
> > identifier. If I try to download it then it just times out.
> >
> > Any ideas?
> >
> > Dan