Date: Mon, 11 Jun 2007 21:21:52 -0500 From: "illoai@gmail.com" <illoai@gmail.com> To: Modulok <modulok@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: umount -f Message-ID: <d7195cff0706111921l3437c58cx651e2da731619ac@mail.gmail.com> In-Reply-To: <64c038660706111652p311c6d84i1ec295edcfc16994@mail.gmail.com> References: <64c038660706111652p311c6d84i1ec295edcfc16994@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/06/07, Modulok <modulok@gmail.com> wrote: > 3. Is there any safe way to unconditionally umount a file system, even if a > run-away process is writing to it (as bad of an idea as this is)? UFS is refreshingly robust (at least in my experience) in this regard, in that you may end up with a truncated (or slightly mauled) file but never a corrupt filesystem. Even kicking the power cord out only results in minor, repairable corruption something like 30% of the time. Again, in terms of personal experience I would suggest that umount -f is shrug-inducingly "safe" at 3 or 4 nines of the time. -- --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d7195cff0706111921l3437c58cx651e2da731619ac>