From: Chris Murphy <lists@colorremedies.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Jeffrey Michels <jeffreym@skyward.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Filesystem will remount read-only
Date: Fri, 16 Sep 2016 18:56:47 -0600 [thread overview]
Message-ID: <CAJCQCtQGOQ0=vmkGeDBBRug05jD1_Chm_=JQf+V+AJpym8JrUw@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtSxcVuE_ZFNvHR=4gF5hDaYTYoav_yV_wEbdjeEfrpOTw@mail.gmail.com>
On Fri, Sep 16, 2016 at 6:08 PM, Chris Murphy <lists@colorremedies.com> wrote:
>
> If -o recovery doesn't work, you'll need to use something newer, you
> could use one of:
>
> Fedora Rawhide nightly with 4.8rc6 kernel and btrfs-progs 4.7.2. This
> is a small netinstall image. dd to a USB stick, choose Troubleshooting
> option, then the Rescue option, then after startup use the 3 option to
> get to a shell where you can try to mount normally, or use
> btrfs-check. Limited tty, no sshd.
> https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20160914.n.0/compose/Everything/x86_64/iso/Fedora-Everything-netinst-x86_64-Rawhide-20160914.n.0.iso.n.0.iso
>
> Or something more official with published hash's for the image and a
> GUI, Fedora 24 workstation has kernel 4.5.5 and btrfs-progs 4.5.2
> https://getfedora.org/en/workstation/download/
Just to complete the thought... use these just to boot and have access
to something newer. I'm not suggesting install them. First try a
normal mount, and if that fails, try -o recovery, if that fails, I'm
curious about
btrfs rescue super-recover -v <dev>
btrfs check <dev>
What I'm after is a way to get it to mount cleanly with a new kernel,
and then hoping you can then just reboot with the ancient kernel and
it'll be back to normal.
--
Chris Murphy
next prev parent reply other threads:[~2016-09-17 0:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 14:57 Filesystem will remount read-only Jeffrey Michels
2016-09-16 23:18 ` Duncan
2016-09-17 0:08 ` Chris Murphy
2016-09-17 0:56 ` Chris Murphy [this message]
2016-09-21 15:24 ` Jeffrey Michels
2016-09-21 15:49 ` Chris Murphy
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='CAJCQCtQGOQ0=vmkGeDBBRug05jD1_Chm_=JQf+V+AJpym8JrUw@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=jeffreym@skyward.com \
--cc=linux-btrfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).