All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Ritika Srivastava <ritika.srivastava@oracle.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 1/1] lsblk: Ignore hidden devices
Date: Thu, 14 May 2020 15:56:03 +0200	[thread overview]
Message-ID: <20200514135603.oti23br45cw3kzpu@ws.net.home> (raw)
In-Reply-To: <1589407570-25740-1-git-send-email-ritika.srivastava@oracle.com>

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@redhat.com>
 http://karelzak.blogspot.com


      reply	other threads:[~2020-05-14 13:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 22:06 [PATCH 1/1] lsblk: Ignore hidden devices Ritika Srivastava
2020-05-14 13:56 ` Karel Zak [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=20200514135603.oti23br45cw3kzpu@ws.net.home \
    --to=kzak@redhat.com \
    --cc=ritika.srivastava@oracle.com \
    --cc=util-linux@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.