Return to BSD News archive
From: "Jay Rothschild" <jay@ais.net> Subject: Re: Bad file descriptor Newsgroups: comp.unix.bsd.freebsd.misc References: <01bc4f22$8ba41540$32a19acf@jay> Organization: RTI Message-ID: <01bc4f35$d3860d10$32a19acf@jay> X-Newsreader: Microsoft Internet News 4.70.1160 NNTP-Posting-Host: jay.netrti.net Date: 22 Apr 97 15:57:26 GMT Lines: 17 Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!solace!nntp.uio.no!news.radio.cz!CESspool!europa.clark.net!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!ais.net!news3.ais.net!jay.netrti.net Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:39566 Never Mind... I figured out to unmount the dev and fsck fixed it up Jay Rothschild <jay@ais.net> wrote in article <01bc4f22$8ba41540$32a19acf@jay>... > > On a FreeBSD 2.2.1 machine with Adaptec 2940 UW, & Quantum Atlas II 4.5GB > UW, the daily security check found this: > checking setuid files and devices: > find: /home1: Bad file descriptor > find: /home1: Bad file descriptor > > Luckily nothing in that directory, but I would like to get that 2gb back. > The directory is visible with an ls /, but not visible with an ls -l /. Any > ideas on how to fix this? > >