Re: FreeBSD 5.x and Bad File Descriptor errors. Why?
On Wed, Dec 03, 2003 at 01:43:57PM +0200, Dan Naumov wrote: Hello What follows is a description of a problem I used to have when running FreeBSD 5.0 and 5.1. I am not running FreeBSD right now, but I am considering going back to it but I need to figure out how to prevent this issue from happening again. My system has 2 harddrives, a 16 GB Seagate that I use for backups and mount it under /mnt/backup and a 40 GB Maxtor that I am using for everything else. After the installation of the OS (usually about 8-12 days of running non-stop) I start getting Bad File Descriptor errors on random files all around the Maxtor drive and I have to go to single-user mode in order to run a full fsck on the system. After that, the system works, until in 8-12 days time even more files get corrupted this way and the process has to be repeated. Eventually, so many files are damaged that a full OS reinstall is required. You get that error from what command(s)? Have you tried with 5.2, which has a new ATA driver? Kris pgp0.pgp Description: PGP signature
Re: FreeBSD 5.x and Bad File Descriptor errors. Why?
Kris Kennaway wrote You get that error from what command(s)? Have you tried with 5.2, which has a new ATA driver? Kris I usually discover that I am having data corruption when trying to update ports. A file that has a Bad File Descriptor refuses to let cvsup overwrite and/or remove itself. I've also had make installworld fail on me for the very same reason. A file in the base system would get corrupted and would prevent anything from overwriting itself. These problems would go away after a full system fsck, but the fsck would remove the damaged files completely, sometimes leaving the system in a severely broken state. And even if it did not, data corruption would happen again in 8-12 days. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.x and Bad File Descriptor errors. Why?
On Wed, Dec 03, 2003 at 05:55:29PM +0200, Dan Naumov wrote: Kris Kennaway wrote You get that error from what command(s)? Have you tried with 5.2, which has a new ATA driver? Kris I usually discover that I am having data corruption when trying to update ports. A file that has a Bad File Descriptor refuses to let cvsup overwrite and/or remove itself. I've also had make installworld fail on me for the very same reason. A file in the base system would get corrupted and would prevent anything from overwriting itself. These problems would go away after a full system fsck, but the fsck would remove the damaged files completely, sometimes leaving the system in a severely broken state. And even if it did not, data corruption would happen again in 8-12 days. Are there any other console or system messages logged? It sounds like there should be some other error reported by the kernel before the userland command receives the EBADF. Kris pgp0.pgp Description: PGP signature
Re: FreeBSD 5.x and Bad File Descriptor errors. Why?
Dan Naumov wrote: What follows is a description of a problem I used to have when running FreeBSD 5.0 and 5.1. [...] After the installation of the OS (usually about 8-12 days of running non-stop) I start getting Bad File Descriptor errors on random files all around the Maxtor drive and I have to go to single-user mode in order to run a full fsck on the system. After that, the system works, until in 8-12 days time even more files get corrupted this way and the process has to be repeated. Eventually, so many files are damaged that a full OS reinstall is required. I had exactly the same experiences while using the same FreeBSD versions. The filesystems slowly died without any direct sign pointing to hardware problems. But, after having exchanged the harddisk with a newer one, the effect never occured again. k.j. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.x and Bad File Descriptor errors. Why?
On Wed, 3 Dec 2003, Dan Naumov wrote: causing this bizarre behavior ? If this is of any help, the exact model number of the HD is MAXTOR 4K040H2 and I was using UFS2 on both drives. Thanks in advance. Maxtor has a diag tool that goes onto a floppy that you could run. I have this exact disk in my sparc64 here and the first time I used it, it kept running over bad sectors and generally causing mayhem. Running the full scan with the tool, it prompted to fix some problems, then the bad sectors went away. I reinstalled the OS to clear out the broken files and I never had any problems afterward. The program is called PowerMax and is available from the downloads section under either diagnostics or utilities. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.x and Bad File Descriptor errors. Why?
Doug White wrote: Maxtor has a diag tool that goes onto a floppy that you could run. I have this exact disk in my sparc64 here and the first time I used it, it kept running over bad sectors and generally causing mayhem. Running the full scan with the tool, it prompted to fix some problems, then the bad sectors went away. I reinstalled the OS to clear out the broken files and I never had any problems afterward. The program is called PowerMax and is available from the downloads section under either diagnostics or utilities. I've tried running PowerMax on the drive with a through scan but no errors were found. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]