Jump to content
DZMM

6.5.0-rc5 syslog filling up with error - emhttpd: error: get_filesystem_status, 6475: Operation not supported (95): getxattr:

16 posts in this topic Last Reply

Recommended Posts

I've had a var log filling up alert popup and checking my logs I've been getting this error every second since I upgraded to 6.5rc5 - I've been running fuse mounts for a week or so, but I think this error has only started with 6.5rc5 (I didn't run the other 6.5 releases).  I'm using unionfs from nerd tools.

 

Mar  7 07:47:17 Highlander emhttpd: error: get_filesystem_status, 6475: Operation not supported (95): getxattr: /mnt/user/movies_adults_fuse
Mar  7 07:47:17 Highlander emhttpd: error: get_filesystem_status, 6475: Operation not supported (95): getxattr: /mnt/user/movies_kids_fuse
Mar  7 07:47:17 Highlander emhttpd: error: get_filesystem_status, 6475: Operation not supported (95): getxattr: /mnt/user/tv_adults_fuse
Mar  7 07:47:17 Highlander emhttpd: error: get_filesystem_status, 6475: Operation not supported (95): getxattr: /mnt/user/tv_kids_fuse

The fuse folders are a combo of plexdrive folders (_gd) of files on google drive and local folders (_upload) of files waiting to be uploaded:

 

# Unmount before remounting
fusermount -uz /mnt/user/tv_adults_fuse
fusermount -uz /mnt/user/tv_kids_fuse
fusermount -uz /mnt/user/movies_adults_fuse
fusermount -uz /mnt/user/movies_kids_fuse
unionfs -o cow,allow_other,direct_io,auto_cache,sync_read /mnt/user/tv_adults_upload=RW:/mnt/disks/crypt/tv_adults_gd=RO /mnt/user/tv_adults_fuse
unionfs -o cow,allow_other,direct_io,auto_cache,sync_read /mnt/user/tv_kids_upload=RW:/mnt/disks/crypt/tv_kids_gd=RO /mnt/user/tv_kids_fuse
unionfs -o cow,allow_other,direct_io,auto_cache,sync_read /mnt/user/movies_adults_upload=RW:/mnt/disks/crypt/movies_adults_gd=RO /mnt/user/movies_adults_fuse
unionfs -o cow,allow_other,direct_io,auto_cache,sync_read /mnt/user/movies_kids_upload=RW:/mnt/disks/crypt/movies_kids_gd=RO /mnt/user/movies_kids_fuse

 

highlander-diagnostics-20180309-0838.zip

Share this post


Link to post

also got this in my smb settings:

 

[tv_kids_fuse] 
path = /mnt/user/tv_kids_fuse
comment = fuse of local and files uploaded
browseable = yes 
read only = yes
valid users = kodi kodi_adults kodi_kids
vfs objects =

[movies_kids_fuse] 
path = /mnt/user/movies_kids_fuse
comment = fuse of local and files uploaded
browseable = yes 
read only = yes
valid users = kodi kodi_adults kodi_kids
vfs objects =

[tv_adults_fuse] 
path = /mnt/user/tv_adults_fuse
comment = fuse of local and files uploaded
browseable = yes 
read only = yes
valid users = kodi kodi_adults
vfs objects =

[movies_adults_fuse] 
path = /mnt/user/tv_adults_fuse
comment = fuse of local and files uploaded
browseable = yes 
read only = yes
valid users = kodi kodi_adults
vfs objects =

 

Share this post


Link to post

getxattr refers to extended attributes. These are used by unRAID in user shares to keep track on which disk(s) a share and its contents are present.

 

I am not using unionfs, but it seems it doesn't support/like extended attributes. Perhaps @limetech can explain if there is a difference in implementation with 6.5..

 

Unrelated but to let you know: network addresses 172.32.x.x and higher are actual public addresses, perhaps better to change your docker network assignments to 172.22.x.x ...

  • Upvote 1

Share this post


Link to post
8 minutes ago, bonienl said:

getxattr refers to extended attributes. These are used by unRAID in user shares to keep track on which disk(s) a share and its contents are present.

 

I am not using unionfs, but it seems it doesn't support/like extended attributes. Perhaps @limetech can explain if there is a difference in implementation with 6.5..

 

Unrelated but to let you know: network addresses 172.32.x.x and higher are actual public addresses, perhaps better to change your docker network assignments to 172.22.x.x ...

Hmm I got rid of the 172.32.x.x, 172.33.x.x etc addresses when you pointed this out before, but there must be some reminants somewhere - where did you spot that? 

 

I use 172.30.12.x for my LAN and my Vlans are now (should be on!) on 192.168.10.x, 192.168.20.x, 192.168.30.x, 192.168.40.x and 192.168.50.x

Share this post


Link to post

This is your docker configuration file

DOCKER_ENABLED="yes"
DOCKER_IMAGE_FILE="/mnt/cache/ssd/docker/docker.img"
DOCKER_IMAGE_SIZE="20"
DOCKER_APP_CONFIG_PATH="/mnt/cache/appdata"
DOCKER_APP_UNRAID_PATH=""
DOCKER_AUTHORING_MODE="no"
DOCKER_DHCP_BR0="172.30.12.0/25"
DOCKER_LOG_ROTATION="yes"
DOCKER_LOG_SIZE="50m"
DOCKER_LOG_FILES="1"
DOCKER_DHCP_BR0_10="172.31.12.0/25"
DOCKER_DHCP_BR0_20="172.32.12.0/25"
DOCKER_DHCP_BR0_30="172.33.12.0/25"
DOCKER_DHCP_BR0_50="172.35.12.0/25"
DOCKER_DHCP_BR0_40="172.34.12.0/25"
DOCKER_USER_NETWORKS="remove"

