Solaris 11, How to map device to mount point?
Solaris 11,
iostat -xncz 5
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
....
6.0 18.2 226.7 205.6 0.0 0.0 0.0 1.7 0 3 vdc206
6.8 39.6 252.6 341.0 0.0 0.1 0.0 1.5 0 4 vdc207
0.2 30.0 9.4 266.9 0.0 0.0 0.0 1.1 0 1 vdc208
6.6 19.4 242.2 330.1 0.0 0.0 0.0 1.9 0 4 vdc209
6.8 36.4 230.9 371.2 0.0 0.1 0.0 1.4 0 4 vdc210
....
the mounts like, df
...
/S0T1 (ds/S0T1 ): 7815505 blocks 7815505 files
/S0Q1 (ds/S0Q1 ): 9602502 blocks 9602502 files
...
I may want to know how these devices, vdc* mapped to the mounts, /S0*?
solaris
add a comment |
Solaris 11,
iostat -xncz 5
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
....
6.0 18.2 226.7 205.6 0.0 0.0 0.0 1.7 0 3 vdc206
6.8 39.6 252.6 341.0 0.0 0.1 0.0 1.5 0 4 vdc207
0.2 30.0 9.4 266.9 0.0 0.0 0.0 1.1 0 1 vdc208
6.6 19.4 242.2 330.1 0.0 0.0 0.0 1.9 0 4 vdc209
6.8 36.4 230.9 371.2 0.0 0.1 0.0 1.4 0 4 vdc210
....
the mounts like, df
...
/S0T1 (ds/S0T1 ): 7815505 blocks 7815505 files
/S0Q1 (ds/S0Q1 ): 9602502 blocks 9602502 files
...
I may want to know how these devices, vdc* mapped to the mounts, /S0*?
solaris
Can anyone help? Thanks!
– SeanB
Oct 14 at 12:24
add a comment |
Solaris 11,
iostat -xncz 5
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
....
6.0 18.2 226.7 205.6 0.0 0.0 0.0 1.7 0 3 vdc206
6.8 39.6 252.6 341.0 0.0 0.1 0.0 1.5 0 4 vdc207
0.2 30.0 9.4 266.9 0.0 0.0 0.0 1.1 0 1 vdc208
6.6 19.4 242.2 330.1 0.0 0.0 0.0 1.9 0 4 vdc209
6.8 36.4 230.9 371.2 0.0 0.1 0.0 1.4 0 4 vdc210
....
the mounts like, df
...
/S0T1 (ds/S0T1 ): 7815505 blocks 7815505 files
/S0Q1 (ds/S0Q1 ): 9602502 blocks 9602502 files
...
I may want to know how these devices, vdc* mapped to the mounts, /S0*?
solaris
Solaris 11,
iostat -xncz 5
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
....
6.0 18.2 226.7 205.6 0.0 0.0 0.0 1.7 0 3 vdc206
6.8 39.6 252.6 341.0 0.0 0.1 0.0 1.5 0 4 vdc207
0.2 30.0 9.4 266.9 0.0 0.0 0.0 1.1 0 1 vdc208
6.6 19.4 242.2 330.1 0.0 0.0 0.0 1.9 0 4 vdc209
6.8 36.4 230.9 371.2 0.0 0.1 0.0 1.4 0 4 vdc210
....
the mounts like, df
...
/S0T1 (ds/S0T1 ): 7815505 blocks 7815505 files
/S0Q1 (ds/S0Q1 ): 9602502 blocks 9602502 files
...
I may want to know how these devices, vdc* mapped to the mounts, /S0*?
solaris
solaris
edited Oct 13 at 20:58
user88036
asked Oct 13 at 20:57
SeanB
254
254
Can anyone help? Thanks!
– SeanB
Oct 14 at 12:24
add a comment |
Can anyone help? Thanks!
– SeanB
Oct 14 at 12:24
Can anyone help? Thanks!
– SeanB
Oct 14 at 12:24
Can anyone help? Thanks!
– SeanB
Oct 14 at 12:24
add a comment |
1 Answer
1
active
oldest
votes
These are ZFS datasets, correct? If you run zpool status ds, you should see something like
pool: ds
state: ONLINE
scan: ...
config:
NAME STATE READ WRITE CKSUM
ds ONLINE 0 0 0
vdc206 ONLINE 0 0 0
vdc207 ONLINE 0 0 0
The exact structure will depend on the way the pool is constructed. But I'm guessing that the devices are in a mirror or a RAIDZ array, or something similar, in which case there's no way to map the devices to the mountpoints. This is the way ZFS is supposed to work: take a bunch of raw devices, abstract them away, and give you a single pseudo-device (in no Unix sense of the word) from which you can carve out filesystem namespace.
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%2f475308%2fsolaris-11-how-to-map-device-to-mount-point%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
These are ZFS datasets, correct? If you run zpool status ds, you should see something like
pool: ds
state: ONLINE
scan: ...
config:
NAME STATE READ WRITE CKSUM
ds ONLINE 0 0 0
vdc206 ONLINE 0 0 0
vdc207 ONLINE 0 0 0
The exact structure will depend on the way the pool is constructed. But I'm guessing that the devices are in a mirror or a RAIDZ array, or something similar, in which case there's no way to map the devices to the mountpoints. This is the way ZFS is supposed to work: take a bunch of raw devices, abstract them away, and give you a single pseudo-device (in no Unix sense of the word) from which you can carve out filesystem namespace.
add a comment |
These are ZFS datasets, correct? If you run zpool status ds, you should see something like
pool: ds
state: ONLINE
scan: ...
config:
NAME STATE READ WRITE CKSUM
ds ONLINE 0 0 0
vdc206 ONLINE 0 0 0
vdc207 ONLINE 0 0 0
The exact structure will depend on the way the pool is constructed. But I'm guessing that the devices are in a mirror or a RAIDZ array, or something similar, in which case there's no way to map the devices to the mountpoints. This is the way ZFS is supposed to work: take a bunch of raw devices, abstract them away, and give you a single pseudo-device (in no Unix sense of the word) from which you can carve out filesystem namespace.
add a comment |
These are ZFS datasets, correct? If you run zpool status ds, you should see something like
pool: ds
state: ONLINE
scan: ...
config:
NAME STATE READ WRITE CKSUM
ds ONLINE 0 0 0
vdc206 ONLINE 0 0 0
vdc207 ONLINE 0 0 0
The exact structure will depend on the way the pool is constructed. But I'm guessing that the devices are in a mirror or a RAIDZ array, or something similar, in which case there's no way to map the devices to the mountpoints. This is the way ZFS is supposed to work: take a bunch of raw devices, abstract them away, and give you a single pseudo-device (in no Unix sense of the word) from which you can carve out filesystem namespace.
These are ZFS datasets, correct? If you run zpool status ds, you should see something like
pool: ds
state: ONLINE
scan: ...
config:
NAME STATE READ WRITE CKSUM
ds ONLINE 0 0 0
vdc206 ONLINE 0 0 0
vdc207 ONLINE 0 0 0
The exact structure will depend on the way the pool is constructed. But I'm guessing that the devices are in a mirror or a RAIDZ array, or something similar, in which case there's no way to map the devices to the mountpoints. This is the way ZFS is supposed to work: take a bunch of raw devices, abstract them away, and give you a single pseudo-device (in no Unix sense of the word) from which you can carve out filesystem namespace.
answered Dec 11 at 7:12
Danek Duvall
14114
14114
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f475308%2fsolaris-11-how-to-map-device-to-mount-point%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
Can anyone help? Thanks!
– SeanB
Oct 14 at 12:24