[systemd-devel] systemd-remount-api-vfs fails for me

[Andreas Jaeger]

On Thursday 11 November 2010 11:01:21 Kay Sievers wrote:
> On Thu, Nov 11, 2010 at 10:34, Andreas Jaeger <aj at novell.com> wrote:
> > I noticed for some time that systemd-remount-api-vfs is in the failed
> > state and found now the following in the log files
> > 
> > <4>[    3.063357] systemd[1]: systemd 11 running in system mode. (+PAM
> > +LIBWRAP +AUDIT +SELINUX +SYSVINIT; suse) <4>[    3.142518] systemd[1]:
> > Set hostname to <byrd.suse.de>.
> > <4>[    4.598928] systemd-remount-api-vfs[467]: /bin/mount for
> > /proc/bus/usb exited with exit status 32. <4>[    4.603561]
> > systemd-remount-api-vfs[467]: mount: /proc/bus/usb not mounted already,
> > or bad option <4>[    4.620621] systemd[1]:
> > systemd-remount-api-vfs.service: main process exited, code=exited,
> > status=1 <4>[    4.634045] systemd[1]: Unit
> > systemd-remount-api-vfs.service entered failed state.
> > 
> > My fstab contains:
> > usbfs                /proc/bus/usb        usbfs      noauto              
> >  0 0
> > 
> > What's wrong?
> 
> It's a bug in the systemd filter list. systemd has a list of stuff to
> ignore, along with the API filesystems it uses itself. The
> remount-api-vfs tool uses the entire list, so this goes wrong with
> /proc/bus/usb. I'll look into it.
> 
> Unrelated to that, usbfs is deprecated since long, we even disabled it
> in the SUSE kernel, in think. You still need that for something?

I don't need it - and it's noauto, so it should not get mounted at all ;)

Andreas
-- 
 Andreas Jaeger, Program Manager openSUSE,  aj@{novell.com,opensuse.org}
  Twitter: jaegerandi | Identica: jaegerandi
   SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
    Maxfeldstr. 5, 90409 Nürnberg, Germany
     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126