From: Chris Murphy <lists@colorremedies.com>
To: Eric Levy <contact@ericlevy.name>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: parent transid verify failed
Date: Fri, 31 Dec 2021 16:09:58 -0700 [thread overview]
Message-ID: <CAJCQCtRxkZ4NjQA9KrOvb_ybDE-sg_BzzMU=91fT_p8gMEKw6Q@mail.gmail.com> (raw)
In-Reply-To: <baa90652685a400aa60636f8596e3d28304da1ad.camel@ericlevy.name>
Dec 29 21:01:09 hostname kernel: sd 4:0:0:1: Warning! Received an
indication that the LUN assignments on this target have changed. The
Linux SCSI layer does not automatical
...
Dec 30 03:47:10 hostname kernel: sd 4:0:0:1: rejecting I/O to offline device
Dec 30 03:47:10 hostname kernel: blk_update_request: I/O error, dev
sdc, sector 523542288 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio
class 0
Can you tell us more about /dev/sdc a.k.a. scsi 4:0:0:1? Because this
device seems to be in a bad state, and is rejecting writes.
--
Chris Murphy
next prev parent reply other threads:[~2021-12-31 23:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 21:10 parent transid verify failed Eric Levy
2021-12-30 21:47 ` Chris Murphy
2022-01-01 15:11 ` devel
2021-12-31 19:14 ` Zygo Blaxell
2021-12-31 20:33 ` Eric Levy
2021-12-31 23:09 ` Chris Murphy [this message]
2022-01-01 7:33 ` Eric Levy
2022-01-01 20:49 ` Chris Murphy
2022-01-01 21:57 ` Eric Levy
2022-01-01 20:56 ` Zygo Blaxell
2022-01-01 21:58 ` Eric Levy
2022-01-02 0:15 ` Zygo Blaxell
2022-01-02 0:55 ` Eric Levy
2022-01-02 3:27 ` Zygo Blaxell
2022-01-02 4:03 ` Eric Levy
2022-01-02 5:57 ` Zygo Blaxell
2022-01-02 10:17 ` Eric Levy
2022-01-03 7:41 ` Chris Murphy
2022-01-02 7:31 ` Andrei Borzenkov
-- strict thread matches above, loose matches on Subject: below --
2017-05-11 10:01 Massimo B.
[not found] <E18363B1-CD81-41F4-A03C-4D09AA669915@plack.net>
2015-04-28 12:34 ` Anthony Plack
2010-09-06 17:28 Jan Steffens
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='CAJCQCtRxkZ4NjQA9KrOvb_ybDE-sg_BzzMU=91fT_p8gMEKw6Q@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=contact@ericlevy.name \
--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 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.