From: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
To: "David H. Rhodes Clymer" <david-LEGOU7lN1jbY0TyS/+Ba5Q@public.gmane.org>
Cc: "linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Bcache (device?) failure
Date: Tue, 29 Jan 2013 11:11:26 -0800 [thread overview]
Message-ID: <20130129191126.GN26407@google.com> (raw)
In-Reply-To: <1359131422.8441.0.camel-BhfXqN+OCyH0JUkrLwYuUYegIDNd2VA9XqFh9Ls21Oc@public.gmane.org>
On Fri, Jan 25, 2013 at 11:30:22AM -0500, David H. Rhodes Clymer wrote:
> Speaking of bcache integrity...This morning, bcache started indicating
> that it was encountering errors writing to the drive.
>
> For some stupid reason, I rebooted, and on boot, it cannot find the
> volume group (I was running LVM on bcache) that my root fs is on,
> finally dropping to the initramfs shell.
>
> I then find that attempting to register my bcache component devices
> fails:
>
> (initramfs) echo /dev/sdb1 > /sys/fs/bcache/register
> sh: write error: invalid argument
> (initramfs) ls /sys/fs/bcache/
> register register_quiet
>
> This happens for both the cache device and the backing store. I realize
> that collecting information prior to a reboot would have been much more
> useful...sorry.
>
> Is there any simple reason why I would be seeing this behavior? I assume
> that either both devices are corrupt, and no longer seen as bcache
> formatted devices. Does that seem likely?
Yeah... you'd have to check the dmesg log to be sure, but the most
likely cause for that is bcache isn't finding a bcache superblock :/
prev parent reply other threads:[~2013-01-29 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 16:30 Bcache (device?) failure David H. Rhodes Clymer
[not found] ` <1359131422.8441.0.camel-BhfXqN+OCyH0JUkrLwYuUYegIDNd2VA9XqFh9Ls21Oc@public.gmane.org>
2013-01-29 19:11 ` Kent Overstreet [this message]
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=20130129191126.GN26407@google.com \
--to=koverstreet-hpiqsd4aklfqt0dzr+alfa@public.gmane.org \
--cc=david-LEGOU7lN1jbY0TyS/+Ba5Q@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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.