lvm related ioctl?

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

Taking a working 6 Dec 9.99.19/amd64 box, I see:

# /etc/rc.d/lvm onestart
Configuring lvm devices.
File descriptor 3 () leaked on lvm invocation. Parent PID 687: 
File descriptor 3 () leaked on lvm invocation. Parent PID 687: 
 Activated Volume Groups: vg0

Updating kernel and modules to today's current (9.99.21), I see:

# /etc/rc.d/lvm onestart
Configuring lvm devices.
File descriptor 3 () leaked on lvm invocation. Parent PID 1270: 
  A non-block device file at '/dev/mapper/rvg0-distfiles' is already present
  A non-block device file at '/dev/mapper/rvg0-packages' is already present
  A non-block device file at '/dev/mapper/rvg0-releasedir' is already present
  A non-block device file at '/dev/mapper/rvg0-home' is already present
  A non-block device file at '/dev/mapper/rvg0-obj' is already present
  A non-block device file at '/dev/mapper/rvg0-scratch' is already present
File descriptor 3 () leaked on lvm invocation. Parent PID 1270: 
  ioctl deps call failed with errno 2

  _deps: task run failed for (169:0)
  Failed to add device (169:0) to dtree
  ioctl deps call failed with errno 2

  _deps: task run failed for (169:0)
  Failed to add device (169:0) to dtree
  ioctl deps call failed with errno 2

  _deps: task run failed for (169:0)
  Failed to add device (169:0) to dtree
  ioctl deps call failed with errno 2

  _deps: task run failed for (169:0)
  Failed to add device (169:0) to dtree
  ioctl deps call failed with errno 2

  _deps: task run failed for (169:0)
  Failed to add device (169:0) to dtree
  ioctl deps call failed with errno 2

  _deps: task run failed for (169:0)
  Failed to add device (169:0) to dtree
 Activated Volume Groups: vg0

I don't see which ioctl dep failed in e.g. dmesg

# ls /dev/mapper/*obj*
/dev/mapper/rrvg0-obj     /dev/mapper/rvg0-obj      /dev/mapper/vg0-obj

^rr ?

lvm vgs, and lvm lvs appear to be sane, but

# mount /dev/mapper/vg0-obj /usr/obj
mount_ffs: /dev/mapper/vg0-obj on /usr/obj: Device busy

Why busy - it isn't mounted...

Reverting kernel & modules to 9.99.19 and all OK again.


Cheers,

Patrick