Bug #1973

Incorrect major number for root device

Added by rumcic over 3 years ago. Updated almost 3 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

On latest master major numbers for devices are properly setup, but only after
the kernel booted and the root device keeps it's major number at "0". Due to
this "/" is mounter read-only (as should be) but cannot be remounted
read-write when starting up due to major number mismatch:
cannot update mount, udev does not match 00000000:00020040 vs 00000016:00020040
--
Please do not CC me, since I already receive everything from these MLs.

Regards,
Rumko

History

#1 Updated by swildner over 3 years ago

On 1/29/2011 0:21, Rumko wrote:
> On latest master major numbers for devices are properly setup, but only after
> the kernel booted and the root device keeps it's major number at "0". Due to
> this "/" is mounter read-only (as should be) but cannot be remounted
> read-write when starting up due to major number mismatch:
> cannot update mount, udev does not match 00000000:00020040 vs 00000016:00020040

Is root UFS or hammer? I saw the r/o mount on my UFS VM too but didn't
make the connection, while my HAMMER file server doesn't seem to have
this issue.

S.

#2 Updated by rumcic over 3 years ago

Root is UFS on this machines (almost all mount points are UFS).
I wonder why hammer would work, hm.

#3 Updated by rumcic almost 3 years ago

  • Description updated (diff)
  • Status changed from New to Closed

Fixed long ago

Also available in: Atom PDF