From: covici@ccs.covici.com
To: Chris Murphy <lists@colorremedies.com>
Cc: Henk Slager <eye1tm@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs problems on new file system
Date: Sat, 26 Dec 2015 02:29:11 -0500 [thread overview]
Message-ID: <5117.1451114951@ccs.covici.com> (raw)
In-Reply-To: <CAJCQCtTQ-73RbohA9wdrttj_uSnF5f8x1Opa0a6O2ZF-5NVqhQ@mail.gmail.com>
Chris Murphy <lists@colorremedies.com> 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.
--
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
next prev parent reply other threads:[~2015-12-26 7:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-25 10:03 btrfs problems on new file system covici
2015-12-25 19:01 ` Henk Slager
2015-12-25 21:14 ` covici
2015-12-26 3:53 ` Chris Murphy
2015-12-26 7:29 ` covici [this message]
2015-12-26 10:47 ` Duncan
2015-12-26 11:38 ` covici
2015-12-26 19:07 ` Chris Murphy
2015-12-26 19:22 ` covici
2015-12-26 19:50 ` Chris Murphy
2015-12-26 20:02 ` covici
2015-12-26 20:33 ` Chris Murphy
2015-12-26 5:20 ` Duncan
2015-12-26 7:44 ` covici
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5117.1451114951@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=eye1tm@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.