Ticket #2080 (closed bug: fixed)

Opened 9 months ago

Last modified 6 months ago

Mount point not removed

Reported by: andreasf Owned by: stippi
Priority: normal Milestone: R1
Component: Applications/DriveSetup Version: R1 development
Cc: Blocked By:
Platform: x86 Blocking:

Description

When unmounting a volume from DriveSetup, its mount point is not removed.

This leads to a multitude of numbered directories when mounting and unmounting the same volume multiple times.

When unmounting through Tracker, the directory is gone, as expected.

Change History

follow-up: ↓ 2   Changed 9 months ago by stippi

  • status changed from new to assigned

Good point. I am using BPartition::Unmount() directly, but it is BVolume which takes care of removing the mount point if it is called the same as the partition. I should just switch to using that...

in reply to: ↑ 1   Changed 9 months ago by bonefish

Replying to stippi:

Good point. I am using BPartition::Unmount() directly, but it is BVolume which takes care of removing the mount point if it is called the same as the partition. I should just switch to using that...

Or adjust BPartition::Unmount(). Maybe add a boolean removeMountPoint flag?

follow-up: ↓ 4   Changed 9 months ago by axeld

There is no BVolume::Unmount(), actually. Tracker just deletes the mount point manually. Of course, if Mount() creates the mount point, Unmount() should remove it - otherwise it really shouldn't, though (as you might want to mount a volume not on root level).

in reply to: ↑ 3   Changed 9 months ago by bonefish

Replying to axeld:

There is no BVolume::Unmount(), actually. Tracker just deletes the mount point manually. Of course, if Mount() creates the mount point, Unmount() should remove it - otherwise it really shouldn't, though (as you might want to mount a volume not on root level).

Mount() gets the mount point as optional argument. If one is given it expects it to exist. If not given, the standard mount point is created. Hence my suggestion to add a flag to Unmount().

  Changed 6 months ago by andreasf

Sounds like r26593 might have resolved this issue?

  Changed 6 months ago by stippi

  • status changed from assigned to closed
  • resolution set to fixed

Yes, thanks. Fixed in r26593.

Note: See TracTickets for help on using tickets.