From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: "James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
bvanassche@acm.org, hare@suse.de, hch@lst.de,
ming.lei@redhat.com, sumanesh.samanta@broadcom.com,
michael.christie@oracle.com, john.garry@huawei.com,
johannes.thumshirn@wdc.com, axboe@kernel.dk, osandov@fb.com,
kashyap.desai@broadcom.com, gregkh@linuxfoundation.org
Subject: scsi: Recent kernels drop into emergency shell
Date: Mon, 20 Feb 2023 11:45:59 +0530 [thread overview]
Message-ID: <20230220061559.GJ159593@linux.vnet.ibm.com> (raw)
On a freshly installed system, booting latest upstream kernels causes the
system to drop into emergency shell. The reason for dropping into emergency
shell is system is unable to mount /home partition.
The system was able to boot properly on v5.18 kernel, but failed to boot
v5.19 and 6.2-rc8 kernels.
On the recent or failing kernels, I see the below msg when kernel drops into
emergency shell.
lvm[1370]: /dev/sda3 excluded: device is not in devices file.
lvm[1370]: WARNING: no autoactivation for /dev/sda3: system.devices naa.60050768108001b3a800000000000097 current missing device id.
systemd[1]: dev-mapper-rhel_ltcden3\x2d\x2dlp9\x2dhome.device: Job dev-mapper-rhel_ltcden3\x2d\x2dlp9\x2dhome.device/start timed out.
systemd[1]: Timed out waiting for device /dev/mapper/rhel_ltcden3--lp9-home.
systemd[1]: Dependency failed for /home.
systemd[1]: Dependency failed for Local File Systems.
systemd[1]: Dependency failed for Mark the need to relabel after reboot.
systemd[1]: selinux-autorelabel-mark.service: Job selinux-autorelabel-mark.service/start failed with result 'dependency'.
systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
systemd[1]: home.mount: Job home.mount/start failed with result 'dependency'.
systemd[1]: dev-mapper-rhel_ltcden3\x2d\x2dlp9\x2dhome.device: Job dev-mapper-rhel_ltcden3\x2d\x2dlp9\x2dhome.device/start failed with result 'timeout'.
lsblk o/p when system has fallen into ememrgency shell (aka bad kernel)
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 100G 0 disk
ââsda1 8:1 0 4M 0 part
ââsda2 8:2 0 1G 0 part /boot
ââsda3 8:3 0 99G 0 part
âârhel_ltcden3--lp9-root 253:0 0 63.8G 0 lvm /
âârhel_ltcden3--lp9-swap 253:1 0 4G 0 lvm [SWAP]
sr0 11:0 1 1024M 0 rom
lsblk o/p when system boots normally on v5.18 or earlier kernels
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 100G 0 disk
ââsda1 8:1 0 4M 0 part
ââsda2 8:2 0 1G 0 part /boot
ââsda3 8:3 0 99G 0 part
âârhel_ltcden3--lp9-root 253:0 0 63.8G 0 lvm /
âârhel_ltcden3--lp9-swap 253:1 0 4G 0 lvm [SWAP]
âârhel_ltcden3--lp9-home 253:2 0 31.2G 0 lvm /home
sr0 11:0 1 1024M 0 rom
lvdisplay o/p when system has fallen into emergency shell (aka bad kernel)
Devices file sys_wwid naa.60050768108001b3a800000000000097 PVID iws5FZqBFBVE12w874dFuppLWkQUyEcb last seen on /dev/sda3 not found.
lvdisplay o/p when system boots normally on v5.18 or earlier kernels
--- Logical volume ---
LV Path /dev/rhel_ltcden3-lp9/swap
LV Name swap
VG Name rhel_ltcden3-lp9
LV UUID pzxuKG-ofVC-7jBY-HXn9-RDPN-G3hP-K5gdcI
LV Write Access read/write
LV Creation host, time ltcden3-lp9, 2023-01-24 09:44:21 +0530
LV Status available
# open 2
LV Size <4.01 GiB
Current LE 1026
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
--- Logical volume ---
LV Path /dev/rhel_ltcden3-lp9/home
LV Name home
VG Name rhel_ltcden3-lp9
LV UUID XDcVN6-kP6V-0LtL-nLM4-rvLv-gMQm-uaDRwi
LV Write Access read/write
LV Creation host, time ltcden3-lp9, 2023-01-24 09:44:26 +0530
LV Status available
# open 1
LV Size 31.16 GiB
Current LE 7977
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2
--- Logical volume ---
LV Path /dev/rhel_ltcden3-lp9/root
LV Name root
VG Name rhel_ltcden3-lp9
LV UUID sJlMVf-eE2v-UKJp-Esqg-uxis-wA1Y-gOXFnO
LV Write Access read/write
LV Creation host, time ltcden3-lp9, 2023-01-24 09:44:36 +0530
LV Status available
# open 1
LV Size 63.82 GiB
Current LE 16339
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
git bisect start '--'
# bad: [3d7cb6b04c3f3115719235cc6866b10326de34cd] Linux 5.19
git bisect bad 3d7cb6b04c3f3115719235cc6866b10326de34cd
# good: [4b0986a3613c92f4ec1bdc7f60ec66fea135991f] Linux 5.18
git bisect good 4b0986a3613c92f4ec1bdc7f60ec66fea135991f
# bad: [c011dd537ffe47462051930413fed07dbdc80313] Merge tag 'arm-soc-5.19' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
git bisect bad c011dd537ffe47462051930413fed07dbdc80313
# good: [7e062cda7d90543ac8c7700fc7c5527d0c0f22ad] Merge tag 'net-next-5.19' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
git bisect good 7e062cda7d90543ac8c7700fc7c5527d0c0f22ad
# good: [f8122500a039abeabfff41b0ad8b6a2c94c1107d] Merge branch 'etnaviv/next' of https://git.pengutronix.de/git/lst/linux into drm-next
git bisect good f8122500a039abeabfff41b0ad8b6a2c94c1107d
# good: [2518f226c60d8e04d18ba4295500a5b0b8ac7659] Merge tag 'drm-next-2022-05-25' of git://anongit.freedesktop.org/drm/drm
git bisect good 2518f226c60d8e04d18ba4295500a5b0b8ac7659
# good: [f7a344468105ef8c54086dfdc800e6f5a8417d3e] ASoC: max98090: Move check for invalid values before casting in max98090_put_enab_tlv()
git bisect good f7a344468105ef8c54086dfdc800e6f5a8417d3e
# bad: [fbe86daca0ba878b04fa241b85e26e54d17d4229] Merge tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
git bisect bad fbe86daca0ba878b04fa241b85e26e54d17d4229
# bad: [f304d35e59958ea4be399f78e5be08d4a0c4db75] scsi: mpi3mr: Update driver version to 8.0.0.69.0
git bisect bad f304d35e59958ea4be399f78e5be08d4a0c4db75
# good: [21c2e3418d07955c7b87fc3f75688cb1c2b04a32] scsi: ufs: Remove the TRUE and FALSE definitions
git bisect good 21c2e3418d07955c7b87fc3f75688cb1c2b04a32
# good: [671a52f2aeafe2f42bddb53dcfe3933b1f641843] scsi: fnic: Remove unneeded flush_workqueue()
git bisect good 671a52f2aeafe2f42bddb53dcfe3933b1f641843
# bad: [d657700ccac71da19a4d1a591fafcd598ce0dd6e] scsi: core: Do not truncate INQUIRY data on modern devices
git bisect bad d657700ccac71da19a4d1a591fafcd598ce0dd6e
# good: [c5acd61dbb32b6bda0f3a354108f2b8dcb788985] scsi: megaraid: Fix error check return value of register_chrdev()
git bisect good c5acd61dbb32b6bda0f3a354108f2b8dcb788985
# good: [dc1178767cba9d67f5100fb370670fd613319362] scsi: mpt3sas: Use cached ATA Information VPD page
git bisect good dc1178767cba9d67f5100fb370670fd613319362
# bad: [e17d63403076affccd72d195f93bbf3f39514005] scsi: core: Pick suitable allocation length in scsi_report_opcode()
git bisect bad e17d63403076affccd72d195f93bbf3f39514005
# bad: [c92a6b5d63359dd6d2ce6ea88ecd8e31dd769f6b] scsi: core: Query VPD size before getting full page
git bisect bad c92a6b5d63359dd6d2ce6ea88ecd8e31dd769f6b
# first bad commit: [c92a6b5d63359dd6d2ce6ea88ecd8e31dd769f6b] scsi: core: Query VPD size before getting full page
Commit c92a6b5d6335 ("scsi: core: Query VPD size before getting full page")
went in between v5.18 and v5.19.
Verifications:
I have verified that reverting the said bad commit on top of v6.2-rc8, v5.19
and on top of c92a6b5d63359dd6d2ce6ea88ecd8e31dd769f6b causes the system to
boot normally.
--
Thanks and Regards
Srikar Dronamraju
next reply other threads:[~2023-02-20 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 6:15 Srikar Dronamraju [this message]
2023-02-20 6:22 ` scsi: Recent kernels drop into emergency shell Srikar Dronamraju
2023-02-20 7:40 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-20 11:23 ` Srikar Dronamraju
2023-02-20 11:48 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-05 13:29 ` Linux regression tracking #update (Thorsten Leemhuis)
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=20230220061559.GJ159593@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=johannes.thumshirn@wdc.com \
--cc=john.garry@huawei.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@oracle.com \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.com \
--cc=sumanesh.samanta@broadcom.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 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.