Can't find ISCSI drives after NAS firmware update
This is what it's all about: I've got a Linux network with an actual hardware server running two separate virtual machines and a QNAP NAS T-459 Pro+ as a fileserver. Since updating the QNAP firmware on the NAS, the main server cannot access the ISCSI drives anymore. Effect: All net drives at the workstations are not accessible anymore, so you can't access any file from there. The hardware server is running XenServer as a virtualisation software, providing one VM as a VPN gateway and another VM as a Samba server (192.168.1.33). Whenever I try mounting the ISCSI drives on the Samba server using the UUID (as in /etc/fstab), I get: server01:/home# mount 2d3e150d-a259-4a82-bfe5-f60c6785bc06 /mnt/nfs/backup -t ext3 mount: special device 2d3e150d-a259-4a82-bfe5-f60c6785bc06 does not exist Same if I use mount /dev/sda1 /mnt/iscsi_d -t ext3. Though it is possible to access the QNAP-NAS (192.168.1.34) from the Samba server via ssh. I've mounted a NAS-folder on the Samba server using NFS. Attached I will send you the last entries in /etc/logs/kmsg. Have you got any ideas? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Can't find ISCSI drives after NAS firmware update
This is what it's all about: I've got a Linux network with an actual hardware server running two separate virtual machines and a QNAP NAS T-459 Pro+ as a fileserver. Since updating the QNAP firmware on the NAS, the main server cannot access the ISCSI drives anymore. Effect: All net drives at the workstations are not accessible anymore, so you can't access any file from there. The hardware server is running XenServer as a virtualisation software, providing one VM as a VPN gateway and another VM as a Samba server (192.168.1.33). Whenever I try mounting the ISCSI drives on the Samba server using the UUID (as in /etc/fstab), I get: server01:/home# mount 2d3e150d-a259-4a82-bfe5-f60c6785bc06 /mnt/nfs/backup -t ext3 mount: special device 2d3e150d-a259-4a82-bfe5-f60c6785bc06 does not exist Same if I use: mount /dev/sda1 /mnt/iscsi_d -t ext3 Though it is possible to access the QNAP-NAS (192.168.1.34) from the Samba server via ssh. I've mounted a NAS-folder on the Samba server using NFS. Attached I will send you the last entries in /etc/logs/kmsg. Have you got any ideas? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Automatic update of files between a group of hosts
Hello, I have a virtual disk shared by a group of two hosts. Both are connecting to the virtual disk correctly, but if I write a file from one host to the virtual disk the other host cannot see it until the virtual disk is unmounted and mounted again. It happens the same from the other host. Both hosts are running linux, one is Ubuntu 10.04 and the other is Fedora 17. I am concerned that this behavious can lead to data corruption, as one machine is not aware of changes made on the virtual disk by the other machine. Is it possible to fix this issue by tunning any open-iscsi parameter? Thanks in advance Antonio -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[PATCH -next] [SCSI] scsi_transport_iscsi: fix error return code in iscsi_transport_init()
From: Wei Yongjun yongjun_...@trendmicro.com.cn
Fix to return -ENOMEM in the create workqueue error case
instead of 0, as done elsewhere in this function.
Signed-off-by: Wei Yongjun yongjun_...@trendmicro.com.cn
---
drivers/scsi/scsi_transport_iscsi.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/scsi/scsi_transport_iscsi.c
b/drivers/scsi/scsi_transport_iscsi.c
index 47799a3..475265a 100644
--- a/drivers/scsi/scsi_transport_iscsi.c
+++ b/drivers/scsi/scsi_transport_iscsi.c
@@ -3985,8 +3985,10 @@ static __init int iscsi_transport_init(void)
}
iscsi_eh_timer_workq = create_singlethread_workqueue(iscsi_eh);
- if (!iscsi_eh_timer_workq)
+ if (!iscsi_eh_timer_workq) {
+ err = -ENOMEM;
goto release_nls;
+ }
return 0;
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To unsubscribe from this group and stop receiving emails from it, send an email
to open-iscsi+unsubscr...@googlegroups.com.
To post to this group, send email to open-iscsi@googlegroups.com.
Visit this group at http://groups.google.com/group/open-iscsi?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Automatic update of files between a group of hosts
Hello, No. Open-iSCSI can't fix this issue. You're problem is that you don't have a Cluster file system in place, each server believes they own the disk exclusively. If you keep this as-is you will corrupt the data, that's for sure. Easiest thing is to connect with one server, then share out that disk over NFS. Regards, Don On Fri, Apr 19, 2013 at 8:22 AM, Antonio López alop...@tid.es wrote: Hello, I have a virtual disk shared by a group of two hosts. Both are connecting to the virtual disk correctly, but if I write a file from one host to the virtual disk the other host cannot see it until the virtual disk is unmounted and mounted again. It happens the same from the other host. Both hosts are running linux, one is Ubuntu 10.04 and the other is Fedora 17. I am concerned that this behavious can lead to data corruption, as one machine is not aware of changes made on the virtual disk by the other machine. Is it possible to fix this issue by tunning any open-iscsi parameter? Thanks in advance Antonio -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
