Date: Sun, 18 May 2003 20:17:00 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: andy@siliconlandmark.com Cc: current@FreeBSD.org Subject: Re: 5.1-BETA umount problems Message-ID: <200305190317.h4J3H0M7066994@gw.catspoiler.org> In-Reply-To: <20030518225640.S28986@alpha.siliconlandmark.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18 May, Andre Guibert de Bruet wrote: > Hi, > > Have a look at the following: > > bling# umount -f /lib > bling# umount -f /var > bling# umount -f /tmp > bling# df > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/ad4s1a 253678 114254 119130 49% / > devfs 1 1 0 100% /dev > /dev/ad4s1f 188308574 5989134 167254756 3% /usr > /dev/ad2 236514322 134812068 82781110 62% /lib/oldbackup > /lib/oldbackup has about 130GB worth of dumps in it, none of which are > displayed in ls. /dev/ad2 becomes unmountable because it's busy and > /lib/oldbackup contains nothing because it's unmounted. Is there a trick > to get out of this catch-22? All filesystems in bling are UFS2. I suspect nothing short of a reboot will get you out of this jam. IMHO, "umount -f /lib" should have failed in this case.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305190317.h4J3H0M7066994>