From owner-freebsd-questions@freebsd.org Sat Jul 25 18:56:56 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E701F9ABE1C for ; Sat, 25 Jul 2015 18:56:56 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AA6FB1FF2 for ; Sat, 25 Jul 2015 18:56:56 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by igk11 with SMTP id 11so25977466igk.1 for ; Sat, 25 Jul 2015 11:56:56 -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=1s76XO4NhlliTBqE+nz0cZc+Q+9EL29G7PjBvEZzco8=; b=p+Gotja1526of+kZ+HoE69AjtfI2Y+y3k1YgWk6ynjHe1SmbxhKBgigtLUoqWLFuun Y6WKTayWcNxpttXUspbbbmcPseyvD8AZdFC/qxr6ZLcTY0+woHEBoTpHEaTefiuzVzTu CibYra5Gddu6WomnoFIoay7TR6Zd/VhiI9EslfSBlC0d79UaxPYXqrUBHBBw6CwuB46f 5xVjSaNI9DBcuYKEkWIx4hN1kOWYZ0Aj3QBqzbkTxtrqnpCqUHooC1RZU057UB91uNW1 D96d89F4EU9Azmf/fMDV0guQg39owoFAu1uMorxNG2PkbOii8xbgYDiea2b8CaQShg0e KE1w== MIME-Version: 1.0 X-Received: by 10.107.27.195 with SMTP id b186mr30335091iob.140.1437850616064; Sat, 25 Jul 2015 11:56:56 -0700 (PDT) Received: by 10.36.38.133 with HTTP; Sat, 25 Jul 2015 11:56:55 -0700 (PDT) In-Reply-To: References: <0MRCCJ-1ZUCcr1rAt-00UeQk@mail.gmx.com> Date: Sat, 25 Jul 2015 11:56:55 -0700 Message-ID: Subject: Re: Endless Data Loss From: Adrian Chadd To: CeDeROM Cc: CK , FreeBSD Questions Mailing List Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 18:56:57 -0000 I've had the opposite experience - after the last couple rounds of fixes in -HEAD, I've had zero issues with SU+J on all my -HEAD laptops/desktops. (And yes, I kernel panic the laptops frequently..) -adrian