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 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
> pro
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 Ra
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
> > K
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 bu
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 wan
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
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 i
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-multipa
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 Tris
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.000
11 matches
Mail list logo