search

gmzang / maczfs

Automatically exported from code.google.com/p/maczfs
Other
0 stars 0 forks source link

Lots of "add_fsevent: unable to get path for vp" error messages… #35

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
add_fsevent: unable to get path for vp 0xffffff800f4e0000 (-UNKNOWN-FILE; ret 
2; type 9)
add_fsevent: unabled to get a path for vp 0xffffff800f4e0000.  dropping the 
event.

No idea what's causing it just yet, but I'm guessing it's something in how my 
fork has filesystems 
show up as separate drives… hoping to find a solution in the 10a286 code.

Original issue reported on code.google.com by jason.richard.mcneil on 4 Mar 2010 at 6:45

GoogleCodeExporter commented 8 years ago 
Have you been able to replicate this yet? Is it to do with whether a zpool, or 
zfs under a zpool, is enabled for spotlight?

Original comment by alex.ble...@gmail.com on 19 Jul 2010 at 11:22

GoogleCodeExporter commented 8 years ago 
These messages still show up in MacZFS-74-0-1 in /var/system/kernel.log.

Original comment by alex.ble...@gmail.com on 12 Dec 2010 at 3:07

GoogleCodeExporter commented 8 years ago 
Looks like changes in the filesystem are working as expected; fseventd is 
picking up the list.

# Event
  type           = FSE_CREATE_FILE
  pid            = 669 (exited?)
  # Details
    # type           len  data
    vp     = 6c6f562f
    FSE_ARG_STRING    18  string = /Volumes/Foobar/a
    FSE_ARG_DEV        4  dev    = 0x2d00000c (major 45, minor 12)
    FSE_ARG_INO        4  ino    = 18
    FSE_ARG_MODE       4  mode   = -rw-r--r--  (0x0081a4, vnode type VREG)
    FSE_ARG_UID        4  uid    = 1000 (alex)
    FSE_ARG_GID        4  gid    = 0 (wheel)
    FSE_ARG_INT64      8  tstamp = 13230773581078
    FSE_ARG_DONE (0xb33f)
# Event
  type           = FSE_CREATE_FILE
  pid            = 669 (exited?)
  # Details
    # type           len  data
    vp     = 6c6f562f
    FSE_ARG_STRING    23  string = /Volumes/Foobar/Ping/b
    FSE_ARG_DEV        4  dev    = 0x2d00001a (major 45, minor 26)
    FSE_ARG_INO        4  ino    = 5
    FSE_ARG_MODE       4  mode   = -rw-r--r--  (0x0081a4, vnode type VREG)
    FSE_ARG_UID        4  uid    = 1000 (alex)
    FSE_ARG_GID        4  gid    = 1000 (alex)
    FSE_ARG_INT64      8  tstamp = 13230773793926
    FSE_ARG_DONE (0xb33f)
=> received 94 bytes

As might be expected, Foobar (the pool) has a major device id, and the ZFS pool 
has a minor device id. A sub pool has a different minor device id.

Not sure why it's reporting that the VP for both is the same. It might be 
recycling the vnode between requests.

Original comment by alex.ble...@gmail.com on 9 Jan 2011 at 9:17

GoogleCodeExporter commented 8 years ago 
I'm getting the same messages, under Lion

Original comment by asl...@gmail.com on 18 Jul 2011 at 6:41

GoogleCodeExporter commented 8 years ago 
Also getting this very frequently.  No ideas as to the cause.

Aug 11 07:23:52 zeus kernel[0]: add_fsevent: unable to get path for vp 
0xffffff8023441c98 (sessions; ret 22; type 2)
Aug 11 07:23:52 zeus kernel[0]: add_fsevent: unabled to get a path for vp 
0xffffff8023441c98.  dropping the event.
Aug 11 07:23:52 zeus kernel[0]: add_fsevent: unable to get path for vp 
0xffffff8023441c98 (sessions; ret 22; type 2)
Aug 11 07:23:52 zeus kernel[0]: add_fsevent: unabled to get a path for vp 
0xffffff8023441c98.  dropping the event.
Aug 11 07:23:52 zeus kernel[0]: add_fsevent: unable to get path for vp 
0xffffff8023441c98 (sessions; ret 22; type 2)
Aug 11 07:23:52 zeus kernel[0]: add_fsevent: unabled to get a path for vp 
0xffffff8023441c98.  dropping the event.
Aug 11 07:23:52 zeus kernel[0]: add_fsevent: unable to get path for vp 
0xffffff8023441c98 (sessions; ret 22; type 2)
Aug 11 07:23:52 zeus kernel[0]: add_fsevent: unabled to get a path for vp 
0xffffff8023441c98.  dropping the event.
Aug 11 07:23:52 zeus kernel[0]: add_fsevent: unable to get path for vp 
0xffffff8023441c98 (sessions; ret 22; type 2)
Aug 11 07:23:52 zeus kernel[0]: add_fsevent: unabled to get a path for vp 
0xffffff8023441c98.  dropping the event.
Aug 11 07:23:52 zeus kernel[0]: add_fsevent: unable to get path for vp 
0xffffff8023441c98 (sessions; ret 22; type 2)
Aug 11 07:23:52 zeus kernel[0]: add_fsevent: unabled to get a path for vp 
0xffffff8023441c98.  dropping the event.

