Re: Changes made on iSCSI disk are not shown on initiator
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 storage file system like Oracle's ASM, but they aren't so easy to deal with. NFS4 has locking, user authentication, and everything you need built into the protocol. Mark -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Antw: Changes made on iSCSI disk are not shown on initiator
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 schrieb am 12.05.2011 um 13:10 in Nachricht <0cccb82e-bdf5-483a-b6ff-0145b3f35...@gv8g2000vbb.googlegroups.com>: > 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 this file afterwards only on the > initiator, but not on the target. Means, I open a Terminal on the > target and take a look what is available on the disk, but > unfortunately the disk is still shown as empty, despite showing the > file being there via the Initiator. > While copying I took a look in Wireshark and it was shown that the > transfer really is happening, but the file still isn't there!! > What could be the problem? Is it maybe because my shared disk is > formatted with ext3? This shouldn't be the problem however, since the > tutorial found under ( > http://www.howtoforge.com/using-iscsi-on-ubuntu-9.04-initiator-and-target > ) also suggested this file system. > > Thanks! -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Changes made on iSCSI disk are not shown on initiator
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 target (via > the mounted folder) I can see this file afterwards only on the > initiator, but not on the target. Are you trying to say that you mounted the same device that you're exporting via iSCSI, on the target machine as well? This is quite a bad idea, and very likely leads to data corruption as you experienced. Ext3 is not a cluster file system, it should be mounted only by one machine at a time. I repeat: *do not do this*, it will not work. If you absolutely need something like this, use a clustered file system like OCFS2 on the raw device. Cheers, -- cc -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Changes made on iSCSI disk are not shown on initiator
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 this file afterwards only on the initiator, but not on the target. Means, I open a Terminal on the target and take a look what is available on the disk, but unfortunately the disk is still shown as empty, despite showing the file being there via the Initiator. While copying I took a look in Wireshark and it was shown that the transfer really is happening, but the file still isn't there!! What could be the problem? Is it maybe because my shared disk is formatted with ext3? This shouldn't be the problem however, since the tutorial found under ( http://www.howtoforge.com/using-iscsi-on-ubuntu-9.04-initiator-and-target ) also suggested this file system. Thanks! -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.