https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082011-01-29T15:46:43ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #1973: Incorrect major number for root devicehttps://bugs.dragonflybsd.org/issues/1973?journal_id=95392011-01-29T15:46:43Zswildner
<ul></ul><p>On 1/29/2011 0:21, Rumko wrote:</p>
<blockquote>
<p>On latest master major numbers for devices are properly setup, but only after<br />the kernel booted and the root device keeps it's major number at "0". Due to<br />this "/" is mounter read-only (as should be) but cannot be remounted<br />read-write when starting up due to major number mismatch:<br />cannot update mount, udev does not match 00000000:00020040 vs 00000016:00020040</p>
</blockquote>
<p>Is root UFS or hammer? I saw the r/o mount on my UFS VM too but didn't <br />make the connection, while my HAMMER file server doesn't seem to have <br />this issue.</p>
<p>S.</p> DragonFlyBSD - Bug #1973: Incorrect major number for root devicehttps://bugs.dragonflybsd.org/issues/1973?journal_id=95412011-01-30T00:20:38Zrumcic
<ul></ul><p>Root is UFS on this machines (almost all mount points are UFS).<br />I wonder why hammer would work, hm.</p> DragonFlyBSD - Bug #1973: Incorrect major number for root devicehttps://bugs.dragonflybsd.org/issues/1973?journal_id=103752011-12-18T19:09:09Zrumcic
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/10375/diff?detail_id=64">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul><p>Fixed long ago</p>