[arch-releng] regression with race condition on pxe boot with nbd

Christian Hesse list at eworm.de
Wed May 25 08:35:54 UTC 2016


Gerardo Exequiel Pozzi <vmlinuz386 at gmail.com> on Tue, 2016/05/24 21:27:
> On 05/24/16 09:54, Christian Hesse wrote:
> > Christian Hesse <list at eworm.de> on Tue, 2016/05/24 14:35:  
> >> Hello everybody,
> >>
> >> with my latest builds I see a regression on pxe boot with nbd. About 50%
> >> of boots fail. The nbd module is loaded, nbd-client attaches the device,
> >> but mount fails:
> >>
> >> mount: you must specify the filesystem type
> >> ERROR; Failed to mount '/dev/nbd0'
> >>    Falling back to interactive prompt
> >>    You can try to fix the problem manually, log out when you are finished
> >>
> >> A simple mount allows to continue boot:
> >>
> >> mount /dev/nbd0 /run/archiso/bootmnt/
> >> <Ctrl>-d
> >>
> >> My guess is that linux 4.6 introduced a race condition. Any idea how to
> >> fix or handle this?  
> > 
> > Looks like adding a boot parameter
> > 
> > nbd.nbds_max=2
> > 
> > fixes this (or makes it a lot less likely to happen). However this is
> > still more of a workaround...
> >   
> 
> Hi Christian
> 
> Did you try booting with earlymodules=nbd if goes better?
> 
> Thanks for doing a good job here.

Yes, looks like earlymodules=nbd works as well. What's the best way to get
this into the scripts? Or should we just move modprobe to run_earlyhook()?
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Best regards             my address:    */=0;b=c[a++];)
putchar(b-1/(/*    Chris            cc -ox -xc - && ./x    */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-releng/attachments/20160525/a8914bae/attachment-0001.asc>


More information about the arch-releng mailing list