From: keith.busch@intel.com (Keith Busch)
Subject: "Couldn't open file /tmp/nvme-skip"
Date: Mon, 25 Jan 2016 15:37:35 +0000 [thread overview]
Message-ID: <20160125153734.GB31221@localhost.localdomain> (raw)
In-Reply-To: <2268CE55-80F6-42C6-8D5D-18DCC2AFD75E@cisco.com>
On Sat, Jan 23, 2016@04:10:32AM +0000, Joshua Dotson -T (josdotso - SELECT GROUP LLC THE@Cisco) wrote:
>
> Hi folks.
>
> Could you give any hint as to what this message means, as seen in the logs during a PXE boot, and also how to safely avoid it? I don?t have a lot of details on the matter, as I?m investigating on behalf of a colleague, but I also cannot find a reference to this file anywhere in my searches of Google, Github, Linux kernel source, nvme-cli, RedHat Bugzilla, Ubuntu Launchpad.
>
> I suppose the message might emit from a custom script in the mix in my colleague?s environment, but at this point that doesn?t seem the case.
The message looks like a custom artifact from the environment.
prev parent reply other threads:[~2016-01-25 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 4:10 "Couldn't open file /tmp/nvme-skip" Joshua Dotson -T (josdotso - SELECT GROUP LLC THE@Cisco)
2016-01-25 15:37 ` Keith Busch [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=20160125153734.GB31221@localhost.localdomain \
--to=keith.busch@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox