xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
* xen DomU image on RAID5 + XFS causes issues with tap:aio
@ 2010-04-26 20:05 netwiz
  0 siblings, 0 replies; 2+ messages in thread
From: netwiz @ 2010-04-26 20:05 UTC (permalink / raw)
  To: xen-devel


Hi all,

Firstly, I'm not subscribed to this list so please CC me into replies.

Upon bashing my head against a wall trying to get Xen working on my new
hardware I came across an interesting discovery. Every install using
virt-install was failing and I could only use the file: access method for
my DomUs. Every time I tries to use tap:aio the guest would error on boot
saying it couldn't find the root partition.

My system is as follows:
OS: CentOS 5.4
Xen: 3.0.3-94.el5_4.3
/ = 2 x 80Gb HDDs, dmraid1, ext3
/mnt/raid = 3 x 1Tb HDDs, dmraid5, xfs

On whim, I moved the DomU images from /mnt/raid/vm-images to /vm-images
and instantly tap:aio worked again.

This brings me to my question:

Why would tap:aio fail when the images are on an XFS/RAID5 filesystem but
work correctly when on a RAID1/ext3 filesystem?

To me, this seems like a bug.

--
Steven Haigh
http://www.crc.id.au

^ permalink raw reply	[flat|nested] 2+ messages in thread
* xen DomU image on RAID5 + XFS causes issues with tap:aio
@ 2010-04-26 20:07 Steven Haigh
  0 siblings, 0 replies; 2+ messages in thread
From: Steven Haigh @ 2010-04-26 20:07 UTC (permalink / raw)
  To: xen-devel


Hi all,

Firstly, I'm not subscribed to this list so please CC me into replies.

Upon bashing my head against a wall trying to get Xen working on my new
hardware I came across an interesting discovery. Every install using
virt-install was failing and I could only use the file: access method for
my DomUs. Every time I tries to use tap:aio the guest would error on boot
saying it couldn't find the root partition.

My system is as follows:
OS: CentOS 5.4
Xen: 3.0.3-94.el5_4.3
/ = 2 x 80Gb HDDs, dmraid1, ext3
/mnt/raid = 3 x 1Tb HDDs, dmraid5, xfs

On whim, I moved the DomU images from /mnt/raid/vm-images to /vm-images
and instantly tap:aio worked again.

This brings me to my question:

Why would tap:aio fail when the images are on an XFS/RAID5 filesystem but
work correctly when on a RAID1/ext3 filesystem?

To me, this seems like a bug.

-- 
Steven Haigh
 
Email: netwiz@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-04-26 20:07 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-26 20:05 xen DomU image on RAID5 + XFS causes issues with tap:aio netwiz
  -- strict thread matches above, loose matches on Subject: below --
2010-04-26 20:07 Steven Haigh

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).