I'm working too on this issue. As we see with on initiator side lvm
info not updated at all. It does not sees any changes on exported disk
that contains lvm.
Does it possible that lvm cache info or scst cache it?
I'm try to remove /etc/lvm/.cache dir but this not change anything.

2013/10/16 Egor Medvedev <[email protected]>:
> Hello everyone.
>
>
> I have a strange problem with scst v3 and lvm.
>
>
> Lets say, I have 2 nodes.
>
>
> node-1, that have some lv's. I export them to other nodes with srp.
>
> node-2 work machine, connects to node-1
>
>
> After upgrading to scst 3 on node-1, I can't see new LV's.
>
>
> Here is an example:
>
>
> ====
>
> root@node-1:~# lvs | grep 63161
>
>   1_63161_1      node-1 -wi-a---   5.00g
>
>   1_63161_2      node-1 -wi-a---   5.00g
>
>   2_63161_1      node-1 -wi-a---   5.00g
>
>   2_63161_3      node-1 -wi-a---   5.00g
>
>   3_63161_1      node-1 -wi-a---   5.00g
>
> ====
>
> 3_63161_1 was created after upgrade
>
>
> output on node-2:
>
> ====
>
> root@node-2:~ # lvs | grep 63161
>
>   1_63161_1      node-1 -wi---   5.00G
>
>   1_63161_2      node-1 -wi---   5.00G
>
>   2_63161_1      node-1 -wi---   5.00G
>
>   2_63161_3      node-1 -wi---   5.00G
>
>
> ====
>
> Can't find any useful information with dmesg.
>
>
> Any ideas?
>
>
> --
> Best Regards,
> Egor
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
> _______________________________________________
> Scst-devel mailing list
> https://lists.sourceforge.net/lists/listinfo/scst-devel
>



-- 
Vasiliy Tolstov,
e-mail: [email protected]
jabber: [email protected]
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to