iSCSI - Unable to mount external disk on target
up vote
0
down vote
favorite
I use targetcli-fb package
My target is configured on a computer with installed Debian.
Initiator is configured on Virtual Debian System, I use VirtualBox for virtualisation.
I log in to target from initiator. I mount disk
mount /dev/sdb1 /mnt
I then create some trash files on /mnt
nano test.txt
mkdir test
And now I want check /dev/sdb1 on target. I can't mount /dev/sdb1 to /mnt on target. I also tried to mount it before logging from initiator.
I tried to check processess binded to it, but I ask here how to check them. Which information I need deliver to get answer?
How to mount this /dev/sdb1 on target and check what is stored on it? Or how check what is on this disk?
mount: /dev/sdb1 is already mounted or /mnt busy
debian mount iscsi
asked Nov 20 at 11:14
OrdinaryDraft
106
add a comment |
up vote
0
down vote
favorite
I use targetcli-fb package
My target is configured on a computer with installed Debian.
Initiator is configured on Virtual Debian System, I use VirtualBox for virtualisation.
I log in to target from initiator. I mount disk
mount /dev/sdb1 /mnt
I then create some trash files on /mnt
nano test.txt
mkdir test
And now I want check /dev/sdb1 on target. I can't mount /dev/sdb1 to /mnt on target. I also tried to mount it before logging from initiator.
I tried to check processess binded to it, but I ask here how to check them. Which information I need deliver to get answer?
How to mount this /dev/sdb1 on target and check what is stored on it? Or how check what is on this disk?
mount: /dev/sdb1 is already mounted or /mnt busy
debian mount iscsi
asked Nov 20 at 11:14
OrdinaryDraft
106
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I use targetcli-fb package
My target is configured on a computer with installed Debian.
Initiator is configured on Virtual Debian System, I use VirtualBox for virtualisation.
I log in to target from initiator. I mount disk
mount /dev/sdb1 /mnt
I then create some trash files on /mnt
nano test.txt
mkdir test
And now I want check /dev/sdb1 on target. I can't mount /dev/sdb1 to /mnt on target. I also tried to mount it before logging from initiator.
I tried to check processess binded to it, but I ask here how to check them. Which information I need deliver to get answer?
How to mount this /dev/sdb1 on target and check what is stored on it? Or how check what is on this disk?
mount: /dev/sdb1 is already mounted or /mnt busy
debian mount iscsi
asked Nov 20 at 11:14
OrdinaryDraft
106
I use targetcli-fb package
My target is configured on a computer with installed Debian.
Initiator is configured on Virtual Debian System, I use VirtualBox for virtualisation.
I log in to target from initiator. I mount disk
mount /dev/sdb1 /mnt
I then create some trash files on /mnt
nano test.txt
mkdir test
And now I want check /dev/sdb1 on target. I can't mount /dev/sdb1 to /mnt on target. I also tried to mount it before logging from initiator.
I tried to check processess binded to it, but I ask here how to check them. Which information I need deliver to get answer?
How to mount this /dev/sdb1 on target and check what is stored on it? Or how check what is on this disk?
mount: /dev/sdb1 is already mounted or /mnt busy
debian mount iscsi
debian mount iscsi
asked Nov 20 at 11:14
OrdinaryDraft
106
asked Nov 20 at 11:14
OrdinaryDraft
106
asked Nov 20 at 11:14
OrdinaryDraft
106
asked Nov 20 at 11:14
OrdinaryDraft
106
asked Nov 20 at 11:14
OrdinaryDraft
106
106
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
iSCSI is not a file sharing protocol but a block device sharing protocol: Without some serious tricking (a cluster file system) it is not possible to mount the same iSCSI disk on two initiators.
To mount it on an initiator and the target runs into the additional problem, that the target software will exclusivly lock the disk and so prevent a local mount.
If you want to share a disk in the sense of being able to access it from both operating systems at the same time, use a file sharing protocol.
EDIT
If you want to mount the disk on the target side, stop the iSCSI service - this will release the lock.
You can of course force the concurrent use of the disk (by logging into the iSCSI target from the target-sided OS), but if you mount the block device on both sides without using a proper cluster file system, you will lose data. Seriously.
answered Nov 20 at 11:22
Eugen Rieck
9,47722127
1) So I shouldn't mount it on target? 2) I don't see the storage from server/target level? 3) Can I log in to target from target? (to see what is on disk)
– OrdinaryDraft
Nov 20 at 11:29
To make it short: You can always use a shared block device only on one OS at the time without real clustering software.
– Eugen Rieck
Nov 20 at 11:32
See my edit: Unmount from the initator, log out from initiator, stop iSCSI service, then mount on target.
– Eugen Rieck
Nov 20 at 11:37
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
iSCSI is not a file sharing protocol but a block device sharing protocol: Without some serious tricking (a cluster file system) it is not possible to mount the same iSCSI disk on two initiators.
To mount it on an initiator and the target runs into the additional problem, that the target software will exclusivly lock the disk and so prevent a local mount.
If you want to share a disk in the sense of being able to access it from both operating systems at the same time, use a file sharing protocol.
EDIT
If you want to mount the disk on the target side, stop the iSCSI service - this will release the lock.
You can of course force the concurrent use of the disk (by logging into the iSCSI target from the target-sided OS), but if you mount the block device on both sides without using a proper cluster file system, you will lose data. Seriously.
answered Nov 20 at 11:22
Eugen Rieck
9,47722127
1) So I shouldn't mount it on target? 2) I don't see the storage from server/target level? 3) Can I log in to target from target? (to see what is on disk)
– OrdinaryDraft
Nov 20 at 11:29
To make it short: You can always use a shared block device only on one OS at the time without real clustering software.
– Eugen Rieck
Nov 20 at 11:32
See my edit: Unmount from the initator, log out from initiator, stop iSCSI service, then mount on target.
– Eugen Rieck
Nov 20 at 11:37
add a comment |
up vote
1
down vote
accepted
iSCSI is not a file sharing protocol but a block device sharing protocol: Without some serious tricking (a cluster file system) it is not possible to mount the same iSCSI disk on two initiators.
To mount it on an initiator and the target runs into the additional problem, that the target software will exclusivly lock the disk and so prevent a local mount.
If you want to share a disk in the sense of being able to access it from both operating systems at the same time, use a file sharing protocol.
EDIT
If you want to mount the disk on the target side, stop the iSCSI service - this will release the lock.
You can of course force the concurrent use of the disk (by logging into the iSCSI target from the target-sided OS), but if you mount the block device on both sides without using a proper cluster file system, you will lose data. Seriously.
answered Nov 20 at 11:22
Eugen Rieck
9,47722127
1) So I shouldn't mount it on target? 2) I don't see the storage from server/target level? 3) Can I log in to target from target? (to see what is on disk)
– OrdinaryDraft
Nov 20 at 11:29
To make it short: You can always use a shared block device only on one OS at the time without real clustering software.
– Eugen Rieck
Nov 20 at 11:32
See my edit: Unmount from the initator, log out from initiator, stop iSCSI service, then mount on target.
– Eugen Rieck
Nov 20 at 11:37
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
iSCSI is not a file sharing protocol but a block device sharing protocol: Without some serious tricking (a cluster file system) it is not possible to mount the same iSCSI disk on two initiators.
To mount it on an initiator and the target runs into the additional problem, that the target software will exclusivly lock the disk and so prevent a local mount.
If you want to share a disk in the sense of being able to access it from both operating systems at the same time, use a file sharing protocol.
EDIT
If you want to mount the disk on the target side, stop the iSCSI service - this will release the lock.
You can of course force the concurrent use of the disk (by logging into the iSCSI target from the target-sided OS), but if you mount the block device on both sides without using a proper cluster file system, you will lose data. Seriously.
answered Nov 20 at 11:22
Eugen Rieck
9,47722127
iSCSI is not a file sharing protocol but a block device sharing protocol: Without some serious tricking (a cluster file system) it is not possible to mount the same iSCSI disk on two initiators.
To mount it on an initiator and the target runs into the additional problem, that the target software will exclusivly lock the disk and so prevent a local mount.
If you want to share a disk in the sense of being able to access it from both operating systems at the same time, use a file sharing protocol.
EDIT
If you want to mount the disk on the target side, stop the iSCSI service - this will release the lock.
You can of course force the concurrent use of the disk (by logging into the iSCSI target from the target-sided OS), but if you mount the block device on both sides without using a proper cluster file system, you will lose data. Seriously.
answered Nov 20 at 11:22
Eugen Rieck
9,47722127
edited Nov 20 at 11:35
answered Nov 20 at 11:22
Eugen Rieck
9,47722127
answered Nov 20 at 11:22
Eugen Rieck
9,47722127
answered Nov 20 at 11:22
Eugen Rieck
9,47722127
9,47722127
1) So I shouldn't mount it on target? 2) I don't see the storage from server/target level? 3) Can I log in to target from target? (to see what is on disk)
– OrdinaryDraft
Nov 20 at 11:29
To make it short: You can always use a shared block device only on one OS at the time without real clustering software.
– Eugen Rieck
Nov 20 at 11:32
See my edit: Unmount from the initator, log out from initiator, stop iSCSI service, then mount on target.
– Eugen Rieck
Nov 20 at 11:37
add a comment |
1) So I shouldn't mount it on target? 2) I don't see the storage from server/target level? 3) Can I log in to target from target? (to see what is on disk)
– OrdinaryDraft
Nov 20 at 11:29
To make it short: You can always use a shared block device only on one OS at the time without real clustering software.
– Eugen Rieck
Nov 20 at 11:32
See my edit: Unmount from the initator, log out from initiator, stop iSCSI service, then mount on target.
– Eugen Rieck
Nov 20 at 11:37
1) So I shouldn't mount it on target? 2) I don't see the storage from server/target level? 3) Can I log in to target from target? (to see what is on disk)
– OrdinaryDraft
Nov 20 at 11:29
1) So I shouldn't mount it on target? 2) I don't see the storage from server/target level? 3) Can I log in to target from target? (to see what is on disk)
– OrdinaryDraft
Nov 20 at 11:29
To make it short: You can always use a shared block device only on one OS at the time without real clustering software.
– Eugen Rieck
Nov 20 at 11:32
To make it short: You can always use a shared block device only on one OS at the time without real clustering software.
– Eugen Rieck
Nov 20 at 11:32
See my edit: Unmount from the initator, log out from initiator, stop iSCSI service, then mount on target.
– Eugen Rieck
Nov 20 at 11:37
See my edit: Unmount from the initator, log out from initiator, stop iSCSI service, then mount on target.
– Eugen Rieck
Nov 20 at 11:37
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1376937%2fiscsi-unable-to-mount-external-disk-on-target%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
