What does “no device” mean when running iostat -En
We presume to have a faulty cable that connects the SAN to a direct I/O LDOM. This is a snippet of the error when running iostat -En
c5t60060E8007C50E000030C50E00001067d0 Soft Errors: 0 Hard Errors: 696633 Transport Errors: 704386
Vendor: HITACHI Product: OPEN-V Revision: 8001 Serial No: 504463
Size: 214.75GB <214748364800 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 6 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
What does No Device: 6 mean here?
solaris disk iostat san
asked Mar 5 at 22:01
hoveyhovey
82
add a comment |
We presume to have a faulty cable that connects the SAN to a direct I/O LDOM. This is a snippet of the error when running iostat -En
c5t60060E8007C50E000030C50E00001067d0 Soft Errors: 0 Hard Errors: 696633 Transport Errors: 704386
Vendor: HITACHI Product: OPEN-V Revision: 8001 Serial No: 504463
Size: 214.75GB <214748364800 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 6 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
What does No Device: 6 mean here?
solaris disk iostat san
asked Mar 5 at 22:01
hoveyhovey
82
What HBA/device driver are you using?
– Andrew Henle
Mar 5 at 23:07
HBA Port WWN: 21000024ff470f2e OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 371-4522-02 Firmware Version: 8.05.00 FCode/BIOS Version: BIOS: 2.10; fcode: 3.06; EFI: 2.04; Serial Number: 0402T00-1232085736 Driver Name: qlc Driver Version: 170516-5.06c Type: N-port State: online Supported Speeds: 2Gb 4Gb 8Gb Current Speed: 8Gb Node WWN: 20000024ff470f2e Link Error Statistics: Link Failure Count: 4386
– hovey
Mar 6 at 1:18
add a comment |
We presume to have a faulty cable that connects the SAN to a direct I/O LDOM. This is a snippet of the error when running iostat -En
c5t60060E8007C50E000030C50E00001067d0 Soft Errors: 0 Hard Errors: 696633 Transport Errors: 704386
Vendor: HITACHI Product: OPEN-V Revision: 8001 Serial No: 504463
Size: 214.75GB <214748364800 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 6 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
What does No Device: 6 mean here?
solaris disk iostat san
asked Mar 5 at 22:01
hoveyhovey
82
We presume to have a faulty cable that connects the SAN to a direct I/O LDOM. This is a snippet of the error when running iostat -En
c5t60060E8007C50E000030C50E00001067d0 Soft Errors: 0 Hard Errors: 696633 Transport Errors: 704386
Vendor: HITACHI Product: OPEN-V Revision: 8001 Serial No: 504463
Size: 214.75GB <214748364800 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 6 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
What does No Device: 6 mean here?
solaris disk iostat san
solaris disk iostat san
asked Mar 5 at 22:01
hoveyhovey
82
asked Mar 5 at 22:01
hoveyhovey
82
asked Mar 5 at 22:01
hoveyhovey
82
asked Mar 5 at 22:01
hoveyhovey
82
asked Mar 5 at 22:01
hoveyhovey
82
82
What HBA/device driver are you using?
– Andrew Henle
Mar 5 at 23:07
HBA Port WWN: 21000024ff470f2e OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 371-4522-02 Firmware Version: 8.05.00 FCode/BIOS Version: BIOS: 2.10; fcode: 3.06; EFI: 2.04; Serial Number: 0402T00-1232085736 Driver Name: qlc Driver Version: 170516-5.06c Type: N-port State: online Supported Speeds: 2Gb 4Gb 8Gb Current Speed: 8Gb Node WWN: 20000024ff470f2e Link Error Statistics: Link Failure Count: 4386
– hovey
Mar 6 at 1:18
add a comment |
What HBA/device driver are you using?
– Andrew Henle
Mar 5 at 23:07
HBA Port WWN: 21000024ff470f2e OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 371-4522-02 Firmware Version: 8.05.00 FCode/BIOS Version: BIOS: 2.10; fcode: 3.06; EFI: 2.04; Serial Number: 0402T00-1232085736 Driver Name: qlc Driver Version: 170516-5.06c Type: N-port State: online Supported Speeds: 2Gb 4Gb 8Gb Current Speed: 8Gb Node WWN: 20000024ff470f2e Link Error Statistics: Link Failure Count: 4386
– hovey
Mar 6 at 1:18
What HBA/device driver are you using?
– Andrew Henle
Mar 5 at 23:07
What HBA/device driver are you using?
– Andrew Henle
Mar 5 at 23:07
HBA Port WWN: 21000024ff470f2e OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 371-4522-02 Firmware Version: 8.05.00 FCode/BIOS Version: BIOS: 2.10; fcode: 3.06; EFI: 2.04; Serial Number: 0402T00-1232085736 Driver Name: qlc Driver Version: 170516-5.06c Type: N-port State: online Supported Speeds: 2Gb 4Gb 8Gb Current Speed: 8Gb Node WWN: 20000024ff470f2e Link Error Statistics: Link Failure Count: 4386– hovey
Mar 6 at 1:18
HBA Port WWN: 21000024ff470f2e OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 371-4522-02 Firmware Version: 8.05.00 FCode/BIOS Version: BIOS: 2.10; fcode: 3.06; EFI: 2.04; Serial Number: 0402T00-1232085736 Driver Name: qlc Driver Version: 170516-5.06c Type: N-port State: online Supported Speeds: 2Gb 4Gb 8Gb Current Speed: 8Gb Node WWN: 20000024ff470f2e Link Error Statistics: Link Failure Count: 4386– hovey
Mar 6 at 1:18
add a comment |
1 Answer
1
active
oldest
votes
A search through the Illumos fiber-channel device code for ENODEV shows 13 uses of ENODEV in the source code that originated as OpenSolaris.
Of those instances, I suspect this is the one most likely to cause your "No device" errors:
pd = fctl_hold_remote_port_by_pwwn(port, &pwwn);
if (pd == NULL) {
fcio->fcio_errno = FC_BADDEV;
return (ENODEV);
}
That code is in the fp_fcio_login() function, where the code appears to be trying to login to a remote WWN. It seems appropriate to assume a bad cable could prevent that from happening. Note that fiber-channel error code is FC_BADDEV, which also seems appropriate for a bad cable.
In short, a review of the source code indicates that ENODEV errors are consistent a bad cable.
You can use dTrace to more closely identify the association if necessary. Given that both hard and transport errors occur about 5 or 6 orders of magnitude more frequently, IMO that effort isn't necessary until the ENODEV errors occur after the other errors are addressed and no longer occur.
answered Mar 6 at 11:27
Andrew HenleAndrew Henle
2,787911
Thanks. So is 'No Device' a counter of sorts?
– hovey
Mar 6 at 20:30
In this case, the number you are seeing is a count of the number of times that error code was returned when something didn't work. But if you look at your total number of errors, you have 6 "No device" errors likely generated when your system had trouble connecting to a remote disk controller/LUN compared to 1.4 million hard and transfer errors.
– Andrew Henle
Mar 8 at 13:42
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f504585%2fwhat-does-no-device-mean-when-running-iostat-en%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
A search through the Illumos fiber-channel device code for ENODEV shows 13 uses of ENODEV in the source code that originated as OpenSolaris.
Of those instances, I suspect this is the one most likely to cause your "No device" errors:
pd = fctl_hold_remote_port_by_pwwn(port, &pwwn);
if (pd == NULL) {
fcio->fcio_errno = FC_BADDEV;
return (ENODEV);
}
That code is in the fp_fcio_login() function, where the code appears to be trying to login to a remote WWN. It seems appropriate to assume a bad cable could prevent that from happening. Note that fiber-channel error code is FC_BADDEV, which also seems appropriate for a bad cable.
In short, a review of the source code indicates that ENODEV errors are consistent a bad cable.
You can use dTrace to more closely identify the association if necessary. Given that both hard and transport errors occur about 5 or 6 orders of magnitude more frequently, IMO that effort isn't necessary until the ENODEV errors occur after the other errors are addressed and no longer occur.
answered Mar 6 at 11:27
Andrew HenleAndrew Henle
2,787911
Thanks. So is 'No Device' a counter of sorts?
– hovey
Mar 6 at 20:30
In this case, the number you are seeing is a count of the number of times that error code was returned when something didn't work. But if you look at your total number of errors, you have 6 "No device" errors likely generated when your system had trouble connecting to a remote disk controller/LUN compared to 1.4 million hard and transfer errors.
– Andrew Henle
Mar 8 at 13:42
add a comment |
A search through the Illumos fiber-channel device code for ENODEV shows 13 uses of ENODEV in the source code that originated as OpenSolaris.
Of those instances, I suspect this is the one most likely to cause your "No device" errors:
pd = fctl_hold_remote_port_by_pwwn(port, &pwwn);
if (pd == NULL) {
fcio->fcio_errno = FC_BADDEV;
return (ENODEV);
}
That code is in the fp_fcio_login() function, where the code appears to be trying to login to a remote WWN. It seems appropriate to assume a bad cable could prevent that from happening. Note that fiber-channel error code is FC_BADDEV, which also seems appropriate for a bad cable.
In short, a review of the source code indicates that ENODEV errors are consistent a bad cable.
You can use dTrace to more closely identify the association if necessary. Given that both hard and transport errors occur about 5 or 6 orders of magnitude more frequently, IMO that effort isn't necessary until the ENODEV errors occur after the other errors are addressed and no longer occur.
answered Mar 6 at 11:27
Andrew HenleAndrew Henle
2,787911
Thanks. So is 'No Device' a counter of sorts?
– hovey
Mar 6 at 20:30
In this case, the number you are seeing is a count of the number of times that error code was returned when something didn't work. But if you look at your total number of errors, you have 6 "No device" errors likely generated when your system had trouble connecting to a remote disk controller/LUN compared to 1.4 million hard and transfer errors.
– Andrew Henle
Mar 8 at 13:42
add a comment |
A search through the Illumos fiber-channel device code for ENODEV shows 13 uses of ENODEV in the source code that originated as OpenSolaris.
Of those instances, I suspect this is the one most likely to cause your "No device" errors:
pd = fctl_hold_remote_port_by_pwwn(port, &pwwn);
if (pd == NULL) {
fcio->fcio_errno = FC_BADDEV;
return (ENODEV);
}
That code is in the fp_fcio_login() function, where the code appears to be trying to login to a remote WWN. It seems appropriate to assume a bad cable could prevent that from happening. Note that fiber-channel error code is FC_BADDEV, which also seems appropriate for a bad cable.
In short, a review of the source code indicates that ENODEV errors are consistent a bad cable.
You can use dTrace to more closely identify the association if necessary. Given that both hard and transport errors occur about 5 or 6 orders of magnitude more frequently, IMO that effort isn't necessary until the ENODEV errors occur after the other errors are addressed and no longer occur.
answered Mar 6 at 11:27
Andrew HenleAndrew Henle
2,787911
A search through the Illumos fiber-channel device code for ENODEV shows 13 uses of ENODEV in the source code that originated as OpenSolaris.
Of those instances, I suspect this is the one most likely to cause your "No device" errors:
pd = fctl_hold_remote_port_by_pwwn(port, &pwwn);
if (pd == NULL) {
fcio->fcio_errno = FC_BADDEV;
return (ENODEV);
}
That code is in the fp_fcio_login() function, where the code appears to be trying to login to a remote WWN. It seems appropriate to assume a bad cable could prevent that from happening. Note that fiber-channel error code is FC_BADDEV, which also seems appropriate for a bad cable.
In short, a review of the source code indicates that ENODEV errors are consistent a bad cable.
You can use dTrace to more closely identify the association if necessary. Given that both hard and transport errors occur about 5 or 6 orders of magnitude more frequently, IMO that effort isn't necessary until the ENODEV errors occur after the other errors are addressed and no longer occur.
answered Mar 6 at 11:27
Andrew HenleAndrew Henle
2,787911
answered Mar 6 at 11:27
Andrew HenleAndrew Henle
2,787911
answered Mar 6 at 11:27
Andrew HenleAndrew Henle
2,787911
answered Mar 6 at 11:27
Andrew HenleAndrew Henle
2,787911
2,787911
Thanks. So is 'No Device' a counter of sorts?
– hovey
Mar 6 at 20:30
In this case, the number you are seeing is a count of the number of times that error code was returned when something didn't work. But if you look at your total number of errors, you have 6 "No device" errors likely generated when your system had trouble connecting to a remote disk controller/LUN compared to 1.4 million hard and transfer errors.
– Andrew Henle
Mar 8 at 13:42
add a comment |
Thanks. So is 'No Device' a counter of sorts?
– hovey
Mar 6 at 20:30
In this case, the number you are seeing is a count of the number of times that error code was returned when something didn't work. But if you look at your total number of errors, you have 6 "No device" errors likely generated when your system had trouble connecting to a remote disk controller/LUN compared to 1.4 million hard and transfer errors.
– Andrew Henle
Mar 8 at 13:42
Thanks. So is 'No Device' a counter of sorts?
– hovey
Mar 6 at 20:30
Thanks. So is 'No Device' a counter of sorts?
– hovey
Mar 6 at 20:30
In this case, the number you are seeing is a count of the number of times that error code was returned when something didn't work. But if you look at your total number of errors, you have 6 "No device" errors likely generated when your system had trouble connecting to a remote disk controller/LUN compared to 1.4 million hard and transfer errors.
– Andrew Henle
Mar 8 at 13:42
In this case, the number you are seeing is a count of the number of times that error code was returned when something didn't work. But if you look at your total number of errors, you have 6 "No device" errors likely generated when your system had trouble connecting to a remote disk controller/LUN compared to 1.4 million hard and transfer errors.
– Andrew Henle
Mar 8 at 13:42
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f504585%2fwhat-does-no-device-mean-when-running-iostat-en%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What HBA/device driver are you using?
– Andrew Henle
Mar 5 at 23:07
HBA Port WWN: 21000024ff470f2e OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 371-4522-02 Firmware Version: 8.05.00 FCode/BIOS Version: BIOS: 2.10; fcode: 3.06; EFI: 2.04; Serial Number: 0402T00-1232085736 Driver Name: qlc Driver Version: 170516-5.06c Type: N-port State: online Supported Speeds: 2Gb 4Gb 8Gb Current Speed: 8Gb Node WWN: 20000024ff470f2e Link Error Statistics: Link Failure Count: 4386– hovey
Mar 6 at 1:18