On Wed, May 13, 2020 at 03:06:10PM -0700, Ritika Srivastava wrote: > Following patch was added > https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d51f05bfecb299a830897106460bf395be440c0a > Which made lsblk read from /sys/block/<nvmeNcXnY>/device/dev > which do exist for nvmeNcXnY devices. > > After the above patch, the unknown error goes away. > However, another error is encountered in the very next step. > > nvme1c1n1: failed to initialize sysfs handler > > This is because lsblk looks for /sys/dev/block/242:1 > (nvmeNcXnY major:minor) pathname which usually exists for other > block devices but not for the nvmeNcXnY devices as they are hidden. It's interesting that /sys could be inconsistent in /sys/dev/block/ and /sys/block/. Applied, thanks. I did a small change to the patch to make it usable with /sys dumps. https://github.com/karelzak/util-linux/commit/c8487d854ba5cf5bfcae78d8e5af5587e7622351 Karel -- Karel Zak <kzak@xxxxxxxxxx> http://karelzak.blogspot.com
