From: Chris Murphy <lists@colorremedies.com>
To: Alexey Isaev <a.isaev@rqc.ru>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs becomes read-only
Date: Wed, 27 Jan 2021 13:50:45 -0700 [thread overview]
Message-ID: <CAJCQCtQKZFd-evfGhJk6eti1ZjRJFZN8LuNde=499gnF6fLcVA@mail.gmail.com> (raw)
In-Reply-To: <635ef4db-3854-d544-474b-4ecbdea5bc0d@rqc.ru>
On Wed, Jan 27, 2021 at 1:57 AM Alexey Isaev <a.isaev@rqc.ru> wrote:
>
> kernel version:
>
> aleksey@host:~$ sudo uname --all
> Linux host 4.15.0-132-generic #136~16.04.1-Ubuntu SMP Tue Jan 12
> 18:22:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
This is an old and EOL kernel. It could be a long fixed Btrfs bug that
caused this problem, I'm not sure. I suggest 5.4.93+ if you need a
longterm kernel, otherwise 5.10.11 is the current stable kernel.
>
> drive make/model:
>
> Drive is external 5 bay HDD enclosure with raid-5 connected via usb-3
> (made by Orico https://www.orico.cc/us/product/detail/3622.html)
> with 5 WD Red 10 Tb. We use this drive for backups.
>
> When i try to run btrfs check i get error message:
>
> aleksey@host:~$ sudo btrfs check --readonly /dev/sdg
> Couldn't open file system
OK is it now on some other dev node? A relatively recent btrfs-progs
is also recommended, 5.10 is current and I probably wouldn't use
anything older than 5.6.1.
> aleksey@host:~$ sudo smartctl -x /dev/sdg
Yeah probably won't work since it's behind a raid5 controller. I think
there's smartctl commands to enable passthrough and get information
for each drive, so that you don't have to put it in JBOD mode. But I'm
not familiar with how to do that. Anyway it's a good idea to find out
if there's SMART reporting any problems about any drive, but not
urgent.
--
Chris Murphy
next prev parent reply other threads:[~2021-01-27 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 7:08 btrfs becomes read-only Alexey Isaev
2021-01-27 7:38 ` Chris Murphy
2021-01-27 8:57 ` Alexey Isaev
2021-01-27 20:50 ` Chris Murphy [this message]
2021-01-27 13:05 ` Alexey Isaev
2021-01-27 20:54 ` 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='CAJCQCtQKZFd-evfGhJk6eti1ZjRJFZN8LuNde=499gnF6fLcVA@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=a.isaev@rqc.ru \
--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).