From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f54.google.com ([209.85.218.54]:35836 "EHLO mail-oi0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752651AbcIMVG5 (ORCPT ); Tue, 13 Sep 2016 17:06:57 -0400 Received: by mail-oi0-f54.google.com with SMTP id w11so31211325oia.2 for ; Tue, 13 Sep 2016 14:06:57 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <3756c0ee-4f64-7974-932c-0a1615c658c8@gmail.com> References: <53969836-4a5a-f842-6156-3f88a78bfc4e@gmail.com> <3756c0ee-4f64-7974-932c-0a1615c658c8@gmail.com> From: Chris Murphy Date: Tue, 13 Sep 2016 15:06:55 -0600 Message-ID: Subject: Re: Filesystem forced to readonly after use To: Cesar Strauss Cc: "Austin S. Hemmelgarn" , Btrfs BTRFS Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: >>From the fsck... bad block 160420741120 I can't tell though if that's a bad Btrfs leaf/node where both dup copies are bad; or if it's a bad sector. I'd mount it ro, and take a backup of anything you care about before proceeding further. smartctl -x might reveal if there are problems the drive itself is aware of.