From owner-freebsd-questions Sun Aug 10 13:18:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA11947 for questions-outgoing; Sun, 10 Aug 1997 13:18:20 -0700 (PDT) Received: from barnes1.wustl.edu (barnes1.wustl.edu [128.252.162.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA11940 for ; Sun, 10 Aug 1997 13:18:17 -0700 (PDT) Received: (from wayne@localhost) by barnes1.wustl.edu (8.8.5/8.7.3) id PAA08219 for freebsd-questions@freebsd.org; Sun, 10 Aug 1997 15:15:04 -0500 (CDT) From: "Wayne M. Barnes" Message-Id: <199708102015.PAA08219@barnes1.wustl.edu> Subject: NFS ignores mount point. It's happening again. To: freebsd-questions@freebsd.org Date: Sun, 10 Aug 1997 15:15:03 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dear FreeBSDers, mount newcomputer:/ /newcomputer (cd /usr; tar cf - .)|(cd /newcomputer/usr; tar xvf -) df on new computer shows / filling up, and /usr not changing at all. The NFS mount is ignoring and disrespecting the mount points on newcomputer. The tar copy is filling up /, ***under the /usr mount point*** Is this misbehaviour, or what? Is this a bug in mount, NFS, tar, or me? Wayne M. Barnes, Ph.D. wayne@barnes1.wustl.edu Biochemistry Dept. 8231 or barnes@biodec.wustl.edu Washington Univ. Medical School 314.362.3351 fax 7183 660 South Euclid Ave., St. Louis, MO 63110 http://barnes1.wustl.edu Just plain Taq is old tech anymore. -------Previous mail on this subject: ------------- Subject: slash filesystem full identified To: dnelson@emsphone.com (Dan Nelson) Dear Dan, Brilliant! There's a lot of stuff there. (bin, include, lib, libdata, libexec). I was able to go into fixit mode using the 2d "live" CDrom, delete the offending under-usr, then make usr over again empty, then reboot. Thank you, Dan! I wonder how all that stuff got there? This was a very fresh install. About the only thing I have tried to do with this computer (and not succeeded) is to tar-copy everything over from my other computer, (running 2.2.1, having mounted this 2.2.2 / directory as an NFS drive on the 2.2.1 mountpoint /newcomputer with root-writing privileges. It is as if the NFS mounting ignored the new computer's mounting on the /usr mount point, and "under-wrote" it. I tried to untar to /usr from the 2.2.1 computer to the new 2.2.2 computer. I gave a command like (cd /; tar cf - .) | (cd /newcomputer; tar xf -) & The tar command began to fail, (I think now because it was using the wrong usr directory). If I try this again, and it happens again, you will hear from me again, because this doesn't sound right to me. Wayne M. Barnes, Ph.D. wayne@barnes1.wustl.edu > In the last episode (Aug 05), Wayne M. Barnes said: > > Dear FreeBSD, > > > > Why is my / filesystem unusably full? I can't account > > for more than 13.3 MB, and I have room for 52 MB, yet it > > is unwritably full. > > > > #df > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > /dev/wd0a 51791 51791 -4143 109% / > > /dev/wd0s3e 2129022 260555 1698146 13% /usr > > /dev/wd0s3f 29727 486 26863 2% /var > > procfs 4 4 0 100% /proc > > > > #du -sx > > 13227 . > > Try unmounting /usr and /var (and /proc if you can), and see if there > are any files underneath the mount points. > > -Dan Nelson > dnelson@emsphone.com > >