Orphan files?
-
Hey, I got this...
Any ideas about how to fix these files?
[ 12.617020] jffs2: notice: (440) jffs2_build_xattr_subsystem: complete building xattr subsystem, 3 of xdatum (3 unchecked, 0 orphan) and 77 of xref (1 dead, 0 orphan) found.
[ 12.632902] ttyS ttyS0: 14 input overrun(s)
[ 12.637989] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
[ 12.653221] block: extroot: not configured
[ 12.953289] jffs2: notice: (438) jffs2_build_xattr_subsystem: complete building xattr subsystem, 3 of xdatum (3 unchecked, 0 orphan) and 77 of xref (1 dead, 0 orphan) found.
-
I think, this discussion on WDR3600 is about the same observation as yours:
https://patchwork.ozlabs.org/project/lede/patch/5296d02b-6b69-dd4c-ca4e-13150616fd6f@gmail.com/
As you can see in the link, Conor O'Gorman commented that:
..
2) You should not see the jffs2 "complete build" message twice. It's
showing 2 different process ids also. You need to check what you've
added to make this code run twice. The later error would match the idea
of two jffs2 processes.
..At the end, a patch is provided. I guess it is for the build for the above device, WDR3600.
-
@tjoseph1 said in Orphan files?:
- You should not see the jffs2 "complete build" message twice.
Agreed, don't think you should be seeing this twice.
But assuming @Lucas-Gozalvez is using the correct firmware for his device (Omega2+ firmware for Omega2+, or Omega2 fw for Omega2, I'm not sure this type of patch will help.
We already define two different devices for the Omega2 (16MB flash) and Omega2+ (32MB flash) devices.
In general, for
jffs2_build_xattr_subsystemmessages (that only appear once per boot):
We see the same messages on a variety of devices, most of the time with different values for the dead, orphan or unchecked.
And we've observed that after a factory restore or sysupgrade with -n the numbers reset to 0.Given that xattr looks to just be a way to add metadata to files, we're confident that it won't affect the operation of the filesystem or the device itself.
More info on xattr here:
https://en.wikipedia.org/wiki/Extended_file_attributes
https://en.wikipedia.org/wiki/Extended_file_attributes#Linux
-
@Lazar-Demin
For the record, on two LTE boards I have access to I see the same duplicate log messages. At the moment xdatum.orphan and xref.dead count increase every reboot.The boards have python installed, apart from that they are in out-of-the-box state (0.3.2 b232).
Just checked my Omega2 Pro (b218): 2 log entries but orphan/dead counts are stable.
Example:
[ 10.538884] mount_root: loading kmods from internal overlay [ 10.612430] kmodloader: loading kernel modules from //etc/modules-boot.d/* [ 10.626052] kmodloader: done loading kernel modules from //etc/modules-boot.d/* [ 12.054487] jffs2: notice: (445) jffs2_build_xattr_subsystem: complete building xattr subsystem, 18 of xdatum (3 unchecked, 15 orphan) and 65 of xref (22 dead, 1 orphan) found. [ 12.071277] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab [ 12.085997] block: extroot: not configured [ 12.490347] jffs2: notice: (443) jffs2_build_xattr_subsystem: complete building xattr subsystem, 18 of xdatum (3 unchecked, 15 orphan) and 65 of xref (22 dead, 1 orphan) found. [ 12.508068] mount_root: loading kmods from internal overlay [ 12.582514] kmodloader: loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/* [ 12.594977] kmodloader: done loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/* [ 13.347454] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab [ 13.358145] block: extroot: not configured [ 13.363570] mount_root: switching to jffs2 overlay [ 13.437641] overlayfs: upper fs does not support tmpfile.
-
I just noticed I have 1 and 7 on one of Omega2S+ based devices, but they are not increasing and not clearing after reboot. Time to investigate!
-
Updated an LTE board to 0.3.2 b244 just for the sake of it. I still get double entries (see my last post) but so far it doesn't show the increment behaviour but it isn't static either. I keep an eye on it.
