From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail0131.smtp25.com ([75.126.84.131]:39252 "EHLO mail0131.smtp25.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751034AbbLZTWH convert rfc822-to-8bit (ORCPT ); Sat, 26 Dec 2015 14:22:07 -0500 From: covici@ccs.covici.com To: Chris Murphy cc: Duncan <1i5t5.duncan@cox.net>, Btrfs BTRFS Subject: Re: btrfs problems on new file system In-reply-to: References: <16107.1451037790@ccs.covici.com> <18552.1451078098@ccs.covici.com> <5117.1451114951@ccs.covici.com> <25045.1451129900@ccs.covici.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 26 Dec 2015 14:22:02 -0500 Message-ID: <23484.1451157722@ccs.covici.com> Sender: linux-btrfs-owner@vger.kernel.org List-ID: Chris Murphy wrote: > On Sat, Dec 26, 2015 at 4:38 AM, wrote: > > Duncan <1i5t5.duncan@cox.net> wrote: > > > >> covici posted on Sat, 26 Dec 2015 02:29:11 -0500 as excerpted: > >> > >> > Chris Murphy wrote: > >> > > >> >> If you can post the entire dmesg somewhere that'd be useful. MUAs tend > >> >> to wrap that text and make it unreadable on list. I think the problems > >> >> with your volume happened before the messages, but it's hard to say. > >> >> Also, a generation of nearly 5000 is not that new? > >> > > >> > The file system was only a few days old. It was on an lvm volume group > >> > which consisted of two ssd drives, so I am not sure what you are saying > >> > about lvm cache -- how could I do anything different? > >> > > >> >> On another thread someone said you probably need to specify the device > >> >> to mount when using Btrfs and lvmcache? And the device to specify is > >> >> the combined HDD+SSD logical device, for lvmcache that's the "cache > >> >> LV", which is the OriginLV + CachePoolLV. If Btrfs decides to mount the > >> >> origin, it can result in corruption. > >> > > >> > See above. > >> > >> I think he mixed up two threads and thought you were running lvm-cache, > >> not just regular lvm, which should be good unless you're exposing lvm > >> snapshots and thus letting btrfs see multiple supposed UUIDs that aren't > >> actually universal. Since btrfs is multi-device and uses the UUID to > >> track which devices belong to it (because they're _supposed_ to be > >> universally unique, it's even in the _name_!), if it sees the same UUID > >> it'll consider it part of the same filesystem, thus potentially causing > >> corruption if it's a snapshot or something that's not actually supposed > >> to be part of the (current) filesystem. > > > > I found a few more log entries, perhaps these may be helpful to track > > this down, or maybe prevent the filesystem from going read-only. > > No, you need to post the entire dmesg. The "cut here" part is maybe > useful for a developer diagnosing Btrfs's response to the problem, but > the problem, or the pre-problem, happened before this. It would be a 20meg file, if I were to post the whole file. but I can tell you, no hardware errors at any time. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com