Messages in this thread | | | Date | Fri, 31 Dec 2004 09:48:41 -0800 | From | Ush <> | Subject | Re: the umount() saga for regular linux desktop users |
| |
On Fri, 31 Dec 2004 17:41:02 +0000, William <wh@designed4u.net> wrote: > Regularly, when attempting to umount() a filesystem I receive 'device is busy' > errors. The only way (that I have found) to solve these problems is to go on > a journey into processland and kill all the guilty ones that have tied > themselves to the filesystem concerned.
Even a lazy umount doesn't work? "umount -l <filesystem-name>"
> In my opinion, in order for linux to be trully user friendly, "a umount() > should NEVER fail" (even if the device containing the filesystem is no > longuer attached to the system). The kernel should do it's best to satisfy > the umount request and cleanup. Maybe the kernel could try some of the > following:
Would it be user-friendly if this forcible umount caused the user to lose data?
Oisin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |