Hi!
This is not an exact open-iscsi question, but tighlty related:
On a SAN using FibreChannel I had a 4-way multipath device. The basic
configuration (without aliases for devices) is:
devices {
device {
vendor HP
product HSV2.*
On 05/12/2011 01:30 AM, Ulrich Windl wrote:
Hi!
This is not an exact open-iscsi question, but tighlty related:
On a SAN using FibreChannel I had a 4-way multipath device. The basic
configuration (without aliases for devices) is:
devices {
device {
vendor HP
Hello,
the problem I am having is, that luckily I was able to correctly set-
up the whole iSCSI-environment, the disk is successfully mounted on my
initiator and everything seemed to be as expected.
However, when I now copy a file from the initiator to the target (via
the mounted folder) I can see
On 2011. May 12. 13:10:10 Adnan Pasic wrote:
the problem I am having is, that luckily I was able to correctly set-
up the whole iSCSI-environment, the disk is successfully mounted on my
initiator and everything seemed to be as expected.
However, when I now copy a file from the initiator to the
Ouch! You are doing disk sharing via iSCSI, and you are using a non-cluster
filesystem? Ouch!
Lucky that the pieces are not flying around your head already (i.e. kernel
panic, data corruption)
Regards,
Ulrich
Adnan Pasic pq...@yahoo.de schrieb am 12.05.2011 um 13:10 in Nachricht
the mounted folder) I can see this file afterwards only on the
initiator, but not on the target. Means, I open a Terminal on the
The basic rule is that if you are going to export storage to a single
machine, use iSCSI. If you need shared storage, use NFS instead.
You could consider a shared
