WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 262] New: filesystem test on domU's SAN disk hangs

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 262] New: filesystem test on domU's SAN disk hangs
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 26 Sep 2005 22:04:18 +0000
Delivery-date: Mon, 26 Sep 2005 22:04:27 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=262

           Summary: filesystem test on domU's SAN disk hangs
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: hien1@xxxxxxxxxx
                CC: hohnbaum@xxxxxxxxxx


Hardware: x335 SLES9 base 2GB RAM

x335-hien2:/xen-unstable.hg # hg tip
changeset:   6882:75fe7890cf013178e376b88e00158c5b9c8c4324
tag:         tip
user:        cl349@xxxxxxxxxxxxxxxxxxxx
date:        Thu Sep 15 13:39:17 2005
summary:     Export block device read-only state into store.

dom0 built with Emulex driver module for SAN disk. The domU configured with
physical disk (sde2) in its config file. Run fs_di test on /dev/sde2. The test
run for a while and got IO error in dmesg:

 end_request: I/O error, dev sde2, sector 29168072
end_request: I/O error, dev sde2, sector 29174488
end_request: I/O error, dev sde2, sector 29176536
end_request: I/O error, dev sde2, sector 29177560
end_request: I/O error, dev sde2, sector 29179096
end_request: I/O error, dev sde2, sector 29186272
end_request: I/O error, dev sde2, sector 29190888
end_request: I/O error, dev sde2, sector 29194472
end_request: I/O error, dev sde2, sector 29204728
end_request: I/O error, dev sde2, sector 29209336
end_request: I/O error, dev sde2, sector 29210872
end_request: I/O error, dev sde2, sector 29210960
end_request: I/O error, dev sde2, sector 29216512
end_request: I/O error, dev sde2, sector 29216600
end_request: I/O error, dev sde2, sector 29219072
......
......

domU's config file:
# Kernel image file.
kernel = "/boot/vmlinuz-2.6-xenU"
# Optional ramdisk.
# ramdisk = "/boot/initrd-2.6.12-xenU"
# The domain build function. Default is 'linux'.
builder='linux'
# Initial memory allocation (in megabytes) for the new domain.
# memory = 256
memory = 128
cpus = 2
# A name for your domain. All domains must have different names.
name = "x335-hien2-vm1"
disk =  [ 'file:/SLES9-FILEVBD1/sles9-32-filevbd3,sde1,w',
          'phy:sde2,sde2,w' ]
# Set if you want dhcp to allocate the IP address.
# vif =  [ 'mac= AA:00:00:17:12:6E, ip=10.5.1.1' ]
vif =  [ 'mac= AA:00:00:17:12:6E, ip=9.3.189.241' ]
# Set if you want dhcp to allocate the IP address.
# dhcp="dhcp"
# Set netmask.
netmask = '255.255.255.0'
# Set default gateway.
gateway = '10.5.1.1'
# Set the hostname.
hostname= "x335-sles9-vm1"
 
 
# Set root device.
root = "/dev/sde1 ro"
----------
ps -ef shows that the cp command hangs:

root      2885  2865  0 15:25 tty1     00:00:00 -bash
root      2991  2885  0 15:33 tty1     00:00:00 /bin/bash ./fs_ditest.sh 
/dev/sde2
root      2993     5  0 15:33 ?        00:00:00 [pdflush]
root      3001  2991  0 15:35 tty1     00:00:00 /bin/sh /root/test/fstests/fs_di
-d /testext2/fs_ditest -l 1000 -
root      3002  2991  0 15:35 tty1     00:00:00 tee -a
/root/test/fstests/logs/fs_di.testext2.log
root      3074  3001  0 15:40 tty1     00:00:00 cp
/testext2/fs_ditest/fs_di-3001/XXXXXXXXXXXXXXXXXXXX/XXXXXXXXXX

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 262] New: filesystem test on domU's SAN disk hangs, bugzilla-daemon <=