[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#621803: mountkernfs.sh unconditionally mounts /run

On Tue, May 10, 2011 at 11:11:20AM +0200, Michael Biebl wrote:
> Am 09.05.2011 23:40, schrieb rleigh:
> > On Mon, May 09, 2011 at 10:56:39PM +0200, chris h wrote:
> >> with initscripts 2.88dsf-13.5 from exp and initramfs-tools maks/run
> >> there's a new warning during boot:
> >> mount: can't find /run in /etc/fstab or /etc/mtab
> >>
> >> Apparently this is caused by mountkernfs.sh which assumes that it has
> >> the authority to mount /run (line 42).
> >> With the newer initramfs-tools /run gets moved by the initramfs' init,
> >> but this doesn't make it into the mtab, causing the warning.
> >>
> >> I'm unsure what the correct solution would be...
> > 
> > You need the patch from #621803 applying to the maks/run branch?
> > Or was this already applied?
> I can reproduce this issue. I used sysvinit/initscripts 2.88dsf-13.5 and built
> initramfs-tools from the maks/run branch (a6167ad4d32f56db89989e40d1863887c199cc61)
> During boot I get
> mount: can't find /run in /etc/fstab or /etc/mtab
> mount: can't find /sys in /etc/fstab or /etc/mtab
> and as a consequence
> startpar: service(s) returned failure: mountkernfs.sh ... failed!

I think I know what's going on here, but I'll need to test.  If
/run and /sys were mounted before reboot, they exist in the old
/etc/mtab before mtab.sh is run.  If they weren't, the remount
will fail.  mtab is not cleared until S08checkroot.sh, so
mountkernfs still sees the old contents.

The solution here, if this is the problem, is to comment out the
remounting until we have eliminated /etc/mtab by symlinking to
/proc/mounts.  If looks like a remount requires mtab/fstab entry
while mount does not.


  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.

Attachment: signature.asc
Description: Digital signature

Reply to: