Ticket #31 (closed defect: obsolete)

Opened 5 years ago

Last modified 4 years ago

Journal: USB stick does not register when inserted.

Reported by: mungewell Owned by: tomeu
Priority: major Milestone:
Component: journal Version: 0.82.x
Severity: Major Keywords:
Cc: Distribution/OS: Unspecified
Bug Status: Resolved

Description

I had a couple of times over the weekend when a working USB stick became 'un-registerable', it would not show itself at the bottom of the journal page.

I had the following error in the journal log
--
'DatabaseLockError: Unable to acquire database write lock on /media/LEXAR/.olpc.store/index'
--

On mounting the drive read/write and erasing the directory '.olpc.store' and unmounting/removing the USB stick it became useable again.

I think that this may be caused by unplugging a mounted USB stick without umounting.... probably a likely event with school children.

Change History

Changed 4 years ago by tomeu

  • owner changed from marcopg to tomeu
  • component changed from sugar to journal

Changed 4 years ago by tomeu

  • version set to 0.82.x

Changed 4 years ago by gregdek

  • distribution set to Unspecified
  • severity set to Blocker
  • status_field set to Needinfo

Great bug. Some more info would be very helpful here. Could you help us further isolate to a single reproducible case? Some info that would be helpful:

1. Is this on an XO only, or does it happen on non-XOs as well?

2. Can you reliably make it happen with the same error?

3. The theory of "unplugging and then replugging" -- have you tried it, and does that always create the same error?

If you can give us one series of steps that will *always* give this error, that will be much appreciated. Thanks for reporting.

Changed 4 years ago by gregdek

  • severity changed from Blocker to Major

Also, I'm going to set severity of this to "Major," since if this is a problem, I'd call it major myself.

Changed 4 years ago by erikos

  • status changed from new to closed
  • resolution set to obsolete
  • status_field changed from Needinfo to Resolved

Unlikely that we have the ressources to fix this. And it looks like we do not even have a way to reproduce this. This has no effect on 0.84.

Sorry :/

Note: See TracTickets for help on using tickets.