Debian Bug report logs - #498616
open-iscsi: please support LVM

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Ferenc Wagner <wferi@niif.hu>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: open-iscsi: please support LVM

Date: Thu, 11 Sep 2008 15:53:29 +0200

Package: open-iscsi
Version: 2.0.869.2-2.1
Severity: wishlist
Tags: patch

Hi,

please consider supporting LVM volume activation after iSCSI login.
After shamelessly stealing parts of the aoetools init script, I came up
with the following patch.

Also, why not try to umount the respective filesystems before logout?
I had the script fail if deactivation errors out to this end.  That
could get rid of the WARNING! in README.Debian, too.

Thanks,
Feri.

--- open-iscsi.orig	2008-09-10 08:23:37.000000000 +0200
+++ open-iscsi	2008-09-11 15:43:09.000000000 +0200
@@ -18,6 +18,11 @@
 
 . /lib/lsb/init-functions
 
+# Include defaults if available
+if [ -f /etc/default/open-iscsi ]; then
+	. /etc/default/open-iscsi
+fi
+
 if [ ! -d /sys/class/ ]; then
   log_failure_msg "iSCSI requires a mounted sysfs, not started."
   exit 0
@@ -97,6 +102,19 @@
 
 	udevsettle
 
+	if [ ! -x "/sbin/vgchange" -a -n "$LVMGROUPS" ]; then
+		log_warning_msg "LVM2 tools are not installed, not honouring LVMGROUPS."
+		LMVGROUPS=""
+	fi
+	if [ -n "$LVMGROUPS" ]; then
+		log_daemon_msg "Activating iSCSI volume groups"
+		for vg in "$LVMGROUPS"; do
+			log_progress_msg $vg
+			vgchange --available=y $vg
+		done
+		log_end_msg 0
+	fi
+
 	log_daemon_msg "Mounting network filesystems"
 	MOUNT_RESULT=1
 	if mount -a -O _netdev >& /dev/null; then
@@ -125,6 +143,15 @@
 }
 
 stop() {
+	if [ -n "$LVMGROUPS" ]; then
+		log_daemon_msg "Deactivating iSCSI volume groups"
+		for vg in "$LVMGROUPS"; do
+                        log_progress_msg $vg
+                        vgchange --available=n $vg || exit 1
+                done
+                log_end_msg 0
+        fi
+
 	stoptargets
 	log_daemon_msg "Stopping iSCSI initiator service"
 	start-stop-daemon --stop --quiet --pidfile $PIDFILE --signal KILL --exec $DAEMON

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (600, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.26-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Message #10 received at 498616@bugs.debian.org (full text, mbox, reply):

From: "Javier Barroso" <javier.barroso@isotrol.com>

To: 498616@bugs.debian.org

Subject: Unmounting LVM'd isci based filesystem

Date: Mon, 19 Jan 2009 00:00:29 +0100 (CET)

Hello,

I have a similar patch for this issue (but the first in this bug seems
fine too), so I'm not attaching my patch, but yes a complementary patch.

I think unmounting lvm filesystem is necesary. This patch, umount LVM
filesystem from iscsi disk:

--- umountiscsi.sh.orig 2009-01-18 23:35:41.000000000 +0100
+++ umountiscsi.sh      2009-01-18 23:36:44.000000000 +0100
@@ -31,6 +31,16 @@
        done
     done
     log_end_msg 0
+    if [ -x /sbin/lvs ]; then
+           log_daemon_msg "Unmounting iscsi-backed LVM filesystems"
+           for DEVICE in $(mount | awk  '/_netdev/ {print $1}'); do
+               if lvs "$DEVICE" &> /dev/null; then
+                   log_progress_msg $DEVICE
+                   umount $DEVICE
+               fi
+           done
+    fi
+    log_end_msg 0

We (as debian user) have another problem with lenny and iscsi + lvm +
multipath (should I open another bug?). I try to explain it here:

# pwd
/etc/rc6.d
# ls -1 *multipath* *iscsi* *lvm*
K20multipath-tools
K80umountiscsi.sh
K81open-iscsi
S50lvm
S50lvm2

Suppose I have a pv in iscsi lun, and over it a vg, who has a lv.
So if multipath is down, how umountiscsi is capable to unmount lvm volume?

My server hangs forever when is rebooting or shutting down. With sys+rq W
debian said to me there is a process lvchange who is blocked. I can read
in redhat issue tracker [1] about similar bug in redhat systems.

Is it possible to "full" support lvm inside iscsi luns ?

Any help is apreciatte.

Thank you.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=212265

Debian Rocks!

-- 
Javier Barroso Tristán
Administrador de Redes y Sistemas
DIRECCIÓN DE TECNOLOGÍA:OPERACIONES Y SOPORTE
javier.barroso@isotrol.com
--------------------------------------------

ISOTROL
Edificio BLUENET. Avda. Isaac Newton nº 3, 4ª planta.
Parque Tecnológico Cartuja '93, 41092 Sevilla.
Teléfono: 955 036 800 - Fax: 955 036 849
www.isotrol.com

Message #15 received at 498616@bugs.debian.org (full text, mbox, reply):

From: "Javier Barroso" <javier.barroso@isotrol.com>

To: 498616@bugs.debian.org

Subject: Re: Unmounting LVM'd isci based filesystem

Date: Mon, 19 Jan 2009 00:07:11 +0100 (CET)

Hi again,
> Hello,
>
> I have a similar patch for this issue (but the first in this bug seems
> fine too), so I'm not attaching my patch, but yes a complementary patch.
My patch included vgscan, I think it is necessary too. Is it enough with
vgchange like Ferenc propposed ?

-- 
Javier Barroso Tristán
Administrador de Redes y Sistemas
DIRECCIÓN DE TECNOLOGÍA:OPERACIONES Y SOPORTE
javier.barroso@isotrol.com
--------------------------------------------

ISOTROL
Edificio BLUENET. Avda. Isaac Newton nº 3, 4ª planta.
Parque Tecnológico Cartuja '93, 41092 Sevilla.
Teléfono: 955 036 800 - Fax: 955 036 849
www.isotrol.com

Message #20 received at 498616@bugs.debian.org (full text, mbox, reply):

From: Petter Reinholdtsen <pere@hungry.com>

To: 498616@bugs.debian.org

Subject: Re: open-iscsi: please support LVM

Date: Sat, 5 Sep 2009 10:48:10 +0200

Another and perhaps better approach would be to move the files needed
by the init.d script to / and move the init.d script before the lvm2
script, this allowing lvm to see the devices and avoid the need for
special lvm handling in open-iscsi.

See #542370 for a related issue, with a dependency loop between the
init.d scripts lvm2 and open-iscsi.

Happy hacking,
-- 
Petter Reinholdtsen

Message #25 received at 498616@bugs.debian.org (full text, mbox, reply):

From: Javier Barroso <javibarroso@gmail.com>

To: 498616@bugs.debian.org

Subject: Re: open-iscsi: please support LVM

Date: Thu, 15 Oct 2009 00:53:13 +0200

Petter,

What about when the system is over 'local' lvm volumes and you have
another lvm disk from iscsi ?

You couldn't move open-iscsi scripts before lvm, because you won't
have mounted system volumes

Maybe I'm not understanding something.

Thanks your effort in debian boot improvements!

Message #30 received at 498616@bugs.debian.org (full text, mbox, reply):

From: Ritesh Raj Sarraf <rrs@researchut.com>

To: javier.barroso@isotrol.com

Cc: 498616@bugs.debian.org

Subject: Re: Unmounting LVM'd isci based filesystem

Date: Sat, 3 Apr 2010 13:13:41 +0530

[Message part 1 (text/plain, inline)]

Hi,

I think there are 2 parts to this problem.

1) iSCSI + Multipath + LVM

I am not sure how is it handle during start-up. Suppose you have 256 LUNs with 
4 path each. This would result in a large 1000+ scsi device list. Discovering 
these many devices will take some time. And on that, dm-multipath will also 
take time in identifying these devices.

I think to tackle iSCSI + Multipath + LVM, during start-up, we will need a 
custom udev rule to identify Multipathed iSCSI PVs.


2) As one, but during shutdown.
Okay!! Here I think we might be in a trickier situation. To be able to unmount 
iSCSI + Multipath + LVM devices we need a 3 step process.

a. Offline the VG
b. Delete the maps
c. Then stop iSCSI


Currently, in iSCSI this is not handled. And I think if you have a setup like 
this for LUNs referenced in fstab through they LV names, iSCSI might just 
ignore them and shutdown the service. Thus this will lead to a hang state.

To handle this scenario, I think we need a way to tear down the logical 
devices and identify their physical scsi devices. Once we have the scsi device 
names, umountiscsi.sh can determine if it is an iSCSI device or not. And if 
so, it will not stop the iSCSI service (Part of this change has been put into 
2.0.871.3-1, pending to be uploaded to Sid)


Regards,
Ritesh


On Monday 19 Jan 2009 04:30:29 Javier Barroso wrote:
> We (as debian user) have another problem with lenny and iscsi + lvm +
> multipath (should I open another bug?). I try to explain it here:
> 
> # pwd
> /etc/rc6.d
> # ls -1 *multipath* *iscsi* *lvm*
> K20multipath-tools
> K80umountiscsi.sh
> K81open-iscsi
> S50lvm
> S50lvm2
> 
> Suppose I have a pv in iscsi lun, and over it a vg, who has a lv.
> So if multipath is down, how umountiscsi is capable to unmount lvm volume?
> 
> My server hangs forever when is rebooting or shutting down. With sys+rq W
> debian said to me there is a process lvchange who is blocked. I can read
> in redhat issue tracker [1] about similar bug in redhat systems.
> 
> Is it possible to "full" support lvm inside iscsi luns ?
> 
> Any help is apreciatte.
> 
> Thank you.
> 
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=212265
> 
> Debian Rocks!

-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

[signature.asc (application/pgp-signature, inline)]

Message #35 received at 498616@bugs.debian.org (full text, mbox, reply):

From: Ritesh Raj Sarraf <rrs@researchut.com>

To: javier.barroso@isotrol.com, Ferenc Wagner <wferi@niif.hu>

Cc: 498616@bugs.debian.org

Subject: Re: Unmounting LVM'd isci based filesystem

Date: Tue, 8 Jun 2010 19:54:12 +0530

[Message part 1 (text/plain, inline)]

I'm planning an upload in a day or two and I want to fix this bug. I have taken 
your patches and cooked up something.

While testing, I realized that it looks like udev itself is taking care of 
activating/de-activating iscsi devices.

Now I can still go ahead with the patches applied and upload it or else drop 
the patches and offload that task to udev. Comments ?


Ritesh


On Monday 19 Jan 2009 04:30:29 Javier Barroso wrote:
> Hello,
> 
> I have a similar patch for this issue (but the first in this bug seems
> fine too), so I'm not attaching my patch, but yes a complementary patch.
> 
> I think unmounting lvm filesystem is necesary. This patch, umount LVM
> filesystem from iscsi disk:
> 
> --- umountiscsi.sh.orig 2009-01-18 23:35:41.000000000 +0100
> +++ umountiscsi.sh      2009-01-18 23:36:44.000000000 +0100
> @@ -31,6 +31,16 @@
>         done
>      done
>      log_end_msg 0
> +    if [ -x /sbin/lvs ]; then
> +           log_daemon_msg "Unmounting iscsi-backed LVM filesystems"
> +           for DEVICE in $(mount | awk  '/_netdev/ {print $1}'); do
> +               if lvs "$DEVICE" &> /dev/null; then
> +                   log_progress_msg $DEVICE
> +                   umount $DEVICE
> +               fi
> +           done
> +    fi
> +    log_end_msg 0
> 
> We (as debian user) have another problem with lenny and iscsi + lvm +
> multipath (should I open another bug?). I try to explain it here:
> 
> # pwd
> /etc/rc6.d
> # ls -1 *multipath* *iscsi* *lvm*
> K20multipath-tools
> K80umountiscsi.sh
> K81open-iscsi
> S50lvm
> S50lvm2
> 
> Suppose I have a pv in iscsi lun, and over it a vg, who has a lv.
> So if multipath is down, how umountiscsi is capable to unmount lvm volume?
> 
> My server hangs forever when is rebooting or shutting down. With sys+rq W
> debian said to me there is a process lvchange who is blocked. I can read
> in redhat issue tracker [1] about similar bug in redhat systems.
> 
> Is it possible to "full" support lvm inside iscsi luns ?
> 
> Any help is apreciatte.
> 
> Thank you.
> 
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=212265
> 
> Debian Rocks!

-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

[signature.asc (application/pgp-signature, inline)]

Message #40 received at 498616@bugs.debian.org (full text, mbox, reply):

From: Javier Barroso <Javier.Barroso@isotrol.com>

To: Ritesh Raj Sarraf <rrs@researchut.com>

Cc: javier.barroso@isotrol.com, Ferenc Wagner <wferi@niif.hu>, 498616@bugs.debian.org

Subject: Re: Unmounting LVM'd isci based filesystem

Date: Tue, 08 Jun 2010 16:54:51 +0200

On 08/06/10 16:24, Ritesh Raj Sarraf wrote:
> I'm planning an upload in a day or two and I want to fix this bug. I have taken
> your patches and cooked up something.
>
> While testing, I realized that it looks like udev itself is taking care of
> activating/de-activating iscsi devices.
>
> Now I can still go ahead with the patches applied and upload it or else drop
> the patches and offload that task to udev. Comments ?
>    
If udev umount lvm devices, then it is ok (drop this patch). Maybe lvm 
maintainer knows better who should umount these _netdev devices ?

I can test your new upload and tell you if I see any issue

Thank you very much

>
> Ritesh
>
>
> On Monday 19 Jan 2009 04:30:29 Javier Barroso wrote:
>    
>> Hello,
>>
>> I have a similar patch for this issue (but the first in this bug seems
>> fine too), so I'm not attaching my patch, but yes a complementary patch.
>>
>> I think unmounting lvm filesystem is necesary. This patch, umount LVM
>> filesystem from iscsi disk:
>>
>> --- umountiscsi.sh.orig 2009-01-18 23:35:41.000000000 +0100
>> +++ umountiscsi.sh      2009-01-18 23:36:44.000000000 +0100
>> @@ -31,6 +31,16 @@
>>          done
>>       done
>>       log_end_msg 0
>> +    if [ -x /sbin/lvs ]; then
>> +           log_daemon_msg "Unmounting iscsi-backed LVM filesystems"
>> +           for DEVICE in $(mount | awk  '/_netdev/ {print $1}'); do
>> +               if lvs "$DEVICE"&>  /dev/null; then
>> +                   log_progress_msg $DEVICE
>> +                   umount $DEVICE
>> +               fi
>> +           done
>> +    fi
>> +    log_end_msg 0
>>
>> We (as debian user) have another problem with lenny and iscsi + lvm +
>> multipath (should I open another bug?). I try to explain it here:
>>
>> # pwd
>> /etc/rc6.d
>> # ls -1 *multipath* *iscsi* *lvm*
>> K20multipath-tools
>> K80umountiscsi.sh
>> K81open-iscsi
>> S50lvm
>> S50lvm2
>>
>> Suppose I have a pv in iscsi lun, and over it a vg, who has a lv.
>> So if multipath is down, how umountiscsi is capable to unmount lvm volume?
>>
>> My server hangs forever when is rebooting or shutting down. With sys+rq W
>> debian said to me there is a process lvchange who is blocked. I can read
>> in redhat issue tracker [1] about similar bug in redhat systems.
>>
>> Is it possible to "full" support lvm inside iscsi luns ?
>>
>> Any help is apreciatte.
>>
>> Thank you.
>>
>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=212265
>>
>> Debian Rocks!
>>      

Message #45 received at 498616@bugs.debian.org (full text, mbox, reply):

From: Ritesh Raj Sarraf <rrs@researchut.com>

To: Javier Barroso <Javier.Barroso@isotrol.com>

Cc: Ferenc Wagner <wferi@niif.hu>, 498616@bugs.debian.org

Subject: Re: Unmounting LVM'd isci based filesystem

Date: Tue, 8 Jun 2010 22:23:08 +0530

[Message part 1 (text/plain, inline)]

On Tuesday 08 Jun 2010 20:24:51 Javier Barroso wrote:
> If udev umount lvm devices, then it is ok (drop this patch). Maybe lvm 
> maintainer knows better who should umount these _netdev devices ?
> 
> I can test your new upload and tell you if I see any issue
> 
> Thank you very much

You might want to verify these behaviors.

Here's the package and any testing will be good.
http://people.debian.org/~rrs/open-iscsi_2.0.871.3-2_amd64.deb



-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

[signature.asc (application/pgp-signature, inline)]

Message #50 received at 498616@bugs.debian.org (full text, mbox, reply):

From: Ritesh Raj Sarraf <rrs@debian.org>

To: 498616@bugs.debian.org

Cc: Javier Barroso <Javier.Barroso@isotrol.com>, Ferenc Wagner <wferi@niif.hu>

Subject: Re: Bug#498616: Unmounting LVM'd isci based filesystem

Date: Tue, 8 Jun 2010 23:52:51 +0530

[Message part 1 (text/plain, inline)]

The changes included are:

* LVM Handling
* Handling _netdev devices for umounts

_netdev devices will come with the problem that if you have other _netdev 
servcies (like NFS share), they also get included here.

One more thing I can think of is is LUKS devices. I can handle these with 
_netdev but it also needs to be closed. That is not done currently.

And then we have multipath devices. But for multipathed devices, there's no 
need of a delete/disassociate/offline thingy.



I personally am thinking of letting all the features added till now be there. 
This will help us if someone wants to backport the package. It will also help 
if in case udev breaks (which I doubt). But having a manual method as a backup 
plan should not hurt much.

I think I will go with what I have provided you for testing unless someone 
comes up with an objection for it.


Ritesh

On Tuesday 08 Jun 2010 22:23:08 Ritesh Raj Sarraf wrote:
>   On Tuesday 08 Jun 2010 20:24:51 Javier Barroso wrote:
> > If udev umount lvm devices, then it is ok (drop this patch). Maybe lvm 
> > maintainer knows better who should umount these _netdev devices ?
> >
> > 
> >
> > I can test your new upload and tell you if I see any issue
> >
> > 
> >
> > Thank you very much
> 
> You might want to verify these behaviors.
> 
> Here's the package and any testing will be good.
> http://people.debian.org/~rrs/open-iscsi_2.0.871.3-2_amd64.deb

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs

[signature.asc (application/pgp-signature, inline)]

Message #55 received at 498616@bugs.debian.org (full text, mbox, reply):

From: Ritesh Raj Sarraf <rrs@debian.org>

To: 498616@bugs.debian.org

Cc: javier.barroso@isotrol.com, Ferenc Wagner <wferi@niif.hu>

Subject: Re: Bug#498616: Unmounting LVM'd isci based filesystem

Date: Wed, 9 Jun 2010 00:09:46 +0530

[Message part 1 (text/plain, inline)]

On Tuesday 08 Jun 2010 19:54:12 Ritesh Raj Sarraf wrote:
> > We (as debian user) have another problem with lenny and iscsi + lvm +
> >
> > multipath (should I open another bug?). I try to explain it here:
> > 
> >
> > # pwd
> > /etc/rc6.d
> > # ls -1 multipath iscsi lvm
> > K20multipath-tools
> > K80umountiscsi.sh
> > K81open-iscsi
> > S50lvm
> > S50lvm2
> >
> > 
> >
> > Suppose I have a pv in iscsi lun, and over it a vg, who has a lv.
> > So if multipath is down, how umountiscsi is capable to unmount lvm
> > volume?
> >
> > 
> >
> > My server hangs forever when is rebooting or shutting down. With sys+rq W
> > debian said to me there is a process lvchange who is blocked. I can read
> > in redhat issue tracker [1] about similar bug in redhat systems.
> >
> > 
> >
> > Is it possible to "full" support lvm inside iscsi luns ?


For this problem of yours', I had proposed the kernel team for the "Panic on 
Hung Task" feature. But it was not included.
You might want to advocate for that bug and ask the kernel team to enable the 
feature. Debian BTS #550358

Otherwise, with multipath's "queue_if_no_path" enabled and you lose all paths 
to your LUN, you are out of luck.

The idea is the above bug is:
* Kernel detect Hung Task.
* Kernel Panics on Hung Task
* Kernel reboot/reset on Panic

Not the best, but better than going into the data center and hard resetting 
the machine.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs

[signature.asc (application/pgp-signature, inline)]

Message #60 received at 498616@bugs.debian.org (full text, mbox, reply):

From: Javier Barroso <Javier.Barroso@isotrol.com>

To: Ritesh Raj Sarraf <rrs@researchut.com>

Cc: Javier Barroso <Javier.Barroso@isotrol.com>, Ferenc Wagner <wferi@niif.hu>, 498616@bugs.debian.org

Subject: Re: Unmounting LVM'd isci based filesystem

Date: Wed, 09 Jun 2010 12:41:44 +0200

