can't unmount
I'm running into a situation where I can't unmount a mounted
snapshot. It shows "busy" even though neither lsof nor fuser show any open files. Umount -f doesn't work although umount -l does.
Is there anything else I can do to debug this scenario or to clear the busy status myself? Or am I down to rebooting each time?
This is on stock ubuntu-10.04, x86.
--rich
And should I be worried about what umount -l might be leaving behind?
(eg, any unfreed kernel resources) Or is that a reasonable way to deal with this situation on an ongoing basis?
--rich
Quoted 8 lines · K. Richard Pixley
I'm running into a situation where I can't unmount a mounted
snapshot. It shows "busy" even though neither lsof nor fuser show any open files. Umount -f doesn't work although umount -l does.Is there anything else I can do to debug this scenario or to clear the busy status myself? Or am I down to rebooting each time?
This is on stock ubuntu-10.04, x86.
--rich
Quoted 4 lines · K. Richard Pixley
And should I be worried about what umount -l might be leaving behind? (eg, any unfreed kernel resources) Or is that a reasonable way to deal with this situation on an ongoing basis?
Quoted 13 lines
--rich
Quoted 10 lines · K. Richard Pixley
I'm running into a situation where I can't unmount a mounted snapshot. It shows "busy" even though neither lsof nor fuser show any open files. Umount -f doesn't work although umount -l does.
Is there anything else I can do to debug this scenario or to clear the busy status myself? Or am I down to rebooting each time?
This is on stock ubuntu-10.04, x86.
--rich
You are lazy unmounting, as I understand, you are essentially just hiding the fact that the mount was busy to userspace... The mount will remain active in the kernel until you resolve whatever was stopping umount in the first place; kernel will then silently unmount.
Does this affect all of your mounted snapshots, or only a particular one?
C Anthony [mobile]
Quoted 10 lines · C Anthony Risinger
Quoted 9 lines · K. Richard Pixley
And should I be worried about what umount -l might be leaving behind? (eg, any unfreed kernel resources) Or is that a reasonable way to deal with this situation on an ongoing basis?
Quoted 4 lines · K. Richard Pixley
I'm running into a situation where I can't unmount a mounted snapshot. It shows "busy" even though neither lsof nor fuser show any open files. Umount -f doesn't work although umount -l does.
Quoted 8 lines
Quoted 4 lines
Quoted 4 lines
Is there anything else I can do to debug this scenario or to clear the busy status myself? Or am I down to rebooting each time?
This is on stock ubuntu-10.04, x86.
You are lazy unmounting, as I understand, you are essentially just hiding the fact that the mount was busy to userspace... The mount will remain active in the kernel until you resolve whatever was stopping umount in the first place; kernel will then silently unmount.
Understood.
Quoted 2 lines
Does this affect all of your mounted snapshots, or only a particular one?
I'm only mounting one at a time so I haven't noticed. Will check next time it occurs.
--rich
Quoted 21 lines · K. Richard Pixley
Quoted 14 lines · C Anthony Risinger
Quoted 12 lines · K. Richard Pixley
And should I be worried about what umount -l might be leaving behind? (eg, any unfreed kernel resources) Or is that a reasonable way to deal with this situation on an ongoing basis?
Quoted 7 lines · K. Richard Pixley
I'm running into a situation where I can't unmount a mounted snapshot. It shows "busy" even though neither lsof nor fuser show any open files. Umount -f doesn't work although umount -l does.
Is there anything else I can do to debug this scenario or to clear the busy status myself? Or am I down to rebooting each time?
Quoted 6 lines
Quoted 1 line
Quoted 1 line
This is on stock ubuntu-10.04, x86.
You are lazy unmounting, as I understand, you are essentially just hiding the fact that the mount was busy to userspace... The mount will
remain active in the kernel until you resolve whatever was stopping umount in the first place; kernel will then silently unmount.
Quoted 5 lines
Understood.
Quoted 2 lines
Does this affect all of your mounted snapshots, or only a particular one?
I'm only mounting one at a time so I haven't noticed. Will check next time it occurs.
More than likely it's just an open app stopping the mount; make sure any GUI stuff isn't looking at the drive, and no terminals are either. I thought that stuff shows up in lsof, but I swear there are cases when things won't.
C Anthony [mobile]