Mike Christie wrote:
> Hey, I fixed this in the patches and put them in here:
> http://git.kernel.org/?p=linux/kernel/git/mnc/linux-2.6-iscsi.git;a=shortlog;h=refs/heads/iscsi
> Do you prefer that I send the entire patchset to the list? If so let me
I cloned the tree, built/booted with the iscsi b
Jonas,
You don't have to restart it. /etc/init.d/iscsi will start iscsid + log into
any nodes that you've discovered. The only thing you would have to do to add
new disks would be to do the following:
1) iscsiadm -m discovery -t st -p
I usually do that plus pipe that through grep to find t
On Jan 21, 9:07 pm, Pasi Kärkkäinen wrote:
>
> No, you don't need to restart iscsi services.
>
> Just rescan.
I've realized that now, thanks.
> Also: did you consider using LVM on the iSCSI LUNs?
I thought about it, but since I'm using LVM within the kvm-guests that
are the acutal users of th
This is apparently not a good idea - since, as far as I can tell at
least, I have to restart the iscsi subsystem every time I present a
new disk from the PS6000. A "service iscsi restart" effectively
destroys all KVM guests using existing, already logged in iscsi disks
will hang indefinitely wonde
On Jan 21, 9:23 pm, Mike Christie wrote:
> On 01/20/2011 09:15 AM, jbygden wrote:
>
> Are you doing a restart so the iscsi service logs into the new targets?
Yes, because that's what all the manuals say I have to do.
> You have already done the disocvery command to find the new targets right?
On 01/24/2011 03:27 AM, Or Gerlitz wrote:
Mike Christie wrote:
Hey, I fixed this in the patches and put them in here:
http://git.kernel.org/?p=linux/kernel/git/mnc/linux-2.6-iscsi.git;a=shortlog;h=refs/heads/iscsi
Do you prefer that I send the entire patchset to the list? If so let me
I cloned
On 01/21/2011 02:36 PM, jbygden wrote:
Now, when you've told me I was able to find it in the man page though.
The README /usr/share/docs/iscsi-initiator-utils-$VERSION/README might
be more helpful.
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" gr
On 01/14/2011 08:27 AM, Mike Christie wrote:
>
> Hey,
>
> I was working on this patch. It seems to work for iser and cxgbi in
> the normal case. iscsi_tcp is broken with it (there is debugging stuff
> in iscsi_tcp.c so do not look at it for review purposes).
>
Excuse the stupid question: how can y
On 01/24/2011 03:00 PM, torn5 wrote:
On 01/14/2011 08:27 AM, Mike Christie wrote:
Hey,
I was working on this patch. It seems to work for iser and cxgbi in
the normal case. iscsi_tcp is broken with it (there is debugging stuff
in iscsi_tcp.c so do not look at it for review purposes).
Excuse
Mike Christie wrote:
> .39. I am still waiting on test results from others, so I think by the
> time they are done it will be late in .38
make sense, if possible, lets just have things sent to James whenever they're
ready and not just before the .39 merge window...
> It is ok. It is same approac
torn5 wrote:
> The only target would be stgt but it has serious data corruption issues
> on parallel reads, which get periodically reported in the stgt mailing
> list but have never been fixed...
Over the last couple of months, a new iser implementation for stgt was posted
and has gone through fe
11 matches
Mail list logo
