Ben Greear wrote:
> I created a volume, which showed up as /dev/disk/by-path/foo-iscsi-...
> I then did an fdisk on it, which appeared to work:
> fdisk /dev/disk/by-path/....
> After that, it no longer showed up in /dev/disk/by-path/
> but it did exist as /dev/sdc and the partition at /dev/sdc1 was writable.

The iscsi code and tools have nothing to do with making the udev paths, 
and for partitioning a disk the iscsi code is just a passthrough mostly 
sending/receiving iscsi packets to accomplish the upper layers requests, 
so I am not going to be much help here.  Maybe you will get lucky and 
there will be a udev hacker here. If not then the udev list might be best.

My guess:
Udev probably gets some event for new partition and the iscsi udev rule 
is not handling it correctly and killing all the links.

> This was 2.6.29-rc7 (plus my hacks, but no hacks anywhere near iscsi).
> Aside from that, seems to be working marvelously, binding to local
> addresses as I wish.
> Thanks,
> Ben

You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to