From: Roman Mamedov <rm@romanrm.net>
To: Skibbi <skibbi@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: My first attempt to use btrfs failed miserably
Date: Sun, 2 Feb 2020 19:14:05 +0500 [thread overview]
Message-ID: <20200202191405.1b1ad9b3@natsu> (raw)
In-Reply-To: <CACN+yT_AYiLc29M41U+WrQHtk4t==D-4AkH+wRROKJY=WstGAA@mail.gmail.com>
On Sun, 2 Feb 2020 13:45:58 +0100
Skibbi <skibbi@gmail.com> wrote:
> root@rpi4b:~# dmesg |grep btrfs
> [223167.290255] BTRFS: error (device dm-0) in
> btrfs_run_delayed_refs:2935: errno=-5 IO failure
> [223167.389690] BTRFS: error (device dm-0) in
> btrfs_run_delayed_refs:2935: errno=-5 IO failure
> root@rpi4b:~# dmesg |grep BTRFS
Try without that grep, and see if anything else happened to cause these errors.
...
> [203285.469285] BTRFS info (device sda1): read error corrected: ino 0
> off 32759808 (dev /dev/sda1 sector 80368)
> [203285.469515] BTRFS info (device sda1): read error corrected: ino 0
> off 32763904 (dev /dev/sda1 sector 80376)
> [204448.566295] BTRFS: device label NAS devid 1 transid 5 /dev/dm-0
Such as here, doesn't this look like the device may have disconnected and
reappeared (to make btrfs show the "device" message).
--
With respect,
Roman
next prev parent reply other threads:[~2020-02-02 14:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 12:45 My first attempt to use btrfs failed miserably Skibbi
2020-02-02 12:56 ` Qu Wenruo
2020-02-02 13:22 ` Stephan von Krawczynski
2020-02-02 20:04 ` Chris Murphy
2020-02-02 13:29 ` Martin Raiber
2020-02-02 13:36 ` Qu Wenruo
2020-02-02 14:14 ` Roman Mamedov [this message]
2020-02-02 14:45 ` Swâmi Petaramesh
2020-02-02 23:34 ` Zygo Blaxell
2020-02-03 6:28 ` Skibbi
2020-02-03 16:12 ` Chris Murphy
2020-02-03 19:01 ` Marc Joliet
2020-02-03 7:00 ` Swâmi Petaramesh
2020-02-02 19:56 ` Chris Murphy
2020-02-03 6:38 ` Skibbi
2020-02-03 6:51 ` Qu Wenruo
2020-02-03 8:42 ` Skibbi
2020-02-03 10:10 ` Qu Wenruo
2020-02-03 10:17 ` Qu Wenruo
2020-02-03 10:56 ` Skibbi
2020-02-03 11:09 ` Qu Wenruo
2020-02-03 16:17 ` Chris Murphy
2020-02-02 19:57 ` Chris Murphy
2020-02-03 19:14 ` Achim Gratz
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=20200202191405.1b1ad9b3@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=skibbi@gmail.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 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).