Date: Fri, 21 Mar 1997 11:36:53 -0800 From: "Riley J. McIntire" <rjmcintire@earthlink.net> To: "'questions@freebsd.org'" <questions@freebsd.org> Cc: "'Steve'" <shovey@buffnet.net> Subject: RE: Bad file descriptor in security check output Message-ID: <01BC35EC.2D3CBB00@EMILYD>
next in thread | raw e-mail | index | archive | help
I didn't see anything directly pertinent about chflags. I did do an fsck but still get the bad descriptor message and can't remove the others... I also tried to remove the lost+found dir without luck. Assuming the disk is still usable (how can I test this?--I'm a newbie) it seems to me that I need a more brute force method to get rid of these files? I searched the archives for a recent discussion (I believe on the ISP list) about users running a script that makes an end chain of directories, eg, /x/x/x/x/x/x.... Some of the remedies proposed might solve this, but I can't remember exactly what they were. :( Thanks, Riley ---------- From: Steve Sent: Friday, March 21, 1997 5:55 AM To: Riley J. McIntire Subject: RE: Bad file descriptor in security check output Check the chflags man pages - there might be screwy flags ou have to remove first before you can delete it. otherwise i would move the top dir to some name or aother and replace it so that new stuff doesnt go into the corrupted dir. On Thu, 20 Mar 1997, Riley J. McIntire wrote: > When I try to remove these files I get this: > > bash# rm -i '#'06* > rm: #064448: Bad file descriptor > remove #064456? y > rm: #064456: Operation not permitted > remove #064504? y > rm: #064504: Operation not permitted > remove #064505? y > rm: #064505: Operation not permitted > remove #064513? y > rm: #064513: Operation not permitted > bash# ls -l > ls: #064448: Bad file descriptor > total 0 > cr-srwsrwT 21077 57982986 2315373696 219, -2097151869 Nov 11 1975 #064456 > br-srwSrwt 27506 1845521775 1869640805 116, 1819213941 Nov 4 11:56 #064504 > br-xrws--- 29440 1996515182 1735094895 0, 1380974628 Dec 12 16:53 #064505 > br-xrw-r-- 25902 96561670 9742848 101, 1768161394 May 26 1970 #064513 > > Trying chmod I get the same errors... > > Thanks, > > Riley > > > > > ---------- > From: Doug White > Sent: Thursday, March 20, 1997 1:45 PM > To: rjmcintire@wilshire.net > Cc: freebsd-questions@FreeBSD.ORG > Subject: Re: Bad file descriptor in security check output > > On Wed, 19 Mar 1997, Riley J. McIntire wrote: > > some info on troubleshooting this? > . > . > . > > These are recovered inodes from a bad crash and were recovered by fsck. > If the files are usable to you, then you can rename them; otherwise > they're probably useless and you should remove them. > > . > . > . > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major > > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01BC35EC.2D3CBB00>