From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from plane.gmane.org ([80.91.229.3]:43274 "EHLO plane.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755832AbaIECKJ (ORCPT ); Thu, 4 Sep 2014 22:10:09 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XPiyR-0006gP-RF for linux-btrfs@vger.kernel.org; Fri, 05 Sep 2014 04:10:03 +0200 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 05 Sep 2014 04:10:03 +0200 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 05 Sep 2014 04:10:03 +0200 To: linux-btrfs@vger.kernel.org From: Duncan <1i5t5.duncan@cox.net> Subject: Re: BTRFS critical (device dm-0): invalid dir item name len: 45389 Date: Fri, 5 Sep 2014 02:07:39 +0000 (UTC) Message-ID: References: <03A7512C-C195-4906-9995-945AF3D76EB2@colorremedies.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: Chris Murphy posted on Thu, 04 Sep 2014 19:41:39 -0600 as excerpted: > Off chance scrub might fix the problem How? He said it's btrfs raid0. There's no second copy to fix from. (Of course if only the data is raid0, metadata being raid1, then if it's metadata yes a scrub could fix it, but that's not what he said...) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman