|Main Archive Page > Month Archives > drbd-user archives|
Dan Barker, you are my hero !
In my iSCSI config on my DRBD hosts, I had :
So, iSCSI use some caching, and replacing by :
works perfectly now !
Thank you everyone for suggestions :)
Last question for you Dan : where did you find that was iSCSI blockio
the answer of your problems ?
On Fri, Mar 12, 2010 at 11:34 PM, dbarker <email@example.com> wrote:
> You observe that data written on some iscsi client
> to a target on top of DRBD is not (immediately) visible
> from some other iscsi client.
> This I have to believe you.
> I haven't figured out the structure here from these messages, but I did see
> the keyword iSCSI. I had similar problems with iscsi-target LUNs on drbd
> when I had them defined as fileio. iscsi-target was caching. Changing the
> definitions to blockio fixed all. Don't know if this is applicable to your
> situation, but the following worked for me. I was using a VMFS filesystem on
> the iSCSI targets.
> Dan Barker
> cat /etc/ietd.conf
> Target iqn.2010-03.com.visioncomm.Storage00:Storage00
> Lun 0 Path=/dev/drbd1,Type=blockio,ScsiSN=SPIDSK-090311-00
> Lun 1 Path=/dev/drbd2,Type=blockio,ScsiSN=SPIDSK-090312-00
> Alias iDISK0
> View this message in context: http://old.nabble.com/Re%3A-Detection-of-Logical-Volume-on-nested-LVM-tp27805567p27883699.html
> Sent from the DRBD - User mailing list archive at Nabble.com.
> drbd-user mailing list
drbd-user mailing list