Did you mean to type fdisk, or did you really mean fsck? On Fri, 20 Sep 2002, Edward Wildgoose wrote:
> I have a similar problem on one of my machines which has a corrupted inode entry. >Might want to fdisk that drive. > > As an aside I'm not sure how to correct the problem having determined that's whats >wrong. FDisk isn't any help.... > > -----Original Message----- > From: Brenden Walker [mailto:[EMAIL PROTECTED]] > Sent: 20 September 2002 15:57 > To: '[EMAIL PROTECTED]' > Subject: RE: FIND command Locks up Redhat System > > > Hmm, never seen that myself..but.. Is is possible you've got a directory link that >causes directery traversal to recurse forever? > > -----Original Message----- > From: Brice Hamilton [mailto:[EMAIL PROTECTED]] > Sent: Friday, September 20, 2002 10:47 AM > To: [EMAIL PROTECTED] > Subject: FIND command Locks up Redhat System > > > Hello, > > I ran into a problem yesterday with one of my production REDHAT Linux servers. This >particular server is running Oracle DB and is mainly a Database server. I need to >run the standard LINUX/UNIX 'FIND" command to locate a particular file and when I ran >the command, the entire system just locked up ! Dead as a doornail. I was wondering >if anyone out there in the LINUX world has run across this problem, and if so, what >did you do to correct it. Any help is appreciated, thanks. > > Brice Hamilton > Sr. Systems Engineer > Provider HealthNet Services Inc. > (225) 381-6436 > > > -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
