Bug 499630 - F-11 Xen 64-bit domU hangs when trying to format a fake 5TB disk
F-11 Xen 64-bit domU hangs when trying to format a fake 5TB disk
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Xen Maintainance List
Fedora Extras Quality Assurance
Depends On:
Blocks: F11VirtTarget 523128
  Show dependency treegraph
Reported: 2009-05-07 09:45 EDT by Chris Lalancette
Modified: 2010-06-28 08:25 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 523128 (view as bug list)
Last Closed: 2010-06-28 08:25:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Lalancette 2009-05-07 09:45:17 EDT
Description of problem:
I'm following the test case here:


In step 6, we use a script to generate a fake 5TB disk and then attach that to the F-11 domU.  That part works fine, and inside the guest I could then partition the resulting disk using parted.  However, trying to do mkfs.ext4 on that partition resulted in a hard-lockup of the domU.  Unfortunately, I don't have much more information than that, and I'm not sure if this is a dom0 or domU bug.  However, it should be easily reproducible.

The domU kernel is
Comment 1 Stephen Tweedie 2009-05-08 13:59:48 EDT
verify-data ---


was written precisely to test read/write access to very large devices and files, and may be of help in debugging exactly where the IO goes wrong here.
Comment 2 Jeremy Fitzhardinge 2009-06-03 03:00:42 EDT
When you say "hard lockup", do you mean nothing is working at all, or that usermode doesn't work?  Does it respond to sysrq?

I don't think #503840 is Xen-specific, but there's enough overlap (Xen+ext4) to be a bit worrying.
Comment 3 Bug Zapper 2009-06-09 11:19:50 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 4 Bug Zapper 2010-04-27 10:11:19 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 5 Bug Zapper 2010-06-28 08:25:16 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.