> Steve Cowling   wrote:
> 
> The following error was scrolled down the screen: 
> bread in fat_access not found 
> We are running Redhat version 6 on a PC and it has been running fine 
> for about 6 months. The latest work done has been to start using CVS 
> which was installed with the initial installation of Redhat. CVS has 
> been working fine for about a week. Since the bread error appeared we 
> are unable to login either at the console or remotely using telnet 
> from windows. Every time we try to login the "login incorrect" error 
> appears. We have tried all user names and root. The strange thing is 
> that we can still use CVS from our Windows machines using WinCVS 
> 1.0.6 to login and check files in and out. 
> I'm not 100% curtain that CVS is the problem but the machine was
> fine 
> until we started using it.
> Basically we can't login normally at all. 
> Has any body seen this before? Or know what `bread' is? 
> Any help or suggestions would be greatly appreciated. 
> Steve Cowling
        [smc]  First off, I'm no expert, but, bread 
        probably means "Block read", fat_access, 
        might have something to do with reading 
        a DOS/Windows FAT filesystem.  I'm 
        guessing that your password file (or the 
        authentication system somewhere) is 
        corrupted.  You probably have a separate 
        CVS password file in the repository that's 
        not corrupted, and that's why you can still 
        use CVS.  Things that rely on the system 
        authtentication mechanisms (e.g. login, 
        telnet, ftp, etc.) are hosed.  (I'm just 
        guessing here.)

        Is your CVS repository on the same disk 
        as the root filesystem?

        If so, you may want to take out the disk, 
        mount it on another system, and copy
        your repository and anything else valuable 
        that you are able to copy over to a new 
        disk before attempting to repair (or reinstall) 
        over what appears to me to be corruption.

        If you mount the filesystem on another 
        system, it may become obvious what's wrong.
        (oh, attempts to read /mnt/etc/shadow are 
        greeted by I/O errors or something.)

        However, I'm no expert, so you may want a 
        2nd opinion.


Reply via email to