You can go to Docker Settings, stop the service and update the entries for your VLANs.

Share this post


Link to post
11 minutes ago, bonienl said:

This is your docker configuration file


DOCKER_ENABLED="yes"
DOCKER_IMAGE_FILE="/mnt/cache/ssd/docker/docker.img"
DOCKER_IMAGE_SIZE="20"
DOCKER_APP_CONFIG_PATH="/mnt/cache/appdata"
DOCKER_APP_UNRAID_PATH=""
DOCKER_AUTHORING_MODE="no"
DOCKER_DHCP_BR0="172.30.12.0/25"
DOCKER_LOG_ROTATION="yes"
DOCKER_LOG_SIZE="50m"
DOCKER_LOG_FILES="1"
DOCKER_DHCP_BR0_10="172.31.12.0/25"
DOCKER_DHCP_BR0_20="172.32.12.0/25"
DOCKER_DHCP_BR0_30="172.33.12.0/25"
DOCKER_DHCP_BR0_50="172.35.12.0/25"
DOCKER_DHCP_BR0_40="172.34.12.0/25"
DOCKER_USER_NETWORKS="remove"

You can go to Docker Settings, stop the service and update the entries for your VLANs.

hmm I had:

 

5aa2862be1105_FireShotCapture66-Highlander_DockerSettings_-https___1d087a25aac48109ee9a15217a.thumb.png.82e232ab903a5136d181579eb2ed1fc3.png

my gateways are also set, but aren't being shown on the docker page ??

5aa2873c10a73_FireShotCapture67-Highlander_NetworkSettings_-https___1d087a25aac48109ee9a15217a.thumb.png.29a45d47a28f4bf446ae64c830e8ded0.png

 

Share this post


Link to post
Posted (edited)
19 minutes ago, DZMM said:

hmm I had:

 

Since you are using the automatic generated entries these always take the network assignment of the interface (or VLAN) itself. You are good.

 

The config file wasn't updated. I've made an update in 6.5 to clean up unused entries, but obviously these will only be cleaned when the Docker settings are re-applied, which you can do.

 

Edited by bonienl

Share this post


Link to post
19 hours ago, bonienl said:

getxattr refers to extended attributes. These are used by unRAID in user shares to keep track on which disk(s) a share and its contents are present.

 

I am not using unionfs, but it seems it doesn't support/like extended attributes. Perhaps @limetech can explain if there is a difference in implementation with 6.5..

 

Unrelated but to let you know: network addresses 172.32.x.x and higher are actual public addresses, perhaps better to change your docker network assignments to 172.22.x.x ...

@limetech was this problem introduced in 6.5?  I've hit 100% after 3 days running time, so hoping there's a solution other than rebooting every 2 days

Share this post


Link to post

The '/mnt/user' mount point is exclusively for use of unRAID 'shfs' file system.  It's bad practice to manually mount anything else in that tree and not supported.

Share this post


Link to post
36 minutes ago, limetech said:

The '/mnt/user' mount point is exclusively for use of unRAID 'shfs' file system.  It's bad practice to manually mount anything else in that tree and not supported.

Thanks.  Where do you recommend I mount?

Share this post


Link to post
1 minute ago, DZMM said:

Thanks.  Where do you recommend I mount?

Perhaps under /mnt/disks (which is where the Unassigned Devices plugin mounts drives) might be an existing location that is appropriate?

  • Upvote 1

Share this post


Link to post
12 minutes ago, itimpi said:

Perhaps under /mnt/disks (which is where the Unassigned Devices plugin mounts drives) might be an existing location that is appropriate?

yeah, just realised I can make a virtual disk just like I've made virtual disks for plexdrive and the google drive mounts - thanks

Share this post


Link to post

Had this SAME error begin occuring on my system for no clear reason. ALL NFS and SMB shares missing. Having just upgraded a disk I thought this might be it - it wasn't. Multiple reboots failed to clear it. Finally I noticed it was one specific share being called out in the error message. I dug into the config folders on my USB flash, renamed the CFG file for that share, and rebooted. When the system came up the shares were all fine and the CFG for the renamed share had even been rebuilt! Not sure what happened but it was really screwing with my system. While the drive was rebuilding I was seeing the  Unassigned Devices plug-in display ALL of my normal disks as available to it and then revert to a normal display - and back again! I booted in Safe mode and while that behaviour stopped the issue remained until the CFG was renamed. Hope this helps out someone down the line!

 

emhttpd: error: get_filesystem_status, 6475: Operation not supported (95): getxattr

 

 

  • Like 2

Share this post


Link to post

Thanks BLKMGK, your approach saved me!

 

I'm new to unraid and suddenly had this issue after starting the array:

emhttpd: error: get_filesystem_status, 6477: Operation not supported (95): getxattr: /mnt/user/appdata

 

I could not see any shares and not even create new ones. When I tried to stop the array, the GUI froze and I saw this repeating in the log files:

emhttpd: shcmd (140): umount /mnt/user
root: umount: /mnt/user: not mounted.
emhttpd: shcmd (140): exit status: 32
emhttpd: shcmd (141): rmdir /mnt/user
root: rmdir: failed to remove '/mnt/user': Directory not empty
emhttpd: shcmd (141): exit status: 1
emhttpd: shcmd (143): /usr/local/sbin/update_cron
emhttpd: Retry unmounting user share(s)...

There was only this directory and nothing else, so I deleted it from ssh: rm -rf /mnt/user and renamed /boot/config/shares/appdata.cfg before starting the array and everything was back!

Share this post


Link to post
1 hour ago, raav said:

I'm new to unraid and suddenly had this issue after starting the array:

Uninstall or update the netstats plugin.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now