Original comment by matth...@ambientideas.com on 11 Aug 2011 at 2:50

GoogleCodeExporter commented 8 years ago 
Count me among the "me toos" but my filesystem is HFS+. I see this littered 
throughout my log on a stock installation of Lion (fresh install, no upgrade 
from Snow Leopard).

Original comment by cck...@gmail.com on 1 Sep 2011 at 3:08

GoogleCodeExporter commented 8 years ago 
I've submitted this to Apple for some, hopefully, additional eyes to see the 
issue.  It's happening here quite heavily as well and I'd like to know if 
anyone has reached any further understanding of why this is occurring.

Original comment by yllumin...@gmail.com on 8 Sep 2011 at 6:47

GoogleCodeExporter commented 8 years ago 
I too have informed Apple, and would also be interested in hearing if other 
people have additional information on the subject. I can't for the life of my 
pinpoint the cause or even identify a pattern...

Original comment by cck...@gmail.com on 11 Sep 2011 at 3:24

GoogleCodeExporter commented 8 years ago 
I'm getting a similar message over and over:
'
add_fsevent: unable to get path for vp 0xffffff801ebedc98 (-UNKNOWN-FILE; ret 
2; type 9)
add_fsevent: unabled to get a path for vp 0xffffff801ebedc98.  dropping the 
event.
add_fsevent: unable to get path for vp 0xffffff802433c0f8 (-UNKNOWN-FILE; ret 
2; type 9)
add_fsevent: unabled to get a path for vp 0xffffff802433c0f8.  dropping the 
event.
add_fsevent: unable to get path for vp 0xffffff8017456648 (-UNKNOWN-FILE; ret 
2; type 9)
add_fsevent: unabled to get a path for vp 0xffffff8017456648.  dropping the 
event.
add_fsevent: unable to get path for vp 0xffffff802220c170 (-UNKNOWN-FILE; ret 
2; type 9)
add_fsevent: unabled to get a path for vp 0xffffff802220c170.  dropping the 
event.
add_fsevent: unable to get path for vp 0xffffff801e1b1c18 (-UNKNOWN-FILE; ret 
2; type 9)
add_fsevent: unabled to get a path for vp 0xffffff801e1b1c18.  dropping the 
event.
add_fsevent: unable to get path for vp 0xffffff802290b2e8 (-UNKNOWN-FILE; ret 
2; type 9)
add_fsevent: unabled to get a path for vp 0xffffff802290b2e8.  dropping the 
event.

I have no idea if they're related. I have two partitions with HFS+ and ZFS on 
the disk, and I have a second disk with HFS+-only in the optibay. I also use 
Lion.

@yllumin, @cck: did you get any response from Apple after submitting it?

Original comment by lars.tob...@gmail.com on 8 Dec 2011 at 6:47

GoogleCodeExporter commented 8 years ago 
I'm getting these... to the tune of 1000s per hour.
I went to look at the event logs because Time Machine refuses to take a backup 
and I was wondering if I would find anything there. Is this related? Anyone 
else having Time Machine issues?
Time Machine last took a backup on Dec 21.

Original comment by david.be...@gmail.com on 29 Dec 2011 at 12:52

GoogleCodeExporter commented 8 years ago 
I was getting these as well. I went to Server Admin --> Settings Tab --> 
Services Tab, and turned off "Software Update", and I'm no longer receiving 
these messages in my logs.

Original comment by matthew....@gmail.com on 7 Jan 2012 at 1:21