From owner-freebsd-stable@FreeBSD.ORG Sat Sep 22 15:26:01 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A8744106564A; Sat, 22 Sep 2012 15:26:01 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 433FF8FC14; Sat, 22 Sep 2012 15:26:00 +0000 (UTC) Received: by vcbfw7 with SMTP id fw7so6361498vcb.13 for ; Sat, 22 Sep 2012 08:26:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tC5IpFXUknYY15bzCwSu+u6gj56f/s68MnzZcxcd5ls=; b=AbqmUKr/I2o0pDfpM58Dqy7d24mT0YcfdlQXKsEwYIzX3iFtRqOQLMOfIqbrmZ/Udr 7AkiD7cuJ8HbZVOsMrpXfAGIlgH5h5ettzo+GvxmvWCiPuJWV7JPFE37VVcSByQdBJtw DAjJDcrS7pHFHACM7sUmWRaf99/W6CgrI2ErrDQuItEFvU/4eujZzXaJG7A5Yfq4eAWE l4ZwHOQUtoN7Ir4l79jPRgNWLeqZOztysSvJo8FFLt55VaxZcMd6AvPROy6qlx3q/eu7 ZuNJDCVamxEY4DKO+F1U2OprU+E9p1hL/DhqiUaE3HaNqEJSPPzQKBEyjkXU5CSGDsTd tUKQ== MIME-Version: 1.0 Received: by 10.52.27.82 with SMTP id r18mr3803143vdg.120.1348327560173; Sat, 22 Sep 2012 08:26:00 -0700 (PDT) Received: by 10.58.249.135 with HTTP; Sat, 22 Sep 2012 08:26:00 -0700 (PDT) In-Reply-To: <12.61.15248.6977D505@smtp01.insight.synacor.com> References: <12.61.15248.6977D505@smtp01.insight.synacor.com> Date: Sat, 22 Sep 2012 08:26:00 -0700 Message-ID: From: Jim Harris To: Thomas Mueller Content-Type: text/plain; charset=ISO-8859-1 Cc: delphij@freebsd.org, freebsd-stable@freebsd.org Subject: Re: tws bug ? (LSI SAS 9750) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Sep 2012 15:26:01 -0000 On Sat, Sep 22, 2012 at 1:32 AM, Thomas Mueller wrote: > > The specific subject of this thread is not my issue, but I did notice > problems apparently related to CAM on a SATA hard drive. > I would suggest starting a new thread if you have a different issue. > I use one UFS partition, with FreeBSD 9.0-BETA1 installed (subsequently > updated on another partition, using GPT as opposed to MBR), for ports tree > and also NetBSD pkgsrc and NetBSD source code. I built NetBSD 5.1_STABLE i386 > from FreeBSD and also built xorg-modular on the new NetBSD installation from > pkgsrc. Going into and out of the newly installed Xorg resulted in some > crashes with the FreeBSD 9.0-BETA1 partition mounted and not cleanly > unmounted. File system was damaged, and FreeBSD fsck_ffs wouldn't fix it, > went into a loop: > > > Script started on Wed Sep 19 04:15:02 2012 > fsck_ffs /dev/ada0p9 > ** /dev/ada0p9 > ** Last Mounted on /BETA1 > ** Phase 1 - Check Blocks and Sizes > > CANNOT READ BLK: 7584192 > CONTINUE? [yn] y > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 7584318, 7584319, > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > 1475900 files, 4638292 used, 21162419 free (61643 frags, 2637597 blocks, 0.2% fragmentation) > > ***** FILE SYSTEM STILL DIRTY ***** > > ***** PLEASE RERUN FSCK ***** > > Script done on Wed Sep 19 04:17:27 2012 > > > This happened repeatedly, meaning an impasse. > > I didn't get to record preceding error messages relating to ATA and CAM but, > seeing this last message, wonder if there are some bugs in the CAM. > > I booted that new NetBSD 5.1_STABLE i386 installation, on a USB stick, was > able to mount that partition and see it wasn't trashed though there was a > message about the dirty flag. I then umounted and ran NetBSD fsck_ffs > successfully, just a few files were lost, and FreeBSD can access that > partition again. > > I still intend to be more cautious when in NetBSD, not mounting a FreeBSD > partition unnecessarily when doing something crash-prone on my system in > NetBSD, such as going into and out of X. > > Tom