Re: [storage-discuss] iscsiadm source compatibility

2009-09-09 Thread viveks
Hi, Thanks for the reply, The ip address is valid and the targets are reachable as i can discover and login to the targets using the iscsiadm utility on s10. Is it possible that an EFAULT may be returned if the size of the structure passed to the ioctl is different from the size of structure

Re: [storage-discuss] iscsiadm source compatibility

2009-09-09 Thread viveks
Hi, Sorry for the separate post, i should have included this in my previous reply. Is there any way i can debug the driver or get a trace of something to know exactly what is happening inside the driver? Any way of finding out the exact cause of failure of the ioctl call? Thank you, Vivek S

Re: [storage-discuss] FCoE in a N-Port point-to-point topology

2009-09-09 Thread Ronnie koch
Nigel Smith wrote: Hi Ronnie Many thanks for cross-posting that interesting fairly detailed feedback from the open-fcoe list. Sometimes detail is good :) Zhong Wang wrote: Thanks Ronnie, that explains the Open FCoE initiator behavior. The debug trace of Solaris FCoE software can be

Re: [storage-discuss] FCoE in a N-Port point-to-point topology

2009-09-09 Thread Zhong Wang
Ronnie koch wrote: Nigel Smith wrote: Hi Ronnie Many thanks for cross-posting that interesting fairly detailed feedback from the open-fcoe list. Sometimes detail is good :) Zhong Wang wrote: Thanks Ronnie, that explains the Open FCoE initiator behavior. The

Re: [storage-discuss] FCoE in a N-Port point-to-point topology

2009-09-09 Thread Ronnie koch
Did some more testing by changing the target N/PWWN to be smaller than that of the initiator but the results were similar to my 03 trace from yesterday even when I reverted to original WWNs. Seems the OpenFC0E initiator responds differently with E1000 than with the VMware default PCnet xyz. No

Re: [storage-discuss] iscsiadm source compatibility

2009-09-09 Thread Bing Zhao - Sun Microsystems
Hi Viveks: There is no existed dtrace script for debuging iscsi driver. So if you want to do that, you should write the script by yourself. In dtrace script, you can know the return value of a function. So I think this is a way to find which function exits with errors. You can find the

Re: [storage-discuss] [fm-discuss] self test failure on Intel X25-E SSD

2009-09-09 Thread Peter Eriksson
Done some more testing, and I think my X4240/mpt/X25-problems must be something else. Attempting to read (with smartctl) the self test log on the 8850-firmware X25-E gives better results than with the old firmware: X25-E running firmware 8850 on an X4240 with mpt controller: # smartctl -d

[storage-discuss] migration path to COMSTAR

2009-09-09 Thread Joseph Mocker
Hi, Just getting my feet wet with COMSTAR. I have some iSCSI LUs backed by ZVOLs that I created pre-COMSTAR (Nevada 84). I would like to migrate to a newer version of Nevada or OpenSolaris, but my first attempt mailed miserably and apparently I narrowly escaped large amounts of data loss.

[storage-discuss] NexentaStor.org and Open Source components

2009-09-09 Thread Anil Gulecha
Hi All, NexentaStor is an industry leading Storage appliance, based on Opensolaris and Ubuntu LTS. On behalf of Nexenta Systems, I'd like to announce the setup of NexentaStor.org, where we've open-sourced internal kernel gate and plugins that extend the appliance. NexentaStor.org is a complete

Re: [storage-discuss] migration path to COMSTAR

2009-09-09 Thread A Hettinger
one method that does work, is to use a comstar iscsi port on the loopback device, mount it locally then use dd to move the content of your old backing store to the new device. you can then set up views to whatever you want. it's ugly, but it does work. -- This message posted from

Re: [storage-discuss] migration path to COMSTAR

2009-09-09 Thread Joseph Mocker
A Hettinger wrote: one method that does work, is to use a comstar iscsi port on the loopback device, mount it locally then use dd to move the content of your old backing store to the new device. you can then set up views to whatever you want. it's ugly, but it does work. Ah, clever.

Re: [storage-discuss] migration path to COMSTAR

2009-09-09 Thread eneal
Quoting Joseph Mocker m...@sun.com: A Hettinger wrote: one method that does work, is to use a comstar iscsi port on the loopback device, mount it locally then use dd to move the content of your old backing store to the new device. you can then set up views to whatever you want. it's

[storage-discuss] Making zfs HA

2009-09-09 Thread Roman Naumenko
Hello list, What are the options for building clustering storage using opensolaris? I'm interested in HA solutions. I tried only one option - AVS replication. Unfortunately, AVS configuration is too complicated. Groups, bitmaps, queues, rcp timeouts, slicing - it's just a nightmare to make it

Re: [storage-discuss] Making zfs HA

2009-09-09 Thread Erast
Hi Roman, take a look on what NexentaStor is providing: auto-cdp - a commercial plugin which simplifies significantly ZFS/AVS management of primary/secondary hosts auto-sync - a free service which supports sophisticated ZFS send/recv over SSH, NC. Or use send snapshots over RSYNC - which

Re: [storage-discuss] iscsiadm source compatibility

2009-09-09 Thread viveks
Hi, Thanks for the information and your time. I ll give it a try and get back if possible, probably after a while as i am stuck with some other work. Thanks a lot. Vivek S -- This message posted from opensolaris.org ___ storage-discuss mailing list

Re: [storage-discuss] iscsiadm source compatibility

2009-09-09 Thread Bing Zhao - Sun Microsystems
Hi Viveks: Please let us know if you have any questions on the iscsi driver debuging or related dtrace scripts. Regards, Bing viveks wrote: Hi, Thanks for the information and your time. I ll give it a try and get back if possible, probably after a while as i am stuck with some other