From: Miklos S. <mi...@sz...> - 2008-07-23 16:53:15
|
On Wed, 23 Jul 2008, Bernd Schubert wrote: > The system won't continue to shutdown - access to all system union mounts > (e.g. /etc, /var, /usr, /bin, /lib and son) doesn't work anymore, so all > other shutdown scripts won't run. I'm also working on elemination of the / > access deadlock, so even / will have the problem in the future. So if those mounts are needed for shutdown, why are they being umounted? What would happen if they weren't busy, so they would get properly umounted, yet some script needed to access the contents later? Having filesystems kept mounted because some process happens to have an open file or a cwd on them seems more of an accident than anything else. > This is with unionfs-fuse, which we use and which I'm working on for entire > system unionfs. And except rather annoying shutdown problems it works quite > well (already for 1.5 years in production on 50 desktop systems and since > several month on all of our HPC cluster system - several hundred systems). > I know how to handle these shutdown problems, but I guess most other admins > don't - so this keeps people away to use unionfs-fuse, which reduces the > chances people will report bugs I don't know about yet ;) Is this problem specific to unionfs-fuse? Thanks, Miklos |