Re: [Iscsitarget-devel] error in LUN detection on iscsitarget

[Arne R. <arn...@go...>]

Ok, so it's indeed the mess I thought it would be. :)
As I wrote, /etc/init.d/iscsitarget is from the distro package - don't
use that but /etc/init.d/iscsi-target. If there are still issues with
that pls. let us know.

Regarding the compat patches: I didn't run into this on my ubuntu box
(newer flavour though), but I'll try to reproduce it in a 10.04 VM.

Cheers,
Arne

2011/2/28 Aastha Mehta <aas...@gm...>:
> Hi,
> I am running it on Ubuntu 10.04. The script that is present is
> /etc/init.d/iscsitarget.
> I did a completely fresh manual install from iscsitarget-1.4.20.2 (yes,
> after getting messed up with sudo apt-get install iscsitarget and the manual
> install, I cleaned it up and then again installed from the package :-) ).
> If I try to make without any modification, I get an error that looks
> somewhat like (I can't get you the exact lines, as I would have to run make
> again and I don't want to meddle with it right now):
> make error: cannot find linux-2.6.32-28 compatibility patch required with
> 'patch'.
>
> Exactly, this is what happens:
> After I first installed iscsitarget manually, I modified ietd.conf and
> initiators.allow appropriately and issued sudo /etc/init.d/iscsitarget
> start.
> I got the error that it failed as there was no iscsi_trgt module.
> lsmod | grep iscsi_trgt returned nothing, which indicated that the module
> was indeed not inserted.
> I did modprobe -v iscsi_trgt
> and it worked
> lsmod | grep iscsi_trgt shows:
> iscsi_trgt      80103       0
> Then I ran /etc/init.d/iscsitarget restart
> It worked this first time and checked my logs, etc.
> Then I ran /etc/init.d/iscsitarget restart (or even /etc/init.d/iscsitarget
> stop gives the same error) again and it shows:
> Removing iscsi enterprise target devices        [OK]
> Removing iscsi enterprise target modules       [fail]
> Starting iscsi enterprise target service            [OK]
> lsmod | grep iscsi_trgt shows:
> iscsi_trgt      80103      4            => 4 users using the module
> and if i try to do sudo modprobe -rf iscsi_trgt, it shows:
> FATAL: Module iscsi_trgt is in use.
> I had run into this module-failing-to-be-removed error earlier also. Then,
> the crude method had worked fine and I was able to run iscsitarget. This
> time, the problem is not getting resolved.
> Aastha.
> On 28 February 2011 18:21, Arne Redlich <arn...@go...> wrote:
>>
>> 2011/2/28 Aastha Mehta <aas...@gm...>:
>> > Hi,
>> > I am running into a new problem now. When i try to restart iscsitarget,
>> > it
>> > fails to stop and remove the iscsi target modules. That is, iscsi_trgt
>> > is
>> > not removed and reinserted correctly. I read about the brute force
>> > method -
>> > to rename iscsi_trgt.ko module to something else, rebooting, renaming
>> > back
>> > to iscsi_trgt.ko and then modprobe iscsi_trgt.
>> > But this works only once. After that if i again restart iscsitarget, I
>> > get
>> > back the error.
>> > Please tell, how can the problem be fixed permanently.
>>
>> What distribution are you running IET on, and which commandline do you
>> use to restart it?
>> In case it's ubuntu (possibly also applies to debian or derivatives of
>> either of these):
>> The distribution provided package (iscsitarget) installs a
>> /etc/init.d/iscsitarget script, while the IET install from source
>> creates /etc/init.d/iscsi-target. It's best to uninstall the package
>> from the distribution to avoid a messup and after that to reinstall
>> from source (as the package uninstall will probably remove ietd and
>> ietadm). If there is still an issue with the iscsi-target init script
>> pls. let us know.
>>
>> BTW, there shouldn't be any need to modify the backward compat
>> patching code in the Makefile, it should just work. If it doesn't
>> please give us details about the issue so we can fix it.
>>
>> Cheers,
>> Arne
>>
>> Arne
>
>
>
> --
> Aastha Mehta
> Intern, NetApp, Bangalore
> 4th year undergraduate, BITS Pilani
> E-mail: aas...@gm...
>
>
>