Ticket #2629 (new defect)

Opened 7 years ago

Last modified 7 years ago

Removable media with lots of data cannot be unmounted

Reported by: Zack Owned by: tomeu
Priority: high Milestone: Future Release
Component: sugar-datastore Version:
Keywords: Cc: Zack
Action Needed: Verified: no
Deployments affected: Blocked By:

Description (last modified by Zack) (diff)

The journal tries to index everything on a removable disk when it is inserted. It also doesn't allow that disk to be removed while this is happening. It's been chugging away on my 1GB stick for a several minutes, and for a large disk this could take ages. When an unmount is requested, indexing should stop.

Change History

Changed 7 years ago by Zack

  • description modified (diff)

Unmount failure feedback filed as #2630.

Changed 7 years ago by jg

  • milestone changed from Untriaged to Trial-3

Changed 7 years ago by tomeu

  • owner changed from tomeu to bcsaller
  • component changed from journal-activity to datastore

This is really a DS issue.

Ben, I think it passes a long time between a file is going to be processed and the converter notices it cannot be indexed.

I suspect the whole file is being read into memory before the process fails and moves to the next file. Is this correct? Perhaps we could just read the first N bytes if the converter fails and we want to check if it's a text file.

Apart from this, a request to unmount a device that is being imported should stop the import process and unmount it right away.

Changed 7 years ago by tomeu

  • milestone changed from Trial-3 to Untriaged

When a fix for #3058 is in, we won't have this issue in trial3.

Changed 7 years ago by kimquirk

  • milestone changed from Untriaged to First Deployment, V1.0

Moving to FRS to re-evaluate after Trial-3.

Changed 7 years ago by marco

  • milestone changed from First Deployment, V1.0 to V1.1

We won't have content indexing for 1.0, so I guess this won't be an issue.

Note: See TracTickets for help on using tickets.