CINXE.COM
Bug #244808 “{upstream} --incremental --scan --run does not star...” : Bugs : mdadm package : Ubuntu
<!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr"> <head> <base href="https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/244808/+index" /> <meta charset="UTF-8" /> <title>Bug #244808 “{upstream} --incremental --scan --run does not star...” : Bugs : mdadm package : Ubuntu</title> <link rel="apple-touch-icon" sizes="180x180" href="/@@/apple-touch-icon.png?v=2022" /> <link rel="icon" type="image/png" sizes="32x32" href="/@@/favicon-32x32.png?v=2022" /> <link rel="icon" type="image/png" sizes="16x16" href="/@@/favicon-16x16.png?v=2022" /> <link rel="manifest" href="/@@/site.webmanifest?v=2022" /> <link rel="mask-icon" href="/@@/safari-pinned-tab.svg?v=2022" color="#e9531f" /> <link rel="shortcut icon" href="/@@/favicon.ico?v=2022" /> <meta name="msapplication-TileColor" content="#da532c" /> <meta name="msapplication-config" content="/@@/browserconfig.xml?v=2022" /> <meta name="theme-color" content="#ffffff" /> <link rel="canonical" href="https://bugs.launchpad.net/bugs/244808" /> <link rel="alternate" type="application/atom+xml" href="http://feeds.launchpad.net/bugs/244808/bug.atom" title="Bug 244808 Feed" /> <link type="text/css" rel="stylesheet" media="screen, print" href="/+icing/revaa29ae0fff49e4e804b39147c9f259d2fb023199/combo.css" /> <meta name="description" content="Binary package hint: mdadm (ubuntu 8.04) The man page suggests that "mdadm -IRs" will start the arrays that have been assembled incrementally, but which are still missing some redundant members (degraded mode). But this does not seem to have any effect on inactive arrays here. ("mdadm --incremental --scan --run" does not start the (multiple) arrays that have been partially assembled by prior "mdadm --incremental <devices>" commands.) " /> <meta property="og:description" content="Binary package hint: mdadm (ubuntu 8.04) The man page suggests that "mdadm -IRs" will start the arrays that have been assembled incrementally, but which are still missing some redundant members (degraded mode). But this does not seem to have any effect on inactive arrays here. ("mdadm --incremental --scan --run" does not start the (multiple) arrays that have been partially assembled by prior "mdadm --incremental <devices>" commands.) " /> <meta property="og:title" content="Bug #244808 “{upstream} --incremental --scan --run does not star...” : Bugs : mdadm package : Ubuntu" /> <meta property="og:type" content="website" /> <meta property="og:image" content="/@@/launchpad-og-image.png" /> <meta property="og:url" content="https://bugs.launchpad.net/bugs/244808" /> <meta property="og:site_name" content="Launchpad" /> <script type="text/javascript"> var LP = { cache: {}, links: {} }; </script> <script type="text/javascript">var cookie_scope = '; Path=/; Secure; Domain=.launchpad.net';</script> <script type="text/javascript" src="/+combo/revaa29ae0fff49e4e804b39147c9f259d2fb023199/?yui/yui/yui-min.js&lp/meta.js&yui/loader/loader-min.js"></script> <script type="text/javascript"> var raw = null; if (LP.devmode) { raw = 'raw'; } YUI.GlobalConfig = { combine: true, comboBase: '/+combo/revaa29ae0fff49e4e804b39147c9f259d2fb023199/?', root: 'yui/', filter: raw, debug: false, fetchCSS: false, maxURLLength: 2000, groups: { lp: { combine: true, base: '/+combo/revaa29ae0fff49e4e804b39147c9f259d2fb023199/?lp/', comboBase: '/+combo/revaa29ae0fff49e4e804b39147c9f259d2fb023199/?', root: 'lp/', // comes from including lp/meta.js modules: LP_MODULES, fetchCSS: false } } }</script> <script type="text/javascript"> // we need this to create a single YUI instance all events and code // talks across. All instances of YUI().use should be based off of // LPJS instead. var LPJS = new YUI(); </script> <script id="base-layout-load-scripts" type="text/javascript"> //<![CDATA[ LPJS.use('base', 'node', 'console', 'event', 'oop', 'lp', 'lp.app.foldables','lp.app.sorttable', 'lp.app.inlinehelp', 'lp.app.links', 'lp.bugs.bugtask_index', 'lp.bugs.subscribers', 'lp.app.ellipsis', 'lp.code.branchmergeproposal.diff', 'lp.views.global', function(Y) { Y.on("domready", function () { var global_view = new Y.lp.views.Global(); global_view.render(); Y.lp.app.sorttable.SortTable.init(); Y.lp.app.inlinehelp.init_help(); Y.lp.activate_collapsibles(); Y.lp.app.foldables.activate(); Y.lp.app.links.check_valid_lp_links(); }); Y.on('lp:context:web_link:changed', function(e) { window.location = e.new_value; }); }); //]]> </script> <script id="base-helper-functions" type="text/javascript"> //<![CDATA[ // This code is pulled from lp.js that needs to be available on every // request. Pulling here to get it outside the scope of the YUI block. function setFocusByName(name) { // Focus the first element matching the given name which can be focused. var nodes = document.getElementsByName(name); var i, node; for (i = 0; i < nodes.length; i++) { node = nodes[i]; if (node.focus) { try { // Trying to focus a hidden element throws an error in IE8. if (node.offsetHeight !== 0) { node.focus(); } } catch (e) { LPJS.use('console', function(Y) { Y.log('In setFocusByName(<' + node.tagName + ' type=' + node.type + '>): ' + e); }); } break; } } } function selectWidget(widget_name, event) { if (event && (event.keyCode === 9 || event.keyCode === 13)) { // Avoid firing if user is tabbing through or simply pressing // enter to submit the form. return; } document.getElementById(widget_name).checked = true; } //]]> </script> <script type="text/javascript" id="available-official-tags-js">var available_official_tags = ["a11y", "appstream", "bionic", "bisect-done", "bitesize", "block-proposed", "block-proposed-focal", "block-proposed-jammy", "block-proposed-noble", "block-proposed-oracular", "cherry-pick", "community-security", "desktop-file", "dist-upgrade", "fixed-upstream", "focal", "ftbfs", "hw-specific", "jammy", "kernel-bug", "manpage", "metabug", "multiarch", "multigpu", "multimonitor", "needs-bisect", "needs-design", "needs-packaging", "needs-reassignment", "noble", "nvidia", "oracular", "package-conflict", "packaging", "patch", "patch-accepted-debian", "patch-accepted-upstream", "patch-forwarded-debian", "patch-forwarded-upstream", "patch-needswork", "patch-rejected", "patch-rejected-debian", "patch-rejected-upstream", "performing-bisect", "plucky", "qt4-removal", "regression-proposed", "regression-release", "regression-update", "string-fix", "suspend-resume", "systemd-boot", "testcase", "unmetdeps", "update-excuse", "upgrade-software-version", "verification-done-bionic", "verification-done-focal", "verification-done-jammy", "verification-done-noble", "verification-done-oracular", "verification-failed-bionic", "verification-failed-jammy", "verification-needed-bionic", "verification-needed-focal", "verification-needed-jammy", "verification-needed-noble", "verification-needed-oracular", "wayland"];</script> <script type="text/javascript"> LPJS.use('base', 'node', 'oop', 'event', 'lp.bugs.bugtask_index', 'lp.bugs.subscribers', 'lp.code.branchmergeproposal.diff', 'lp.app.comment', 'lp.services.messages.edit', function(Y) { Y.on('domready', function() { Y.lp.code.branchmergeproposal.diff.connect_diff_links(); Y.lp.bugs.bugtask_index.setup_bugtask_index(); Y.lp.bugs.bugtask_index.setup_bugtask_table(); LP.cache.comment_context = LP.cache.bug; var cl = new Y.lp.app.comment.CommentList(); cl.render(); var sl = new Y.lp.bugs.subscribers.createBugSubscribersLoader({ container_box: '#other-bug-subscribers', subscribers_details_view: '/+bug-portlet-subscribers-details', subscribe_someone_else_link: '.menu-link-addsubscriber' }, window); Y.lp.services.messages.edit.setup(); }); }); </script> <style type="text/css"> /* Align the 'add comment' link to the right of the comment box. */ #add-comment-form textarea { width: 100%; } #add-comment-form { max-width: 60em; padding-bottom: 4em; } #add-comment-form .actions {float: right;} .buglink-summary dd { font-size: 10px; } a#privacy-link:link:hover, a#privacy-link:visited:hover {text-decoration:none;} </style> <style type="text/css"> .yui3-overlay .value label { /* It normally makes sense for form labels to be bold, but since this form consists only of radio buttons, there's nothing but labels so we just get wall-to-wall bold. */ font-weight: normal !important; } </style> </head> <body id="document" itemscope="" itemtype="http://schema.org/WebPage" class="tab-bugs main_side public yui3-skin-sam"> <div class="yui-d0"> <div id="locationbar" class="login-logout"> <div id="logincontrol"><a href="https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/244808/+login">Log in / Register</a></div> </div><!--id="locationbar"--> <div id="watermark" class="watermark-apps-portlet"> <div> <a href="https://launchpad.net/ubuntu"><img alt="" width="64" height="64" src="https://launchpadlibrarian.net/606381979/CoF%2064px.png" /></a> </div> <div class="wide"> <h2 id="watermark-heading"><a href="https://launchpad.net/ubuntu">Ubuntu</a><br /><a href="https://launchpad.net/ubuntu/+source/mdadm">mdadm package</a></h2> </div> <!-- Application Menu --> <ul class="facetmenu"> <li class="overview"><a href="https://launchpad.net/ubuntu/+source/mdadm">Overview</a></li> <li class="branches"><a href="https://code.launchpad.net/ubuntu/+source/mdadm">Code</a></li> <li class="bugs active"><a href="https://bugs.launchpad.net/ubuntu/+source/mdadm">Bugs</a></li> <li class="specifications disabled-tab"><span>Blueprints</span></li> <li class="translations"><a href="https://translations.launchpad.net/ubuntu/+source/mdadm">Translations</a></li> <li class="answers"><a href="https://answers.launchpad.net/ubuntu/+source/mdadm">Answers</a></li> </ul> </div> <div class="yui-t4"> <div id="maincontent" class="yui-main"> <div class="yui-b" dir="ltr"> <div class="context-publication"> <h1 id="edit-title"> <span class="yui3-editable_text-text ellipsis" style="max-width: 95%;"> {upstream} --incremental --scan --run does not start anything </span> </h1> <div id="registration" class="registering"> Bug #244808 reported by <a href="https://launchpad.net/~ceg" class="sprite person">ceg</a> <time title="2008-07-02 09:19:27 UTC" datetime="2008-07-02T09:19:27.469649+00:00">on 2008-07-02</time> </div> </div> <div id="request-notifications"> </div> <div> <div id="bug-is-duplicate"> </div> <div style="float: right;"> <span><a href="/+help-bugs/bug-heat.html" target="help" class="sprite flame">4</a></span> </div> <table id="affected-software" class="listing"> <thead> <tr> <th colspan="2">Affects</th> <th>Status</th> <th>Importance</th> <th>Assigned to</th> <th>Milestone</th> </tr> </thead> <tbody> <tr id="tasksummary645318"> <td> </td> <td> <span id="bugtarget-picker-tasksummary645318"> <span class="yui3-activator-data-box"> <a class="sprite product" href="https://bugs.launchpad.net/mdadm">mdadm</a> </span> <div class="yui3-activator-message-box yui3-activator-hidden"></div> </span> </td> <td style="width: 20%; vertical-align: middle"> <div class="status-content" style="width: 100%; float: left"> <span style="float: left" class="value statusNEW">New</span> </div> </td> <td style="width: 15em; vertical-align: middle"> <div class="importance-content" style="width: 100%; float: left"> <span style="float: left" class="value importanceUNDECIDED">Undecided</span> </div> </td> <td style="width:20%; margin: 0; padding: 0; vertical-align: middle; padding-left: 0.5em"> <span id="assignee-picker-tasksummary645318"> <span class="yui3-activator-data-box"> Unassigned </span> <div class="yui3-activator-message-box yui3-activator-hidden"></div> </span> </td> <td style="width: 20%; vertical-align: middle"> </td> </tr> <tr class="highlight" id="tasksummary280973"> <td> </td> <td> <span id="bugtarget-picker-tasksummary280973"> <span class="yui3-activator-data-box"> <a class="sprite package-source" href="https://bugs.launchpad.net/ubuntu/+source/mdadm" title="Latest release: 4.4-5ubuntu1, uploaded to main on 2025-02-18 21:54:12.095586+00:00 by Simon Quigley (tsimonq2), maintained by Ubuntu Developers (ubuntu-devel-discuss-lists)">mdadm (Ubuntu)</a> </span> <div class="yui3-activator-message-box yui3-activator-hidden"></div> </span> </td> <td style="width: 20%; vertical-align: middle"> <div class="status-content" style="width: 100%; float: left"> <span style="float: left" class="value statusCONFIRMED">Confirmed</span> </div> </td> <td style="width: 15em; vertical-align: middle"> <div class="importance-content" style="width: 100%; float: left"> <span style="float: left" class="value importanceUNDECIDED">Undecided</span> </div> </td> <td style="width:20%; margin: 0; padding: 0; vertical-align: middle; padding-left: 0.5em"> <span id="assignee-picker-tasksummary280973"> <span class="yui3-activator-data-box"> Unassigned </span> <div class="yui3-activator-message-box yui3-activator-hidden"></div> </span> </td> <td style="width: 20%; vertical-align: middle"> <div class="milestone-content" style="width: 100%; float: left"> <a class="value" href=""></a> </div> </td> </tr> </tbody> </table> <div id="maincontentsub"> <div class="top-portlet"> <div itemprop="mainContentOfPage" class="report"> <div> <div class="lazr-multiline-edit" id="edit-description"> <div class="clearfix"> <h3>Bug Description</h3> </div> <div class="yui3-editable_text-text"><p>Binary package hint: mdadm</p> <p>(ubuntu 8.04)</p> <p>The man page suggests that "mdadm -IRs" will start the arrays that have been assembled incrementally, but which are still missing some redundant members (degraded mode).</p> <p>But this does not seem to have any effect on inactive arrays here.<br /> ("mdadm --incremental --scan --run" does not start the (multiple) arrays that have been partially assembled by prior "mdadm --incremental <devices>" commands.)</p></div> </div> </div> <div style="margin:-10px 0 20px 5px" class="clearfix"> <span>See <a href="comments/0">original description</a></span> </div> <div id="bug-tags"> <span id="tags-heading"> </span> <span id="tag-list"> </span> </div> <script type="text/javascript"> LPJS.use('event', 'node', 'lp.bugs.tags_entry', function(Y) { Y.on('domready', function(e) { Y.lp.bugs.tags_entry.setup_tag_entry( available_official_tags); }, window); }); </script> <div class="clearfix"></div> </div> <div id="branches-and-cves"> <div id="bug-branches-container" style="float: left"> </div><!-- bug-branch-container --> <div class="clearfix"></div> </div> <!-- branches and CVEs --> </div> <div> <div class="boardComment"> <div class="boardCommentDetails"> <a href="https://launchpad.net/~ceg" class="sprite person">ceg (ceg)</a> <time title="2008-07-24 22:01:47 UTC" datetime="2008-07-24T22:01:47.334987+00:00">on 2008-07-24</time> </div> <div class="boardCommentActivity"> <table class="bug-activity"> <tr> <td style="text-align: right;"> <b>description</b>: </td> <td> updated </td> </tr> </table> </div> </div> <div xmlns="http://www.w3.org/1999/xhtml" itemscope="" itemtype="http://schema.org/UserComments" class="boardComment editable-message " data-baseurl="/ubuntu/+source/mdadm/+bug/244808/comments/1" data-i-can-edit="False"> <div class="boardCommentDetails"> <div class="message-revision-container"> <div class="message-revision-container-header"> <span>Revision history for this message</span> <img src="/+icing/build/overlay/assets/skins/sam/images/close.gif" class="message-revision-close" /> </div> <script type="text/template"> <div class='message-revision-item'> <div class='message-revision-title'> <a class="sprite remove action-icon message-revision-del-btn"> Remove </a> <a class="js-action"> Revision #{revision}, created at {date_created_display} </a> </div> <div class='message-revision-body'>{content}</div> </div> </script> <div class="message-revision-list"></div> </div> <table> <tbody> <tr> <td> <a href="https://launchpad.net/~ceg" class="sprite person">ceg (ceg)</a> wrote <time itemprop="commentTime" datetime="2009-11-25T20:47:55.019684+00:00" title="2009-11-25 20:47:55 UTC">on 2009-11-25</time><span class="editable-message-last-edit-date">: </span> </td> <td> </td> <td> </td> <td class="bug-comment-index"> <a itemprop="url" href="/ubuntu/+source/mdadm/+bug/244808/comments/1"> #1</a> </td> </tr> </tbody> </table> </div> <div class="boardCommentBody"> <div class="editable-message-body"> <div class="comment-text editable-message-text" itemprop="commentText"><p>Current state of ubuntu systems with md raid: <a rel="nofollow" href="https://wiki.ubuntu.com/ReliableRaid">https:/<wbr />/wiki.ubuntu.<wbr />com/ReliableRai<wbr />d</a></p></div> </div> <div class="editable-message-form" style="display: none"> <textarea style="width: 100%" rows="10">Current state of ubuntu systems with md raid: https://wiki.ubuntu.com/ReliableRaid</textarea> <input type="button" value="Update" class="editable-message-update-btn" /> <input type="button" value="Cancel" class="editable-message-cancel-btn" /> </div> </div> </div> <div xmlns="http://www.w3.org/1999/xhtml" itemscope="" itemtype="http://schema.org/UserComments" class="boardComment editable-message " data-baseurl="/ubuntu/+source/mdadm/+bug/244808/comments/2" data-i-can-edit="False"> <div class="boardCommentDetails"> <div class="message-revision-container"> <div class="message-revision-container-header"> <span>Revision history for this message</span> <img src="/+icing/build/overlay/assets/skins/sam/images/close.gif" class="message-revision-close" /> </div> <script type="text/template"> <div class='message-revision-item'> <div class='message-revision-title'> <a class="sprite remove action-icon message-revision-del-btn"> Remove </a> <a class="js-action"> Revision #{revision}, created at {date_created_display} </a> </div> <div class='message-revision-body'>{content}</div> </div> </script> <div class="message-revision-list"></div> </div> <table> <tbody> <tr> <td> <a href="https://launchpad.net/~ceg" class="sprite person">ceg (ceg)</a> wrote <time itemprop="commentTime" datetime="2010-03-27T06:37:44.861747+00:00" title="2010-03-27 06:37:44 UTC">on 2010-03-27</time><span class="editable-message-last-edit-date">: </span> </td> <td> </td> <td> </td> <td class="bug-comment-index"> <a itemprop="url" href="/ubuntu/+source/mdadm/+bug/244808/comments/2"> #2</a> </td> </tr> </tbody> </table> </div> <div class="boardCommentBody"> <div class="editable-message-body"> <div class="comment-text editable-message-text" itemprop="commentText"><p>Note that starting all incomplete array indiscriminately is not a good idea in general.</p> <p>i.e. on boot, start only selected arrays degraded that are known to be needed.</p></div> </div> <div class="editable-message-form" style="display: none"> <textarea style="width: 100%" rows="10">Note that starting all incomplete array indiscriminately is not a good idea in general. i.e. on boot, start only selected arrays degraded that are known to be needed.</textarea> <input type="button" value="Update" class="editable-message-update-btn" /> <input type="button" value="Cancel" class="editable-message-cancel-btn" /> </div> </div> </div> <div class="boardComment"> <div class="boardCommentDetails"> <a href="https://launchpad.net/~ceg" class="sprite person">ceg (ceg)</a> <time title="2010-03-31 10:15:30 UTC" datetime="2010-03-31T10:15:30.891525+00:00">on 2010-03-31</time> </div> <div class="boardCommentActivity"> <table class="bug-activity"> <tr> <td style="text-align: right;"> <b>summary</b>: </td> <td> - --incremental --scan --run does not start anything<br />+ [upstream] --incremental --scan --run does not start anything </td> </tr> <tr> <td style="text-align: right;"> <b>summary</b>: </td> <td> - [upstream] --incremental --scan --run does not start anything<br />+ {upstream} --incremental --scan --run does not start anything </td> </tr> </table> </div> </div> <div class="boardComment"> <div class="boardCommentDetails"> <a href="https://launchpad.net/~ceg" class="sprite person">ceg (ceg)</a> <time title="2010-04-01 08:15:41 UTC" datetime="2010-04-01T08:15:41.403084+00:00">on 2010-04-01</time> </div> <div class="boardCommentActivity"> <table class="bug-activity"> <tr> <td colspan="2">Changed in mdadm (Ubuntu): </td> </tr> <tr> <td style="text-align: right;"> <b>status</b>: </td> <td> New → Invalid </td> </tr> </table> </div> </div> <div class="boardComment"> <div class="boardCommentDetails"> <a href="https://launchpad.net/~ceg" class="sprite person">ceg (ceg)</a> <time title="2010-04-01 15:17:24 UTC" datetime="2010-04-01T15:17:24.245333+00:00">on 2010-04-01</time> </div> <div class="boardCommentActivity"> <table class="bug-activity"> <tr> <td colspan="2">Changed in mdadm (Ubuntu): </td> </tr> <tr> <td style="text-align: right;"> <b>status</b>: </td> <td> Invalid → New </td> </tr> </table> </div> </div> <div xmlns="http://www.w3.org/1999/xhtml" itemscope="" itemtype="http://schema.org/UserComments" class="boardComment editable-message " data-baseurl="/ubuntu/+source/mdadm/+bug/244808/comments/3" data-i-can-edit="False"> <div class="boardCommentDetails"> <div class="message-revision-container"> <div class="message-revision-container-header"> <span>Revision history for this message</span> <img src="/+icing/build/overlay/assets/skins/sam/images/close.gif" class="message-revision-close" /> </div> <script type="text/template"> <div class='message-revision-item'> <div class='message-revision-title'> <a class="sprite remove action-icon message-revision-del-btn"> Remove </a> <a class="js-action"> Revision #{revision}, created at {date_created_display} </a> </div> <div class='message-revision-body'>{content}</div> </div> </script> <div class="message-revision-list"></div> </div> <table> <tbody> <tr> <td> <a href="https://launchpad.net/~clint-fewbar" class="sprite person">Clint Byrum (clint-fewbar)</a> wrote <time itemprop="commentTime" datetime="2011-04-26T17:01:17.327338+00:00" title="2011-04-26 17:01:17 UTC">on 2011-04-26</time><span class="editable-message-last-edit-date">: </span> </td> <td> </td> <td> </td> <td class="bug-comment-index"> <a itemprop="url" href="/ubuntu/+source/mdadm/+bug/244808/comments/3"> #3</a> </td> </tr> </tbody> </table> </div> <div class="boardCommentBody"> <div class="editable-message-body"> <div class="comment-text editable-message-text" itemprop="commentText"><p>ceg, I know these have been around a long time without a response. I'd like to know what we can do in Ubuntu to help resolve this issue for you. It would be helpful if you could confirm that this is still a problem for you in the latest release (Ubuntu 11.04 is just about to release on 4/28). Also if you could state clearly:</p> <p>- What you expect the system to do (assemble all inactive arrays?)<br /> - What it actually does (??)<br /> - A clear way we can attempt to confirm this behavior (i.e. break an array and then attempt to activate it?)</p> <p>I'm going to mark this one as Incomplete pending your response.</p></div> </div> <div class="editable-message-form" style="display: none"> <textarea style="width: 100%" rows="10">ceg, I know these have been around a long time without a response. I'd like to know what we can do in Ubuntu to help resolve this issue for you. It would be helpful if you could confirm that this is still a problem for you in the latest release (Ubuntu 11.04 is just about to release on 4/28). Also if you could state clearly: - What you expect the system to do (assemble all inactive arrays?) - What it actually does (??) - A clear way we can attempt to confirm this behavior (i.e. break an array and then attempt to activate it?) I'm going to mark this one as Incomplete pending your response. </textarea> <input type="button" value="Update" class="editable-message-update-btn" /> <input type="button" value="Cancel" class="editable-message-cancel-btn" /> </div> </div> <div class="boardCommentActivity"> <table class="bug-activity"> <tr> <td colspan="2">Changed in mdadm (Ubuntu): </td> </tr> <tr> <td style="text-align: right;"> <b>status</b>: </td> <td> New → Incomplete </td> </tr> </table> </div> </div> <div xmlns="http://www.w3.org/1999/xhtml" itemscope="" itemtype="http://schema.org/UserComments" class="boardComment editable-message " data-baseurl="/ubuntu/+source/mdadm/+bug/244808/comments/4" data-i-can-edit="False"> <div class="boardCommentDetails"> <div class="message-revision-container"> <div class="message-revision-container-header"> <span>Revision history for this message</span> <img src="/+icing/build/overlay/assets/skins/sam/images/close.gif" class="message-revision-close" /> </div> <script type="text/template"> <div class='message-revision-item'> <div class='message-revision-title'> <a class="sprite remove action-icon message-revision-del-btn"> Remove </a> <a class="js-action"> Revision #{revision}, created at {date_created_display} </a> </div> <div class='message-revision-body'>{content}</div> </div> </script> <div class="message-revision-list"></div> </div> <table> <tbody> <tr> <td> <a href="https://launchpad.net/~ceg" class="sprite person">ceg (ceg)</a> wrote <time itemprop="commentTime" datetime="2011-04-28T10:01:29.765745+00:00" title="2011-04-28 10:01:29 UTC">on 2011-04-28</time><span class="editable-message-last-edit-date">: </span> </td> <td> </td> <td> </td> <td class="bug-comment-index"> <a itemprop="url" href="/ubuntu/+source/mdadm/+bug/244808/comments/4"> #4</a> </td> </tr> </tbody> </table> </div> <div class="boardCommentBody"> <div class="editable-message-body"> <div class="comment-text editable-message-text" itemprop="commentText"><p>I'm sorry I won't be able to test 11.04 soon.</p> <p><span class="foldable-quoted">> - A clear way we can attempt to confirm this behavior (i.e. break an array and then attempt to activate it?) </span></p> <p>Most of the issues should be covered by the overview in ReliableRaid and the test cases.<br /> <a rel="nofollow" href="https://wiki.ubuntu.com/ReliableRaid">https:/<wbr />/wiki.ubuntu.<wbr />com/ReliableRai<wbr />d</a> and<br /> <a rel="nofollow" href="http://testcases.qa.ubuntu.com/Install/AlternateRaidMirror">http://<wbr />testcases.<wbr />qa.ubuntu.<wbr />com/Install/<wbr />AlternateRaidMi<wbr />rror</a> with all three partitoning schemes.</p> <p>ReliableRaid says this about the bug at hand:<br /> Using the legacy method to start degraded raids selectively (mdadm --assemble --run -uuid) will break later --incremental (re)additions by udev/hotplugging. (The initramfs currently uses "mdadm --assemble --scan --run" and starts *all* arrays available degraded! 497186. The corresponding command "mdadm --incremental --scan --run" to start *all remaining* hotplugable raids degraded (something still to execute only manually if at all!) does not start anything. 244808)</p> <p><span class="foldable-quoted">> - What you expect the system to do (assemble all inactive arrays?)<br /> By default, it should assemble all raid partitions that are connected with --incremental and run them only when they are complete (as defined by the state of their superblocks) to ensure no arrays are never started partially. </span></p> <p><span class="foldable-quoted">> - What it actually does (??)<br /> On boot, ubuntu starts ALL arrays in degraded mode, if the rootfs is still incomplete after a timeout. It should only start the raids necessary for the rootfs in degraded mode. (how this could be done: see ReliableRaid Wiki) </span></p></div> </div> <div class="editable-message-form" style="display: none"> <textarea style="width: 100%" rows="10">I'm sorry I won't be able to test 11.04 soon. > - A clear way we can attempt to confirm this behavior (i.e. break an array and then attempt to activate it?) Most of the issues should be covered by the overview in ReliableRaid and the test cases. https://wiki.ubuntu.com/ReliableRaid and http://testcases.qa.ubuntu.com/Install/AlternateRaidMirror with all three partitoning schemes. ReliableRaid says this about the bug at hand: Using the legacy method to start degraded raids selectively (mdadm --assemble --run -uuid) will break later --incremental (re)additions by udev/hotplugging. (The initramfs currently uses "mdadm --assemble --scan --run" and starts *all* arrays available degraded! 497186. The corresponding command "mdadm --incremental --scan --run" to start *all remaining* hotplugable raids degraded (something still to execute only manually if at all!) does not start anything. 244808) > - What you expect the system to do (assemble all inactive arrays?) By default, it should assemble all raid partitions that are connected with --incremental and run them only when they are complete (as defined by the state of their superblocks) to ensure no arrays are never started partially. > - What it actually does (??) On boot, ubuntu starts ALL arrays in degraded mode, if the rootfs is still incomplete after a timeout. It should only start the raids necessary for the rootfs in degraded mode. (how this could be done: see ReliableRaid Wiki) </textarea> <input type="button" value="Update" class="editable-message-update-btn" /> <input type="button" value="Cancel" class="editable-message-cancel-btn" /> </div> </div> <div class="boardCommentActivity"> <table class="bug-activity"> <tr> <td colspan="2">Changed in mdadm (Ubuntu): </td> </tr> <tr> <td style="text-align: right;"> <b>status</b>: </td> <td> Incomplete → Confirmed </td> </tr> </table> </div> </div> <div xmlns="http://www.w3.org/1999/xhtml" itemscope="" itemtype="http://schema.org/UserComments" class="boardComment editable-message " data-baseurl="/ubuntu/+source/mdadm/+bug/244808/comments/5" data-i-can-edit="False"> <div class="boardCommentDetails"> <div class="message-revision-container"> <div class="message-revision-container-header"> <span>Revision history for this message</span> <img src="/+icing/build/overlay/assets/skins/sam/images/close.gif" class="message-revision-close" /> </div> <script type="text/template"> <div class='message-revision-item'> <div class='message-revision-title'> <a class="sprite remove action-icon message-revision-del-btn"> Remove </a> <a class="js-action"> Revision #{revision}, created at {date_created_display} </a> </div> <div class='message-revision-body'>{content}</div> </div> </script> <div class="message-revision-list"></div> </div> <table> <tbody> <tr> <td> <a href="https://launchpad.net/~ceg" class="sprite person">ceg (ceg)</a> wrote <time itemprop="commentTime" datetime="2011-04-28T10:09:41.380814+00:00" title="2011-04-28 10:09:41 UTC">on 2011-04-28</time><span class="editable-message-last-edit-date">: </span> </td> <td> </td> <td> </td> <td class="bug-comment-index"> <a itemprop="url" href="/ubuntu/+source/mdadm/+bug/244808/comments/5"> #5</a> </td> </tr> </tbody> </table> </div> <div class="boardCommentBody"> <div class="editable-message-body"> <div class="comment-text editable-message-text" itemprop="commentText"><p>Please don't make the issues dissappear by the incomplete-<wbr />>expiraition mechanism (assume that it has gone away), if they are not confirmed to be fixed.</p> <p>These things are fundamental to know not to use ubuntu for software raid.</p></div> </div> <div class="editable-message-form" style="display: none"> <textarea style="width: 100%" rows="10">Please don't make the issues dissappear by the incomplete->expiraition mechanism (assume that it has gone away), if they are not confirmed to be fixed. These things are fundamental to know not to use ubuntu for software raid.</textarea> <input type="button" value="Update" class="editable-message-update-btn" /> <input type="button" value="Cancel" class="editable-message-cancel-btn" /> </div> </div> </div> <div xmlns="http://www.w3.org/1999/xhtml" itemscope="" itemtype="http://schema.org/UserComments" class="boardComment editable-message " data-baseurl="/ubuntu/+source/mdadm/+bug/244808/comments/6" data-i-can-edit="False"> <div class="boardCommentDetails"> <div class="message-revision-container"> <div class="message-revision-container-header"> <span>Revision history for this message</span> <img src="/+icing/build/overlay/assets/skins/sam/images/close.gif" class="message-revision-close" /> </div> <script type="text/template"> <div class='message-revision-item'> <div class='message-revision-title'> <a class="sprite remove action-icon message-revision-del-btn"> Remove </a> <a class="js-action"> Revision #{revision}, created at {date_created_display} </a> </div> <div class='message-revision-body'>{content}</div> </div> </script> <div class="message-revision-list"></div> </div> <table> <tbody> <tr> <td> <a href="https://launchpad.net/~clint-fewbar" class="sprite person">Clint Byrum (clint-fewbar)</a> wrote <time itemprop="commentTime" datetime="2011-04-28T16:08:11+00:00" title="2011-04-28 16:08:11 UTC">on 2011-04-28</time><span class="editable-message-last-edit-date">: </span> <a href="/ubuntu/+source/mdadm/+bug/244808/comments/6"> <strong>Re: [Bug 244808] Re: {upstream} --incremental --scan --run does not start anything</strong> </a> </td> <td> </td> <td> </td> <td class="bug-comment-index"> <a itemprop="url" href="/ubuntu/+source/mdadm/+bug/244808/comments/6"> #6</a> </td> </tr> </tbody> </table> </div> <div class="boardCommentBody"> <div class="editable-message-body"> <div class="comment-text editable-message-text" itemprop="commentText"><p>Excerpts from ceg's message of Thu Apr 28 10:01:29 UTC 2011:<br /> <span class="foldable-quoted"> > I'm sorry I won't be able to test 11.04 soon.<br /> ><br /> > > - A clear way we can attempt to confirm this behavior (i.e. break an<br /> > array and then attempt to activate it?)<br /> ><br /> > Most of the issues should be covered by the overview in ReliableRaid and the test cases.<br /> > <a rel="nofollow" href="https://wiki.ubuntu.com/ReliableRaid">https:/<wbr />/wiki.ubuntu.<wbr />com/ReliableRai<wbr />d</a> and<br /> > <a rel="nofollow" href="http://testcases.qa.ubuntu.com/Install/AlternateRaidMirror">http://<wbr />testcases.<wbr />qa.ubuntu.<wbr />com/Install/<wbr />AlternateRaidMi<wbr />rror</a> with all three partitoning schemes.<br /> ><br /> > ReliableRaid says this about the bug at hand:<br /> > Using the legacy method to start degraded raids selectively (mdadm --assemble --run -uuid) will break later --incremental (re)additions by udev/hotplugging. (The initramfs currently uses "mdadm --assemble --scan --run" and starts *all* arrays available degraded! 497186. The corresponding command "mdadm --incremental --scan --run" to start *all remaining* hotplugable raids degraded (something still to execute only manually if at all!) does not start anything. 244808)<br /> ><br /> > > - What you expect the system to do (assemble all inactive arrays?)<br /> > By default, it should assemble all raid partitions that are connected with --incremental and run them only when they are complete (as defined by the state of their superblocks) to ensure no arrays are never started partially.<br /> ><br /> > > - What it actually does (??)<br /> > On boot, ubuntu starts ALL arrays in degraded mode, if the rootfs is still incomplete after a timeout. It should only start the raids necessary for the rootfs in degraded mode. (how this could be done: see ReliableRaid Wiki) </span></p> <p>Alright, I haven't seen this behavior with BOOT_DEGRADED=<wbr />false. Quite<br /> the opposite, the system stops and asks you what to do, then gives you<br /> a chance to re-assemble the arrays. But maybe I'm missing something in<br /> your description.</p> <p>I've proposed a blueprint to suggest these fixes at UDS-O in Budapest.</p> <p><a rel="nofollow" href="https://blueprints.launchpad.net/ubuntu/+spec/server-o-software-raid">https:/<wbr />/blueprints.<wbr />launchpad.<wbr />net/ubuntu/<wbr />+spec/server-<wbr />o-software-<wbr />raid</a></p> <p>It would be helpful if you could register for uds-o as a virtual attendee<br /> (or even better, a physical attendee!), subscribe as participation<br /> essential (I went ahead and subscribed you but making you participation<br /> essential just helps the scheduler if you are in fact registered),<br /> and join us via IRC/Streaming for the discussion if the blueprint is<br /> approved for a session at the summit.</p> <p>I've linked this bug report to the blueprint. If you could link all of<br /> the others that you feel should be grouped around this, that would be<br /> quite helpful.</p></div> </div> <div class="editable-message-form" style="display: none"> <textarea style="width: 100%" rows="10">Excerpts from ceg's message of Thu Apr 28 10:01:29 UTC 2011: > I'm sorry I won't be able to test 11.04 soon. > > > - A clear way we can attempt to confirm this behavior (i.e. break an > array and then attempt to activate it?) > > Most of the issues should be covered by the overview in ReliableRaid and the test cases. > https://wiki.ubuntu.com/ReliableRaid and > http://testcases.qa.ubuntu.com/Install/AlternateRaidMirror with all three partitoning schemes. > > ReliableRaid says this about the bug at hand: > Using the legacy method to start degraded raids selectively (mdadm --assemble --run -uuid) will break later --incremental (re)additions by udev/hotplugging. (The initramfs currently uses "mdadm --assemble --scan --run" and starts *all* arrays available degraded! 497186. The corresponding command "mdadm --incremental --scan --run" to start *all remaining* hotplugable raids degraded (something still to execute only manually if at all!) does not start anything. 244808) > > > - What you expect the system to do (assemble all inactive arrays?) > By default, it should assemble all raid partitions that are connected with --incremental and run them only when they are complete (as defined by the state of their superblocks) to ensure no arrays are never started partially. > > > - What it actually does (??) > On boot, ubuntu starts ALL arrays in degraded mode, if the rootfs is still incomplete after a timeout. It should only start the raids necessary for the rootfs in degraded mode. (how this could be done: see ReliableRaid Wiki) Alright, I haven't seen this behavior with BOOT_DEGRADED=false. Quite the opposite, the system stops and asks you what to do, then gives you a chance to re-assemble the arrays. But maybe I'm missing something in your description. I've proposed a blueprint to suggest these fixes at UDS-O in Budapest. https://blueprints.launchpad.net/ubuntu/+spec/server-o-software-raid It would be helpful if you could register for uds-o as a virtual attendee (or even better, a physical attendee!), subscribe as participation essential (I went ahead and subscribed you but making you participation essential just helps the scheduler if you are in fact registered), and join us via IRC/Streaming for the discussion if the blueprint is approved for a session at the summit. I've linked this bug report to the blueprint. If you could link all of the others that you feel should be grouped around this, that would be quite helpful. </textarea> <input type="button" value="Update" class="editable-message-update-btn" /> <input type="button" value="Cancel" class="editable-message-cancel-btn" /> </div> </div> </div> <div xmlns="http://www.w3.org/1999/xhtml" itemscope="" itemtype="http://schema.org/UserComments" class="boardComment editable-message " data-baseurl="/ubuntu/+source/mdadm/+bug/244808/comments/7" data-i-can-edit="False"> <div class="boardCommentDetails"> <div class="message-revision-container"> <div class="message-revision-container-header"> <span>Revision history for this message</span> <img src="/+icing/build/overlay/assets/skins/sam/images/close.gif" class="message-revision-close" /> </div> <script type="text/template"> <div class='message-revision-item'> <div class='message-revision-title'> <a class="sprite remove action-icon message-revision-del-btn"> Remove </a> <a class="js-action"> Revision #{revision}, created at {date_created_display} </a> </div> <div class='message-revision-body'>{content}</div> </div> </script> <div class="message-revision-list"></div> </div> <table> <tbody> <tr> <td> <a href="https://launchpad.net/~ceg" class="sprite person">ceg (ceg)</a> wrote <time itemprop="commentTime" datetime="2011-04-28T16:48:40.831080+00:00" title="2011-04-28 16:48:40 UTC">on 2011-04-28</time><span class="editable-message-last-edit-date">: </span> </td> <td> </td> <td> </td> <td class="bug-comment-index"> <a itemprop="url" href="/ubuntu/+source/mdadm/+bug/244808/comments/7"> #7</a> </td> </tr> </tbody> </table> </div> <div class="boardCommentBody"> <div class="editable-message-body"> <div class="comment-text editable-message-text" itemprop="commentText"><p><span class="foldable-quoted">> I haven't seen this behavior with BOOT_DEGRADED=<wbr />false. </span></p> <p>Right, however software raid has been created to allow your box running and rebooting fine even with partial hardware failures. That BOOT_DEGRADED=false option allows admins to safeguard against the bugs and do things manually, but shouldn't have to be there.</p> <p>On the good side, mdadm now officially supports and ships udev --incremental scripts.<br /> I'd suggest to support the debian maintainer in the swich to the --incremental method.</p></div> </div> <div class="editable-message-form" style="display: none"> <textarea style="width: 100%" rows="10">> I haven't seen this behavior with BOOT_DEGRADED=false. Right, however software raid has been created to allow your box running and rebooting fine even with partial hardware failures. That BOOT_DEGRADED=false option allows admins to safeguard against the bugs and do things manually, but shouldn't have to be there. On the good side, mdadm now officially supports and ships udev --incremental scripts. I'd suggest to support the debian maintainer in the swich to the --incremental method.</textarea> <input type="button" value="Update" class="editable-message-update-btn" /> <input type="button" value="Cancel" class="editable-message-cancel-btn" /> </div> </div> </div> <div xmlns="http://www.w3.org/1999/xhtml" itemscope="" itemtype="http://schema.org/UserComments" class="boardComment editable-message " data-baseurl="/ubuntu/+source/mdadm/+bug/244808/comments/8" data-i-can-edit="False"> <div class="boardCommentDetails"> <div class="message-revision-container"> <div class="message-revision-container-header"> <span>Revision history for this message</span> <img src="/+icing/build/overlay/assets/skins/sam/images/close.gif" class="message-revision-close" /> </div> <script type="text/template"> <div class='message-revision-item'> <div class='message-revision-title'> <a class="sprite remove action-icon message-revision-del-btn"> Remove </a> <a class="js-action"> Revision #{revision}, created at {date_created_display} </a> </div> <div class='message-revision-body'>{content}</div> </div> </script> <div class="message-revision-list"></div> </div> <table> <tbody> <tr> <td> <a href="https://launchpad.net/~khamenya" class="sprite person">vak (khamenya)</a> wrote <time itemprop="commentTime" datetime="2014-06-29T19:08:35.344080+00:00" title="2014-06-29 19:08:35 UTC">on 2014-06-29</time><span class="editable-message-last-edit-date">: </span> </td> <td> </td> <td> </td> <td class="bug-comment-index"> <a itemprop="url" href="/ubuntu/+source/mdadm/+bug/244808/comments/8"> #8</a> </td> </tr> </tbody> </table> </div> <div class="boardCommentBody"> <div class="editable-message-body"> <div class="comment-text editable-message-text" itemprop="commentText"><p>not sure if this bug is directly related: <a rel="nofollow" href="https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1335642">https:/<wbr />/bugs.launchpad<wbr />.net/ubuntu/<wbr />+source/<wbr />mdadm/+<wbr />bug/1335642</a></p></div> </div> <div class="editable-message-form" style="display: none"> <textarea style="width: 100%" rows="10">not sure if this bug is directly related: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1335642</textarea> <input type="button" value="Update" class="editable-message-update-btn" /> <input type="button" value="Cancel" class="editable-message-cancel-btn" /> </div> </div> </div> <div style="float: right;"> <a class="menu-link-activitylog" href="https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/244808/+activity">See full activity log</a> </div> <div class="clearfix"></div> <div align="center" id="add-comment-login-first"> To post a comment you must <a href="+login?comments=all">log in</a>. </div> </div><!-- class="top-portlet" --> </div><!--- id="maincontentsub"--> <div> <div id="duplicate-form-container"></div> <div id="privacy-form-container"></div> </div> </div> </div><!-- yui-b --> </div><!-- yui-main --> <div id="side-portlets" class="yui-b side"> <div id="involvement" class="portlet"> <ul class="involvement"> <li class="single"> <a class="sprite bugs" href="/ubuntu/+source/mdadm/+filebug"> Report a bug </a> </li> </ul> </div> <div id="privacy" class="first portlet public"> <div id="privacy-text"> <span id="information-type-summary" class="sprite public">This report contains <strong id="information-type">Public</strong> information </span> <div id="information-type-description" style="padding-top: 5px">Everyone can see this information. </div> </div> </div> <div id="portlet-actions" class="portlet vertical"> <ul id="duplicate-actions"> </ul> <ul id="lock-status-actions"> </ul> </div> <div class="portlet vertical" id="portlet-subscription"> <div class="section"> <div id="current_user_subscription" class="False"> <span>You are</span> <a class="menu-link-subscription sprite modify edit" href="/ubuntu/+source/mdadm/+bug/244808/+subscribe"> not directly subscribed to this bug's notifications. </a> </div> <div id="sub-unsub-spinner">Subscribing...</div> <ul> <li><a class="menu-link-editsubscriptions sprite modify edit" href="https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/244808/+subscriptions" title="View and change your subscriptions to this bug">Edit bug mail</a></li> </ul> </div> <script type="text/javascript"> LPJS.use('io-base', 'node', 'lp.bugs.bugtask_index.portlets.subscription', function(Y) { Y.on('domready', function() { Y.lp.bugs.bugtask_index.portlets.subscription.initialize(); }); }); </script> </div> <div class="portlet vertical" id="portlet-subscribers"> <h2>Other bug subscribers</h2> <div> <div><a class="menu-link-addsubscriber sprite add" href="https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/244808/+addsubscriber" title="Launchpad will email that person whenever this bugs changes">Subscribe someone else</a></div> </div> <div id="other-bug-subscribers"></div> </div> <div class="portlet vertical" id="portlet-blueprints"> <h2>Related blueprints</h2> <ul> <li><a href="https://blueprints.launchpad.net/ubuntu/+spec/foundations-r-software-raid" class="sprite blueprint-high">Improving Reliability of Software RAID</a></li> </ul> </div> <div class="portlet" id="portlet-watches"> <h2>Remote bug watches</h2> <ul> </ul> <p>Bug watches keep track of this bug in other bug trackers.</p> </div> </div><!-- yui-b side --> </div><!-- yui-t4 --> <div id="footer" class="footer"> <div class="lp-arcana"> <div class="lp-branding"> <a href="https://launchpad.net/"><img src="/@@/launchpad-footer-logo.svg" alt="Launchpad" width="65" height="18" /></a> • <a href="https://launchpad.net/+tour">Take the tour</a> • <a href="https://help.launchpad.net/">Read the guide</a> <form id="globalsearch" method="get" accept-charset="UTF-8" action="https://launchpad.net/+search"> <input type="search" id="search-text" name="field.text" /> <input type="image" src="/@@/search" style="vertical-align:5%" alt="Search Launchpad" /> </form> </div> </div> <div class="colophon"> © 2004 <a href="http://canonical.com/">Canonical Ltd.</a> • <a href="https://launchpad.net/legal">Terms of use</a> • <a href="https://www.ubuntu.com/legal/dataprivacy">Data privacy</a> • <a href="/feedback">Contact Launchpad Support</a> • <a href="http://blog.launchpad.net/">Blog</a> • <a href="https://canonical.com/careers">Careers</a> • <a href="https://ubuntu.social/@launchpadstatus">System status</a> <span id="lp-version"> • aa29ae0 (<a href="https://dev.launchpad.net/">Get the code!</a>) </span> </div> </div> </div><!-- yui-d0--> <script id="json-cache-script">LP.cache = {"related_features": {}, "bug": {"self_link": "https://bugs.launchpad.net/api/devel/bugs/244808", "web_link": "https://bugs.launchpad.net/bugs/244808", "resource_type_link": "https://bugs.launchpad.net/api/devel/#bug", "id": 244808, "private": false, "information_type": "Public", "name": null, "title": "{upstream} --incremental --scan --run does not start anything", "description": "Binary package hint: mdadm\n\n\n(ubuntu 8.04)\n\nThe man page suggests that \"mdadm -IRs\" will start the arrays that have been assembled incrementally, but which are still missing some redundant members (degraded mode).\n\nBut this does not seem to have any effect on inactive arrays here.\n(\"mdadm --incremental --scan --run\" does not start the (multiple) arrays that have been partially assembled by prior \"mdadm --incremental \u003cdevices\u003e\" commands.)\n\n\n", "owner_link": "https://bugs.launchpad.net/api/devel/~ceg", "bug_tasks_collection_link": "https://bugs.launchpad.net/api/devel/bugs/244808/bug_tasks", "duplicate_of_link": null, "date_created": "2008-07-02T09:19:27.469649+00:00", "activity_collection_link": "https://bugs.launchpad.net/api/devel/bugs/244808/activity", "subscriptions_collection_link": "https://bugs.launchpad.net/api/devel/bugs/244808/subscriptions", "date_last_updated": "2014-06-29T19:08:35.904699+00:00", "who_made_private_link": null, "date_made_private": null, "heat": 4, "bug_watches_collection_link": "https://bugs.launchpad.net/api/devel/bugs/244808/bug_watches", "cves_collection_link": "https://bugs.launchpad.net/api/devel/bugs/244808/cves", "vulnerabilities_collection_link": "https://bugs.launchpad.net/api/devel/bugs/244808/vulnerabilities", "duplicates_collection_link": "https://bugs.launchpad.net/api/devel/bugs/244808/duplicates", "attachments_collection_link": "https://bugs.launchpad.net/api/devel/bugs/244808/attachments", "security_related": false, "latest_patch_uploaded": null, "tags": [], "date_last_message": "2014-06-29T19:08:35.344080+00:00", "number_of_duplicates": 0, "message_count": 9, "users_affected_count": 0, "users_unaffected_count": 0, "users_affected_collection_link": "https://bugs.launchpad.net/api/devel/bugs/244808/users_affected", "users_unaffected_collection_link": "https://bugs.launchpad.net/api/devel/bugs/244808/users_unaffected", "users_affected_count_with_dupes": 0, "other_users_affected_count_with_dupes": 0, "users_affected_with_dupes_collection_link": "https://bugs.launchpad.net/api/devel/bugs/244808/users_affected_with_dupes", "messages_collection_link": "https://bugs.launchpad.net/api/devel/bugs/244808/messages", "lock_status": "Unlocked", "lock_reason": null, "linked_branches_collection_link": "https://bugs.launchpad.net/api/devel/bugs/244808/linked_branches", "linked_merge_proposals_collection_link": "https://bugs.launchpad.net/api/devel/bugs/244808/linked_merge_proposals", "http_etag": "\"68a318613fae7a7277b1b1c40f73a16ca59c2993-ee4f0cc0ccf349e96e4c20c9e830410039dffbbd\""}, "subscribers_portlet_url_data": {"web_link": "https://bugs.launchpad.net/bugs/244808", "self_link": "https://bugs.launchpad.net/api/devel/bugs/244808"}, "total_comments_and_activity": 17, "initial_comment_batch_offset": 41, "first visible_recent_comment": -32, "bugtask_data": {"645318": {"id": 645318, "row_id": "tasksummary645318", "form_row_id": "task645318", "bugtask_path": "/mdadm/+bug/244808", "prefix": "mdadm", "targetname": "mdadm", "bug_title": "{upstream} --incremental --scan --run does not start anything", "assignee_value": null, "assignee_is_team": null, "assignee_vocabulary": "AllUserTeamsParticipation", "assignee_vocabulary_filters": [], "hide_assignee_team_selection": true, "user_can_unassign": false, "user_can_delete": false, "delete_link": "https://bugs.launchpad.net/mdadm/+bug/244808/+delete", "target_is_product": true, "status_widget_items": [{"name": "New", "value": "New", "description": "Not looked at yet.\n", "description_css_class": "choice-description", "style": "", "help": "", "disabled": false, "css_class": "statusNEW"}], "status_value": "New", "importance_widget_items": "[]", "importance_value": "Undecided", "milestone_widget_items": "[]", "milestone_value": null, "user_can_edit_assignee": false, "user_can_edit_milestone": false, "user_can_edit_status": false, "user_can_edit_importance": false}, "280973": {"id": 280973, "row_id": "tasksummary280973", "form_row_id": "task280973", "bugtask_path": "/ubuntu/+source/mdadm/+bug/244808", "prefix": "ubuntu_mdadm", "targetname": "mdadm (Ubuntu)", "bug_title": "{upstream} --incremental --scan --run does not start anything", "assignee_value": null, "assignee_is_team": null, "assignee_vocabulary": "AllUserTeamsParticipation", "assignee_vocabulary_filters": [], "hide_assignee_team_selection": true, "user_can_unassign": false, "user_can_delete": false, "delete_link": "https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/244808/+delete", "target_is_product": false, "status_widget_items": [{"name": "Confirmed", "value": "Confirmed", "description": "Verified by someone other than the reporter.\n", "description_css_class": "choice-description", "style": "", "help": "", "disabled": false, "css_class": "statusCONFIRMED"}], "status_value": "Confirmed", "importance_widget_items": "[]", "importance_value": "Undecided", "milestone_widget_items": "[]", "milestone_value": null, "user_can_edit_assignee": false, "user_can_edit_milestone": false, "user_can_edit_status": false, "user_can_edit_importance": false}}, "information_type_data": {"PUBLIC": {"value": "PUBLIC", "description": "Everyone can see this information.\n", "name": "Public", "order": 0, "is_private": false, "description_css_class": "choice-description"}, "PUBLICSECURITY": {"value": "PUBLICSECURITY", "description": "Everyone can see this security related information.\n", "name": "Public Security", "order": 1, "is_private": false, "description_css_class": "choice-description"}, "PRIVATESECURITY": {"value": "PRIVATESECURITY", "description": "Only the security group can see this information.\n ", "name": "Private Security", "order": 2, "is_private": true, "description_css_class": "choice-description"}, "USERDATA": {"value": "USERDATA", "description": "Only shared with users permitted to see private user information.\n", "name": "Private", "order": 3, "is_private": true, "description_css_class": "choice-description"}}, "bug_is_private": false, "context": {"self_link": "https://bugs.launchpad.net/api/devel/ubuntu/+source/mdadm/+bug/244808", "web_link": "https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/244808", "resource_type_link": "https://bugs.launchpad.net/api/devel/#bug_task", "bug_link": "https://bugs.launchpad.net/api/devel/bugs/244808", "milestone_link": null, "status": "Confirmed", "status_explanation": null, "importance": "Undecided", "importance_explanation": null, "assignee_link": null, "bug_target_display_name": "mdadm (Ubuntu)", "bug_target_name": "mdadm (Ubuntu)", "bug_watch_link": null, "date_assigned": null, "date_created": "2008-07-02T09:19:27.469649+00:00", "date_confirmed": "2011-04-28T10:03:46.100132+00:00", "date_incomplete": null, "date_in_progress": null, "date_closed": null, "date_left_new": "2010-04-01T08:15:42.035767+00:00", "date_triaged": null, "date_fix_committed": null, "date_fix_released": null, "date_left_closed": "2010-04-01T15:17:25.242603+00:00", "owner_link": "https://bugs.launchpad.net/api/devel/~ceg", "target_link": "https://bugs.launchpad.net/api/devel/ubuntu/+source/mdadm", "title": "Bug #244808 in mdadm (Ubuntu): \"{upstream} --incremental --scan --run does not start anything\"", "related_tasks_collection_link": "https://bugs.launchpad.net/api/devel/ubuntu/+source/mdadm/+bug/244808/related_tasks", "is_complete": false, "http_etag": "\"3b223b895981a97b3c7cb916e36c2b42ec60d571-01be1182e6135c7ba600755a0811b69d2667635d\""}};</script> </body> <!-- Facet name: bugs Page type: main_side Has global search: True Has application tabs: True Has side portlets: True At least 61 queries/external actions issued in 1.05 seconds Features: {'profiling.enabled': None, 'hard_timeout': '9000', 'app.mainsite_only.canonical_url': None, 'js.yui_version': None, 'app.maintenance_message': None, 'bugs.affected_count_includes_dupes.disabled': None, 'baselayout.careers_link.disabled': None, 'visible_render_time': None} raa29ae0 --> </html>