Ticket #7509 (new defect)

Opened 6 years ago

Last modified 6 years ago

journal fails to mount specific usb drive

Reported by: dsd Owned by: tomeu
Priority: high Milestone: 9.1.0-cancelled
Component: journal-activity Version:
Keywords: joyride-2131:- blocks-:8.2.0 8.2.0:- Cc: bjordan, jg, gregorio
Action Needed: diagnose Verified: no
Deployments affected: Blocked By:


Joyride 2131: The journal fails to mount Brian's usb drive.


org.laptop.JournalActivity-1.log (6.2 kB) - added by dsd 6 years ago.
journal log
broken.olpc.store.tar.gz (347.8 kB) - added by dsd 6 years ago.
tarball of broken .olpc.store directory

Change History

Changed 6 years ago by dsd

journal log

Changed 6 years ago by dsd

tarball of broken .olpc.store directory

Changed 6 years ago by dsd

  • owner set to tomeu
  • component changed from not assigned to journal-activity

Changed 6 years ago by cjb

  • keywords blocks?:8.2.0 8.2.0:? added
  • priority changed from normal to blocker
  • next_action changed from never set to diagnose
  • milestone set to 8.2.0 (was Update.2)

Bumping up, at least until diagnosis.

Changed 6 years ago by gregorio

  • cc jg, gregorio added

Hi Brian,

Which USB drive is it? Did it work in previous releases?

Do we know if other USB drives work?

Thanks for filing this one. If its only one specific USB drive that is not common and never worked before I would not mark this a blocker, but if it used to work and its common or it affects a whole class of USB stick I would make it a blocker.

I'll leave it ? for now.


Greg S

Changed 6 years ago by dsd

It is not the USB stick in question, it is the contents of it. sugar has somehow created a corrupt cache, or something has corrupted sugar's cache, and sugar is not dealing with it. If you extract the tarball I added onto *any* blank USB stick then you will reproduce the problem.

Changed 6 years ago by kimquirk

  • keywords blocks-:8.2.0 added; blocks?:8.2.0 removed

I think there is a workaround in that if you find and remove the problem file on the USB, then you will see the rest of the files. If this is not the case, we will need to re-evaluate. If this is true, it is not a blocker.

Should be in release notes.

Changed 6 years ago by marco

Kim is correct.

Changed 6 years ago by marco

  • priority changed from blocker to high

Well, actually you need to remove the index (.olpc.store). But I suppose that's equivalent for the blocker status of this bug.

Changed 6 years ago by marco

  • keywords 8.2.0:- added; 8.2.0:? removed
  • milestone changed from 8.2.0 (was Update.2) to 9.1.0
Note: See TracTickets for help on using tickets.