-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-9.5
-
None
-
None
-
None
-
rhel-sst-storage-io
-
ssg_filesystems_storage_and_HA
-
4
-
False
-
-
None
-
None
-
None
-
None
-
-
x86_64
-
None
What were you trying to do that didn't work?
On systems that boot from SAN over NVMe-TCP or NVMe-FC, it is quite easy to make the system inoperable by issuing a 'nvme disconnect-all". For instance, after issuing the disconnect on a system which boots over NVMe-FC, the console reports the following:
[ 103.827323] block nvme1n1: no available path - failing I/O [ 103.827337] nvme1n1p4: writeback error on inode 67250623, offset 90112, sector 59489176 [ 103.827342] block nvme1n1: no available path - failing I/O [ 103.827346] nvme1n1p4: writeback error on inode 67250623, offset 94208, sector 59489184 [ 103.832144] XFS (nvme1n1p2): Block device removal (0x20) detected at fs_bdev_mark_dead+0x43/0x60 (fs/xfs/xfs_super.c:1179). Shutting down filesystem. [ 103.832152] XFS (nvme1n1p2): Please unmount the filesystem and rectify the problem(s) [ 103.832200] block nvme1n1: no available path - failing I/O [ 103.832204] XFS (nvme1n1p4): log I/O error -5 [ 103.832206] XFS (nvme1n1p4): Filesystem has been shut down due to log error (0x2). [ 103.832207] XFS (nvme1n1p4): Please unmount the filesystem and rectify the problem(s).
Would it be possible for nvme-cli to prevent this from occurring or to present a warning to the end user?
Please provide the package NVR for which bug is seen:
RHEL-9.5.0-20240610.35
nvme-cli-2.9.1-2.el9
