Opened 12 years ago

Closed 12 years ago

#1694 closed bug (fixed)

Not able to unmount other Beos partition

Reported by: cebif Owned by: axeld
Priority: normal Milestone: R1/alpha1
Component: Applications/Tracker Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

With testing on hrev23236 I am unable to unmount other Beos partition. It does not matter how I try to unmount it either by highlighting it with right click and moving mouse then clicking unmount, right clicking on the desktop moving mouse to mount then the sub menu mounted volume name and clicking on that. When I do it the second way a box comes up saying the volume could not be unmount because there is an operation with a file or files on that volume or similar words. I have finised with all file operations like copying to or from.

Change History (11)

comment:1 by cebif, 12 years ago

Component: - GeneralFile Systems/BFS

I have uploaded some shots of The Message Windows and also a KDL that resulted from me trying to open folders in the unmountable partition from previous unmount attempt. One thing I noticed, was that the folders were not showing any contents, after me trying several folders. The attachments are in the order of sequence that I tried things.

comment:2 by cebif, 12 years ago

I have just re uploaded the "KDL After Trying to Open Folders in Beos Partition after Previous Unmount Try" attachment. The previous one was not very clear for reading. Also for the order in which I tried things this attachment should be after the first attachment not the last.

by bonefish, 12 years ago

Attachment: tracker-unmount-kdebug added

KDL Session

comment:3 by bonefish, 12 years ago

I added a panic() in fs_unmount() and analyzed the problem a bit in the kernel debugger (attached debug session). Apparently the AutoMounter thread, who tries to unmount the volume, opens its root directory just before, so that the root vnode is still referenced.

Unmounting with "unmount" from the terminal works as it should.

comment:4 by axeld, 12 years ago

Component: File Systems/BFS- Applications/Tracker
Milestone: R1R1/alpha
Status: newassigned

comment:5 by stippi, 12 years ago

volume.Unset(); ?

comment:6 by axeld, 12 years ago

Resolution: fixed
Status: assignedclosed

Thanks for the work, bonefish! It's fixed in hrev23685.

Note: See TracTickets for help on using tickets.