Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: Changing Block device to Iscsi ?

  1. #1

    Changing Block device to Iscsi ?

    So this server has been running for more then a year now, and I'm finding the throughput still slow.
    We have SLES Dom0, with OES11 running as domu
    Dom0 has a separate RAID, which is presented to the OES11 as Xen Block device.
    On this block device the OES11 domu has created NSS volumes
    When doing a server reboot the OES11, is taking forever to load the block device ( 5 minutes )

    So I am thinking : what about Iscsi ?
    So my question to you all is :
    Can I turn the block device into a Isci share ?
    Will the OES11 keep it's NSS volumes ?
    How is this best done ?

    Thanks, Stephan

  2. #2

    Re: Changing Block device to Iscsi ?

    stelgenkamp wrote:

    >
    > So this server has been running for more then a year now, and I'm
    > finding the throughput still slow.
    > We have SLES Dom0, with OES11 running as domu
    > Dom0 has a separate RAID, which is presented to the OES11 as Xen Block
    > device.
    > On this block device the OES11 domu has created NSS volumes


    All of this seems quite normal

    > When doing a server reboot the OES11, is taking forever to load the
    > block device ( 5 minutes )


    This is the issue that needs to be investigated.
    >
    > So I am thinking : what about Iscsi ?
    > So my question to you all is :
    > Can I turn the block device into a Isci share ?
    > Will the OES11 keep it's NSS volumes ?
    > How is this best done ?


    You should not make random changes to the system with the hope the
    problem will be corrected.


    The first step is to diagnose the cause:

    1. We need to know what software versions you are running. On both Dom0
    and DomU please run "cat /etc/*release". Copy the output and paste it
    into your reply using <code tags>.

    <code tags>: When replying, click the "Go Advanced" button then click
    on the "#" at the top of the reply window.

    2. Look for any clues in /var/log/messages on both Dom0 and DomU.
    Report any interesting messages the same way.



    --
    Kevin Boyle - Knowledge Partner
    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...

  3. #3

    Re: Changing Block device to Iscsi ?

    Dear Kevin,

    In /var/log/message, I could not find anything on this.

    In startup log :
    <6>[ 1.644885] xvdg: detected capacity change from 0 to 476999319552
    <4>[ 6.565997] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...2 60s...255s...250s...245s...240s...235s...230s...22 5s...220s...215s...210s...205s...200s...195s...190 s...185s...180s...175s...170s...165s...160s...155s ...150s...145s...140s...135s...130s...125s...120s. ..115s...110s...105s...100s...95s...90s...85s...80 s...75s...70s...65s...60s...55s...50s...45s...40s. ..35s...30s...25s...20s...15s...10s...5s...0s...
    <4>[ 301.567897] XENBUS: Timeout connecting to device: device/vbd/51840 (local state 3, remote state 2)
    <4>[ 301.570968] XENBUS: Device not ready: device/vbd/51840

    Version virtual OES :
    Code:
    OES server
    LSB_VERSION="core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64"
    Novell Open Enterprise Server 11 (x86_64)
    VERSION = 11
    PATCHLEVEL = 0
    SUSE Linux Enterprise Server 11 (x86_64)
    VERSION = 11
    PATCHLEVEL = 1
    Version Xen Host :
    Code:
    LSB_VERSION="core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64"
    SUSE Linux Enterprise Server 11 (x86_64)
    VERSION = 11
    PATCHLEVEL = 2

  4. #4

    Re: Changing Block device to Iscsi ?

    Hi Stephan,

    Have you tried a Google search on "XENBUS: Waiting for devices to
    initialise"? There are quite a few hits but I have no way to know if
    one of them is your issue.

    Current software releases are:
    SLES11-SP3
    OES11-SP1 on SLES11-SP2

    They contain many bug fixes which may resolve your issue. Have you
    considered upgrading to the current releases?

    You said:
    > So this server has been running for more then a year now, and I'm
    > finding the throughput still slow.


    Are you saying that this issue existed from the time your DomU was
    initially configured?

    If you running other DomUs, do any of them have similar issues?

    Please run these commands on Dom0 and paste the output into your reply
    using "code" tags.

    Code:
    fdisk -l
    xm list
    xm list -l <name of your OES11 DomU>


    --
    Kevin Boyle - Knowledge Partner
    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...

  5. #5

    Re: Changing Block device to Iscsi ?

    Right, have updated the Xen Server to SP3

    Only updating the OES server did give a bad side effect. :-(
    So now the OES11 is booting without any issues,
    but now the Gnome desktop looks screwed.
    I cannot login. the login screen is shown, I login, it starts loading the desktop.
    Somehow crashes and returns to the login screen.

  6. Re: Changing Block device to Iscsi ?

    Hi Stephan,

    > I cannot login. the login screen is shown, I login, it starts loading the desktop.
    > Somehow crashes and returns to the login screen.

    Have you had a look at the ~/.xsession-errors-* file(s), there might be some information on what program failed during desktop initialization.

    Regards,
    Jens
    From the times when today's "old school" was "new school"

    If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...

  7. #7

    Re: Changing Block device to Iscsi ?

    Christmas time ; so finally some off time to check out what happened.
    ./xsession-errors shows :
    Code:
    /etc/X11/xim: Checking whether an input method should be started.
    /etc/X11/xim: use GDM_LANG=nl_NL.UTF-8
    sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
    INPUT_METHOD is not set or empty (no user selected input method).
    Trying to start a default input method for the locale nl_NL.UTF-8 ...
    There is no default input method for the current locale.
    Dummy input method "none" (do not use any fancy input method by default)
    /usr/bin/gpg-agent: symbol lookup error: /lib64/libgcrypt.so.11: undefined symbol: gpg_err_set_errno
    Have no idea how to fix an input method ...
    Any help would be appreciated.
    Stephan

  8. #8

    Re: Changing Block device to Iscsi ?

    Have found a TID on the subject
    http://www.novell.com/support/kb/doc.php?id=7013143
    Will try that tomorrow.

  9. Re: Changing Block device to Iscsi ?

    Hi Stephan,
    Quote Originally Posted by stelgenkamp View Post
    Have found a TID on the subject
    http://www.novell.com/support/kb/doc.php?id=7013143
    Will try that tomorrow.
    not that I could have pointed you at that TID, but that error message caught my eye and made me more suspicious than the input device stuff. Looks to me like an upgrade problem, the TID is likely right on the spot.

    Happy holidays,
    Jens
    From the times when today's "old school" was "new school"

    If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...

  10. #10

    Re: Changing Block device to Iscsi ?

    OK, we're back.
    Have solved the libcrypt 'challenge' and now are back in business.

    However the : "XENBUS: Waiting for devices to initialise" 'challenge' has returned.

    Code:
    (domain
        (domid 28)
        (cpu_weight 256)
        (cpu_cap 0)
        (pool_name Pool-0)
        (bootloader /usr/lib/xen/boot/domUloader.py)
        (vcpus 4)
        (cpus (() () () ()))
        (on_poweroff destroy)
        (description None)
        (on_crash destroy)
        (uuid ecf1c574-5b7b-d898-8415-9122fc4f513e)
        (bootloader_args '--entry=xvda1:/boot/vmlinuz-xen,/boot/initrd-xen')
        (name oes2l)
        (on_reboot restart)
        (maxmem 3072)
        (memory 3072)
        (shadow_memory 0)
        (features '')
        (on_xend_start ignore)
        (on_xend_stop ignore)
        (start_time 1388090521.29)
        (cpu_time 24261.1702008)
        (online_vcpus 4)
        (image
            (linux
                (kernel '')
                (args ' ')
                (superpages 0)
                (pci ())
                (localtime 0)
                (nomigrate 0)
                (tsc_mode 0)
                (device_model /usr/lib/xen/bin/qemu-dm)
                (notes
                    (FEATURES
                        'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|supervisor_mode_kernel'
                    )
                    (VIRT_BASE 18446744071562067968)
                    (GUEST_VERSION 2.6)
                    (PADDR_OFFSET 0)
                    (GUEST_OS linux)
                    (HYPERCALL_PAGE 18446744071562080256)
                    (LOADER generic)
                    (INIT_P2M 18446719884453740544)
                    (SUSPEND_CANCEL 1)
                    (ENTRY 18446744071562076160)
                    (XEN_VERSION xen-3.0)
                    (MOD_START_PFN 1)
                    (SUPPORTED_FEATURES 2063)
                )
            )
        )
        (status 2)
        (state -b----)
        (store_mfn 8388923)
        (console_mfn 8388922)
        (device
            (vif
                (mac 00:16:3e:10:09:17)
                (script /etc/xen/scripts/vif-bridge)
                (uuid 340c40d7-ca68-9ce8-89be-34b6695c1dab)
                (backend 0)
            )
        )
        (device (vkbd (backend 0)))
        (device
            (tap
                (protocol x86_64-abi)
                (uuid 4f394d94-23af-09ff-5ca7-7437cb09b193)
                (bootable 0)
                (dev xvdh:cdrom)
                (uname
                    tap:aio:/root/Installatie/OES11-SP1-addon_with_SLES11-SP2-x86_64-DVD.iso
                )
                (mode r)
                (backend 0)
                (VDI '')
            )
        )
        (device
            (console
                (protocol vt100)
                (location 2)
                (uuid d3773870-144f-a7ff-c443-b77012a5b695)
            )
        )
        (device
            (vbd
                (protocol x86_64-abi)
                (uuid 934b82e4-848b-067b-05f6-1997c848c332)
                (bootable 1)
                (dev xvda:disk)
                (uname phy:/dev/Linux/boot)
                (mode w)
                (backend 0)
                (VDI '')
            )
        )
        (device
            (vbd
                (protocol x86_64-abi)
                (uuid aa14a6f0-9a1f-f172-fead-976ad410742f)
                (bootable 0)
                (dev xvdb:disk)
                (uname phy:/dev/Linux/root)
                (mode w)
                (backend 0)
                (VDI '')
            )
        )
        (device
            (vbd
                (protocol x86_64-abi)
                (uuid 001faa38-93c5-c952-ce20-f821c190823f)
                (bootable 0)
                (dev xvdc:disk)
                (uname phy:/dev/Linux/swap)
                (mode w)
                (backend 0)
                (VDI '')
            )
        )
        (device
            (vbd
                (protocol x86_64-abi)
                (uuid 9d5c94c5-8538-f6a3-f3b9-1db33c79a9e8)
                (bootable 0)
                (dev xvdd:disk)
                (uname phy:/dev/Linux/opt)
                (mode w)
                (backend 0)
                (VDI '')
            )
        )
        (device
            (vbd
                (protocol x86_64-abi)
                (uuid af5a5d8c-a878-49f8-ee36-63a74c781f07)
                (bootable 0)
                (dev xvde:disk)
                (uname phy:/dev/Linux/home)
                (mode w)
                (backend 0)
                (VDI '')
            )
        )
        (device
            (vbd
                (protocol x86_64-abi)
                (uuid 37784803-f92b-4880-3669-7e42ca00dfe8)
                (bootable 0)
                (dev xvdf:disk)
                (uname phy:/dev/Linux/var)
                (mode w)
                (backend 0)
                (VDI '')
            )
        )
        (device
            (vbd
                (protocol x86_64-abi)
                (uuid ff66c73f-8c4f-1c37-8b66-cddce5f5cb51)
                (bootable 0)
                (dev xvdg:disk)
                (uname phy:/dev/sdb)
                (mode w)
                (backend 0)
                (VDI '')
            )
        )
        (device
            (vbd
                (protocol x86_64-abi)
                (uuid eacb8f4b-ad49-b844-1d38-6a03efb98443)
                (bootable 0)
                (dev xvdi:cdrom)
                (uname phy:/dev/sr0)
                (mode r)
                (backend 0)
                (VDI '')
            )
        )
        (device
            (vfb
                (vncunused 1)
                (keymap en-us)
                (vnc 1)
                (uuid 73f26216-6efa-2bad-741c-ce83b198fb43)
                (location 127.0.0.1:5902)
            )
        )
    )
    The device which is showing the XENBUS wait is : phy:/dev/sdb
    This is a separate raid-5 on my xen host.
    Any ideas ?

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •