Andreas Metzler wrote:
If I add the original line again, it fails in the same way. If I then "mkdir /.dev" it works again. The same behaviour (ie. updatedb fails and truncates db) if I instead add "/foo /bar ext3 rw 0 0".

Grr. I cannot reproduce this here. (running kernel-image-2.6.8-2-k7 2.6.8-13)

Ok, this is weird. Using your sequence of commands, I cannot reproduce either. However, if I place the "/foo /bar" line *in the middle" of mtab then I can.


This is my /etc/mtab. This one fails. Notice the placement of the "/foo /bar" line; above (and including) this position it fails, below it works fine.

  /dev/hda1 / ext3 rw,noatime,errors=remount-ro,commit=20 0 0
  proc /proc proc rw 0 0
  sysfs /sys sysfs rw 0 0
  devpts /dev/pts devpts rw,gid=5,mode=620 0 0
  tmpfs /dev/shm tmpfs rw 0 0
  /dev /dev/.static/dev unknown rw,bind 0 0
  /foo /bar ext3 rw 0 0
  none /dev tmpfs rw,size=10M,mode=0755 0 0
  usbfs /proc/bus/usb usbfs rw 0 0

Now for the command sequence:

  [EMAIL PROTECTED] ~# locate initrd | wc -l
  35
  [EMAIL PROTECTED] ~# /etc/cron.weekly/find  ; echo $?
  0
  [EMAIL PROTECTED] ~# locate initrd | wc -l
  1
  [EMAIL PROTECTED] ~# locate initrd
  /boot/initrd.gz
  [EMAIL PROTECTED] ~# updatedb
  /usr/bin/find: error in /etc/mtab: /bar: No such file or directory
  [EMAIL PROTECTED] ~#

So the db isn't empty but it is not fully populated either.


Cheers, Joachim


-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to