Re: [tor-bugs] #9645 [Tor]: Tor client goes berserk downloading microdescriptors forever, if you rm -rf its datadir

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#9645: Tor client goes berserk downloading microdescriptors forever, if you rm -rf
its datadir
------------------------+--------------------------------
     Reporter:  arma    |      Owner:
         Type:  defect  |     Status:  needs_review
     Priority:  normal  |  Milestone:  Tor: 0.2.4.x-final
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:  tor-client
Actual Points:          |  Parent ID:
       Points:          |
------------------------+--------------------------------

Comment (by arma):

 Replying to [comment:4 nickm]:
 > Replying to [comment:3 nickm]:
 > > One option would be just to hold them in RAM when writing to disk
 fails, and not save them to disk at all.
 >
 > This is now "bug9645" in my public repository.
 >
 > > Another (simpler) option would be to exit Tor in this case.
 >
 > This is now "bug9645_big_hammer" in my public repository.
 >
 > These are incompatible with one another, and they both make the #9639
 fix unneeded.

 I don't think we can afford to exit here, so big_hammer isn't a good
 option.

 Are we likely to try writing them again later when we reform our journal
 file? Are there bugs there? I was about to merge bug9645 into maint-0.2.4
 for the new release when I realized it's the sort of thing that will
 produce weird edge cases. Maybe it's best to let it bake in master for a
 while before backporting it (or deciding not to).

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9645#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs