From owner-freebsd-questions@FreeBSD.ORG Wed Jan 26 19:57:20 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 833F516A4CE for ; Wed, 26 Jan 2005 19:57:20 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3454D43D3F for ; Wed, 26 Jan 2005 19:57:20 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7039F516BA; Wed, 26 Jan 2005 11:57:19 -0800 (PST) Date: Wed, 26 Jan 2005 11:57:19 -0800 From: Kris Kennaway To: "Terry R. Friedrichsen" Message-ID: <20050126195719.GC11116@xor.obsecurity.org> References: <200501261250.j0QCo2tT041759@uplift.hosp.misyshealthcare.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4ZLFUWh1odzi/v6L" Content-Disposition: inline In-Reply-To: <200501261250.j0QCo2tT041759@uplift.hosp.misyshealthcare.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 5.3 file system troubles X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 19:57:20 -0000 --4ZLFUWh1odzi/v6L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 26, 2005 at 05:50:02AM -0700, Terry R. Friedrichsen wrote: >=20 > Is anybody besides *me* having file system corruption problems with FreeB= SD > 5.3? I've looked around on several of the mailing lists and found no men- > tion of this. >=20 > I have two different platforms on which I'm trying to run FreeBSD 5.3. O= ne > is an x86 SMP system (dual AMD Athlon 1900+) and the other is an Alpha DS= -10. >=20 > On the SMP system, doing anything I/O intensive (like a kernel build) qui= ckly > corrupts the file system - I start to encounter problems like being unabl= e to > remove entire directory trees because the system thinks that empty direct= ories > are not *really* empty and therefore cannot be deleted. Other problems o= ccur, > too. Drop to single-user mode and run fsck -fy. Sometimes fsck will fail to detect disk corruption at boot time and it will cause problems later on. > On the Alpha system, I'm trying to get Xorg to work, with no success. It's quite possible no-one else has tested this. alpha is no longer a tier-1 architecture because of lack of developer interest. Kris --4ZLFUWh1odzi/v6L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB9/YeWry0BWjoQKURAszdAKCvykJvkwbvZTlJJ+OIRBdmMRxBgACeL6sk qSd9eI0aRFCB+Ez42S3KdF4= =Tbu5 -----END PGP SIGNATURE----- --4ZLFUWh1odzi/v6L--