From: Hannes Reinecke <hare@suse.de>
To: linux-nvme@lists.infradead.org
Subject: Re: [PATCHv2] nvme-mpath: delete disk after last connection
Date: Sat, 1 May 2021 13:59:16 +0200 [thread overview]
Message-ID: <59942a93-3234-2bca-ef67-4ccf9580d073@suse.de> (raw)
In-Reply-To: <20210420141610.GB14300@redsun51.ssa.fujisawa.hgst.com>
On 4/20/21 4:16 PM, Keith Busch wrote:
> On Fri, Apr 16, 2021 at 08:24:11AM +0200, Hannes Reinecke wrote:
>> Now delete all paths to one of the namespaces:
>>
>> # echo 1 > /sys/class/nvme/nvme3/delete_controller
>> # echo 1 > /sys/class/nvme/nvme4/delete_controller
>>
>> We have no path, but mdstat says:
>>
>> # cat /proc/mdstat
>> Personalities : [raid1]
>> md0 : active (auto-read-only) raid1 nvme5n1[1]
>> 64512 blocks super 1.2 [2/1] [_U]
>>
>> And this is reported to cause a problem.
>>
>> With the proposed patch, the following messages appear:
>>
>> [ 227.516807] md/raid1:md0: Disk failure on nvme3n1, disabling device.
>> [ 227.516807] md/raid1:md0: Operation continuing on 1 devices.
>>
>> And mdstat shows only the viable members:
>>
>> # cat /proc/mdstat
>> Personalities : [raid1]
>> md0 : active (auto-read-only) raid1 nvme5n1[1]
>> 64512 blocks super 1.2 [2/1] [_U]
>
> I think there's a copy-paste error in this change log (probably my
> mistake). The first mdstat should have shown nvme3n1 was still there,
> right?
>
Possibly. Will be resending.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2021-05-01 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 6:24 [PATCHv2] nvme-mpath: delete disk after last connection Hannes Reinecke
2021-04-20 8:05 ` Christoph Hellwig
[not found] ` <91f25f95-e5a0-466f-b410-6f6dafdec0a0@email.android.com>
2021-04-20 9:54 ` Christoph Hellwig
2021-04-20 13:19 ` Hannes Reinecke
2021-04-20 14:14 ` Keith Busch
2021-04-20 14:39 ` Christoph Hellwig
2021-04-20 17:02 ` Hannes Reinecke
2021-04-20 17:16 ` Keith Busch
2021-04-20 20:05 ` Martin Wilck
2021-04-20 16:21 ` Hannes Reinecke
2021-04-20 14:16 ` Keith Busch
2021-05-01 11:59 ` Hannes Reinecke [this message]
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=59942a93-3234-2bca-ef67-4ccf9580d073@suse.de \
--to=hare@suse.de \
--cc=linux-nvme@lists.infradead.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