Date: Mon, 16 Apr 2001 09:54:20 -0700 (PDT) From: fredette@mit.edu To: freebsd-gnats-submit@FreeBSD.org Subject: kern/26618: unmount(2) can't unmount a filesystem whose device has been lost Message-ID: <200104161654.f3GGsKe25243@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 26618 >Category: kern >Synopsis: unmount(2) can't unmount a filesystem whose device has been lost >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Apr 16 10:00:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Matthew Fredette >Release: 4.2_RELEASE >Organization: self >Environment: FreeBSD test1.home 4.2-RELEASE FreeBSD 4.2-RELEASE #7: Fri Apr 13 17:11:46 EDT 2001 root@home:/usr/src/sys/compile/TEST1 i386 >Description: unmount(2) can't unmount a filesystem on a device that has been lost. When the namei() call on the mountpoint fails with ENXIO, unmount gives up and returns immediately. >How-To-Repeat: Mount a single filesystem read-only from a SCSI disk. Power down the disk, use 'camcontrol rescan' as appropriate to lose the device. Now try to unmount the filesystem. >Fix: When namei() returns ENXIO on the mountpoint, umount could walk the list of mounted filesystems looking for the mountpoint itself. I'll attach a patch to this PR that does this in a followup email. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200104161654.f3GGsKe25243>