From owner-freebsd-questions@FreeBSD.ORG Fri Dec 8 21:21:48 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2922D16A40F for ; Fri, 8 Dec 2006 21:21:48 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9707D43CAA for ; Fri, 8 Dec 2006 21:20:42 +0000 (GMT) (envelope-from bahamasfranks@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so798442uge for ; Fri, 08 Dec 2006 13:21:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=hotYHLgyY3JbMv5zZTr3zgNYtwhAzbtF6bqk5GeKCaV9OpeyxilBUX8NjksSOlKX9U65MfUABs2T5/GXBRUIo87ca4Fq/0jKDL4SNiwtPZYSP95aw4zzRvSy1PBWpVHO25+RPOu7g9zXGofOpoeoO92Aks8DdFEJQMsuYqFPFiY= Received: by 10.82.113.6 with SMTP id l6mr625412buc.1165612900945; Fri, 08 Dec 2006 13:21:40 -0800 (PST) Received: by 10.82.175.3 with HTTP; Fri, 8 Dec 2006 13:21:40 -0800 (PST) Message-ID: <539c60b90612081321g79dc7068j1c0cb87d9724e571@mail.gmail.com> Date: Fri, 8 Dec 2006 14:21:40 -0700 From: "Steve Franks" Sender: bahamasfranks@gmail.com To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: 5450362dedb0ba07 Subject: acpi woes and dead filesystem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Dec 2006 21:21:48 -0000 So, I got my desktop system (read: personal cpu, not a server) all set up, been using it for a couple weeks, all is happy. Now, I'm a bit of a tree-hugger, see, so I tend to like to suspend my computers insted of leaving them on perpetually. As such, tried acpiconf -s3 initially (others say unsupported). Seemed to go down ok, but coming back up it reboots every time. Ho hum. So I follow the handbook and go apm -Z, but that barely saves any power (can still hear disk, fan, etc, although screen blanks (apm -z also casues a reboot) Reanabled acpi -s3, lo, it appears to work, except, first time, only X comes back (not vtty's). Second time X doesn't come back either. Try ctl-alt-del, try suspend button, etc, no choice but to power down. I should mention at this point, that being paranoid, I habitually set all my fstab's to rw,sync, not just rw, which makes my next finding somewhat suprising to me: Upon power up, I am informed my filesystem is toast, and all I get is a shell. My question: besides searching for sympathy, does anyone know how to truly protect a system against unplanned powerdown and/or crash during disk acess? Not to compare apples and oranges, but I've been shutting down my windows systems by the 'pull the plug' method for years now, and I've never had a corrupted filesystem. I supose this could be because windows is just sloppy and doesn't care if ntfs is trashed, as long as the ntldr, etc, is not in the trashed location. Short of never suspending my system, I'd like a nicer way of preventing this. Course it appears I can't trully suspend my system more than once anyway, so perhaps it's moot. Steve