My environment for testing is i686 (qemu machine from host amd64 doesn't 
permit me to boot amd64 virtual machine (Surely I'm doing something wrong))

So,

Do you have .dsc, so I compile your new package in i686 ? Or can you 
provide a i686 package ?

Thank you again

On 08/06/10 18:53, Ritesh Raj Sarraf wrote:
> On Tuesday 08 Jun 2010 20:24:51 Javier Barroso wrote:
>    
>> If udev umount lvm devices, then it is ok (drop this patch). Maybe lvm
>> maintainer knows better who should umount these _netdev devices ?
>>
>> I can test your new upload and tell you if I see any issue
>>
>> Thank you very much
>>      
> You might want to verify these behaviors.
>
> Here's the package and any testing will be good.
> http://people.debian.org/~rrs/open-iscsi_2.0.871.3-2_amd64.deb
>
>
>
>    


-- 
Javier Barroso
Administrador de Sistemas
Dirección Servicios Corporativos: TI
jbarroso@isotrol.com
__

ISOTROL
Edificio BLUENET. Avda. Isaac Newton, s/n, Isla de la Cartuja
41092 Sevilla.
Tel.: 955 036 800 - Fax: 955 036 849
www.isotrol.com

Message #65 received at 498616@bugs.debian.org (full text, mbox, reply):

From: Ritesh Raj Sarraf <rrs@researchut.com>

To: Javier Barroso <Javier.Barroso@isotrol.com>

Cc: Ferenc Wagner <wferi@niif.hu>, 498616@bugs.debian.org

Subject: Re: Unmounting LVM'd isci based filesystem

Date: Wed, 9 Jun 2010 19:10:47 +0530

[Message part 1 (text/plain, inline)]

On Wednesday 09 Jun 2010 16:11:44 Javier Barroso wrote:
> My environment for testing is i686 (qemu machine from host amd64 doesn't 
> permit me to boot amd64 virtual machine (Surely I'm doing something wrong))
> 
> So,
> 
> Do you have .dsc, so I compile your new package in i686 ? Or can you 
> provide a i686 package ?

You could pull in the git repo and build it. I have already pushed my changes 
there. It is in the master branch

http://git.debian.org/?p=pkg-iscsi/open-iscsi.git


-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

[signature.asc (application/pgp-signature, inline)]

Message #70 received at 498616@bugs.debian.org (full text, mbox, reply):

From: Ritesh Raj Sarraf <rrs@debian.org>

To: Javier Barroso <Javier.Barroso@isotrol.com>

Cc: Ferenc Wagner <wferi@niif.hu>, 498616@bugs.debian.org

Subject: Re: Unmounting LVM'd isci based filesystem

Date: Thu, 10 Jun 2010 14:11:42 +0530

[Message part 1 (text/plain, inline)]

I just got some time and did some testing. I must say I'm happy with the 
outcome. Specify the volgroup in /etc/default/open-iscsi, create LV mount it 
(without _netdev), and stop open-iscsi. It fails to stop. That is what I 
wanted. 


Thank you all. I will be doing the upload in a couple hours.



On Wednesday 09 Jun 2010 19:10:47 Ritesh Raj Sarraf wrote:
> On Wednesday 09 Jun 2010 16:11:44 Javier Barroso wrote:
> > My environment for testing is i686 (qemu machine from host amd64 doesn't
> > permit me to boot amd64 virtual machine (Surely I'm doing something
> > wrong))
> > 
> > So,
> > 
> > Do you have .dsc, so I compile your new package in i686 ? Or can you
> > provide a i686 package ?
> 
> You could pull in the git repo and build it. I have already pushed my
> changes there. It is in the master branch
> 
> http://git.debian.org/?p=pkg-iscsi/open-iscsi.git

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs

[signature.asc (application/pgp-signature, inline)]

Message #75 received at 498616-close@bugs.debian.org (full text, mbox, reply):

From: Ritesh Raj Sarraf <rrs@debian.org>

To: 498616-close@bugs.debian.org

Subject: Bug#498616: fixed in open-iscsi 2.0.871.3-2

Date: Fri, 11 Jun 2010 07:17:09 +0000

Source: open-iscsi
Source-Version: 2.0.871.3-2

We believe that the bug you reported is fixed in the latest version of
open-iscsi, which is due to be installed in the Debian FTP archive:

open-iscsi_2.0.871.3-2.debian.tar.gz
  to main/o/open-iscsi/open-iscsi_2.0.871.3-2.debian.tar.gz
open-iscsi_2.0.871.3-2.dsc
  to main/o/open-iscsi/open-iscsi_2.0.871.3-2.dsc
open-iscsi_2.0.871.3-2_amd64.deb
  to main/o/open-iscsi/open-iscsi_2.0.871.3-2_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 498616@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf <rrs@debian.org> (supplier of updated open-iscsi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 11 Jun 2010 12:33:02 +0530
Source: open-iscsi
Binary: open-iscsi
Architecture: source amd64
Version: 2.0.871.3-2
Distribution: unstable
Urgency: low
Maintainer: Debian iSCSI Maintainers <pkg-iscsi-maintainers@lists.alioth.debian.org>
Changed-By: Ritesh Raj Sarraf <rrs@debian.org>
Description: 
 open-iscsi - High performance, transport independent iSCSI implementation
Closes: 498616 507003 576786
Changes: 
 open-iscsi (2.0.871.3-2) unstable; urgency=low
 .
   * Break down and add quilt patches
     + 003_Fix-CVE-2009-1297.patch
     + 004_make-iscsistart-a-dynamic-binary.patch
   * Add some explanation about initiatorname.iscsi into README.Debian
     (Closes: #507003)
   * Fix double variable assignment in initramfs.local-top. Thanks to Aurelien
     Jarno (Closes: #576786)
   * Document the odd hang behavior during iSCSI login phase when using 32 bit
     open-iscsi with 64 bit kernel
   * Change address to my official Debian address and remove the DMUA flag
   * Handle iSCSI LVM devices and devices marked _netdev (Closes: #498616)
   * Switch to 3.0 (quilt) source format
Checksums-Sha1: 
 ad268825b4508761690363ed02a8b9c5687e4935 2036 open-iscsi_2.0.871.3-2.dsc
 d65378c3f49d638ad7d52ab21ee2c67752e11445 16101 open-iscsi_2.0.871.3-2.debian.tar.gz
 86a9aea65774ce6ad98d8c810a2711c25b5e0fb0 331978 open-iscsi_2.0.871.3-2_amd64.deb
Checksums-Sha256: 
 4c086e0c05df7ff3d1d38b1f54f7f42e9ba5ef5b3d1182fcd68afebf683a0ea8 2036 open-iscsi_2.0.871.3-2.dsc
 cd42ea6b72bffb6ee41c75a5ba98e21ea8d4f8f7045e94630391a577a8b7f1dc 16101 open-iscsi_2.0.871.3-2.debian.tar.gz
 c704b04726140a776f44973f12b057cbfdf754b744ca48a1578a1b6e58a4edca 331978 open-iscsi_2.0.871.3-2_amd64.deb
Files: 
 815097c0fbefc3f3d78a6d3d944d5fa8 2036 net optional open-iscsi_2.0.871.3-2.dsc
 406263d7b9d3da22bdd68dda8c1a6d3b 16101 net optional open-iscsi_2.0.871.3-2.debian.tar.gz
 98c75dec89eac9b5e950752a73048c23 331978 net optional open-iscsi_2.0.871.3-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCgAGBQJMEeFKAAoJEKY6WKPy4XVpbvkP/iVdK1bsPtqwFFAiFkrL2d1I
y32sw1fIYfM6TcCJSxzcAzm/GP/yzCDXbclIB9I0fWLUvYgjUr7ewZJLaUyb68zz
IQKaB+Q4g3VO1NjiHGWiRfAb2i2T4xLu7nTYkrXJsZWf5D0UbJIHVKQcDEerlAr/
TFdOBVu/AEd1d3ZbpDQQf/g1daH9Yh8F9XtdkdQN7ACc3sqTCEGzsUVDZDPic9jC
2nQiJP6pcdYyZWPtiqQqt3EeIQd/QkseXa5TSSO2SM4YwbYgkq8LMNa8ckLsKmjs
q4ln3bleb43zw/+R7t2psZA8vzBuZ6WEky9EK9Ak3nnL+Fmewp53Q5bAF81zoNTM
sdc8SJyF8uUV7xdjKCcvOC5h0GzkR6w1AEgDfOPeBACxYiMEWpt/gHnNNJ7ui2ql
Sf8lSf26A1at4jXyyNJeAeREhip0EDGdHiwmZ/pmk0KzjWw5EqckjMTahXrer64k
7swIbv94CpmOd2UjD8m0QKUeH8wo/Etkc2197wZFRjyIDTgKUCjoqgSEKqLzN6+q
vFBiAPubU1Cpx/FjWwLRBIKaYjn4wgoJ5BZ1lg53QT3aBJjyhIAayy8+iE6s3q4T
8y2rDHuW+RUQZROdvrQ2xZARQgijLZKIIRrqVe/KR4LUTLa8ZI/95y7r9HiwqKfW
9juYSF6XNAsMCASZriiN
=TLk9
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.