Date: Mon, 11 Jun 2007 21:24:30 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Bill Moran <wmoran@potentialtech.com> Cc: freebsd-questions@freebsd.org, Modulok <modulok@gmail.com> Subject: Re: umount -f Message-ID: <20070612012430.GA6276@rot13.obsecurity.org> In-Reply-To: <20070611201714.35153d92.wmoran@potentialtech.com> References: <64c038660706111652p311c6d84i1ec295edcfc16994@mail.gmail.com> <20070611201714.35153d92.wmoran@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 11, 2007 at 08:17:14PM -0400, Bill Moran wrote: > Modulok <modulok@gmail.com> wrote: > > > > Couple questions for anyone on the list who has a moment (and the answer to > > any of these): > > > > Objective: I need to kick people off of a storage drive (we'll say > > /dev/ad4), without corrupting the file system and without bringing the > > entire system down. I need to safely umount the file systems, even if my > > users have processes which have files open. > > > > 1. If I use "umount -f /dev/ad4s1a" to forcefully umount a file system, does > > this jeopardize the integrity of said file system? Like...will it jerk the > > run out from under a process in the middle of a disk write, thus leaving a > > half written file, or will it wait until the write is complete? (I guess > > this would largely depend on the disk controller?) > > I don't believe there are any guarantees if your -f it. The filesystem > will probably be OK, but I would expect files to get corrupt. Shouldn't happen, if it does it's a bug. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070612012430.GA6276>