On Fri, Sep 16, 2016 at 8:57 AM, Jeffrey Michels <jeffr...@skyward.com> wrote:
> I have a system that has been in production for a few years. The SAN the VM
> was running on had a hardware failure about a month ago and now one of the
> two btrfs filesystems will remount after boot read-only. Here is the system
> uname -a
> Linux retain 3.0.101-0.47.71-default #1 SMP Thu Nov 12 12:22:22 UTC 2015
> (b5b212e) x86_64 x86_64 x86_64 GNU/Linux
> Btrfs --version
> Btrfs v0.20+
Impressive that it's been running in production this long and with old
kernel. I like it!
Anyway, you could try mounting with -o recovery and see if that works.
That's about the only thing I'd trust with such an old kernel and
btrfs-progs. I don't even think it's worth trying the btrfsck on v0.20
just to see what the problems might be, and certainly not for actually
using the repair mode. Actually I'm not even sure progs that old even
does repairs, it might be the era of notify only.
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.
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
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html