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


Recommended Posts

Hi All,

 

My setup basically becomes unresponsive after 16-20 hours and my logs is being flooded by these two entries, posting each second:

Jun 23 09:12:50 BrownsBeast emhttpd: error: get_filesystem_status, 6475: Operation not supported (95): getxattr: /mnt/user/media
Jun 23 09:12:50 BrownsBeast emhttpd: error: get_filesystem_status, 6475: Operation not supported (95): getxattr: /mnt/user/photos

 

I am mounting these two shares (on my synology) via User Script with this:

#!/bin/bash
sleep 180
mount -t nfs -o proto=tcp,port=2049 192.168.2.230:/volume1/video /mnt/user/media
mount -t nfs -o proto=tcp,port=2049 192.168.2.230:/volume1/photos /mnt/user/photos

 

NB: I did not use Unassigned Devices as my network is not loaded before it runs UD. In dialogue with the forum we agreed on this was the best approach, though now I get spammed by these and from my research what is causing my system to crash.

 

Hope you can assist me.

 

Best,

 

Casper

 

 

System:

Unraid: 6.5.3 Stable 

Ryzen 1800x

X370-i

32 GB memory

500 gb Samsung 960 PRO NvME

500 gb Samsung 940 EVO Sata

 

 

 

 

brownsbeast-syslog-20180624-0857.zip

Edited by mrbrowndk
Resolved
Link to comment

Probably because unRaid expects a root folder in /mnt/user to be under its control and properly support extended attributes.

 

Why not mount the volumes under /mnt/disks instead where unRaid won't touch them, and then export them over smb manually if you need to

  • Like 1
Link to comment
  • 2 years later...

my system log is full of these errors:

 

Feb 23 00:51:20 Tower emhttpd: error: share_luks_status, 5984: Operation not supported (95): getxattr: /mnt/user/TV_RECORDS

 

the TV_RECORDS share is cache only (but data istn realy on cache than only on the UD HDD)

 

/mnt/user/TV_RECORDS is mountet from an UD HDD to access it via FTP. I get these errors since 1 day (i updated to latest unraid RC2)

Edited by Gee1
Link to comment
14 hours ago, Gee1 said:

/mnt/user/TV_RECORDS is mountet from an UD HDD to access it via FTP. I get these errors since 1 day (i updated to latest unraid RC2)

 

On 6/24/2018 at 7:53 AM, Squid said:

Probably because unRaid expects a root folder in /mnt/user to be under its control and properly support extended attributes.

 

 

Link to comment
  • 8 months later...

I am getting the following error in my logs. emhttpd: error: share_luks_status, 6017: Operation not supported (95): getxattr: /mnt/user/DATA I see what @Squid posted: 

On 6/24/2018 at 7:53 AM, Squid said:

Probably because unRaid expects a root folder in /mnt/user to be under its control and properly support extended attributes.

 

Why not mount the volumes under /mnt/disks instead where unRaid won't touch them, and then export them over smb manually if you need to

 

I have my zfs pool mounted at /WD_RED/DATA and created a ln -s to my directories under /mnt/users/DATA this way I can share "data" in my zfs pool with the SMB share utility in unraid. How do I fix this or go about sharing my zfs pool "data" with my network?

 

Back to what @Squid said, am I able to just manually export smb from /WD_RED/ ? If so, how do I do that? Reason I used ln -s is because I followed the @SpaceInvaderOne video and he did that. I just re-watched the video and realized when he did the ln -s he put the files under /mnt/users/zpool/data. Is it because I missed the zpool? 

 

 

 

Thank you for your help!

Link to comment
  • 3 weeks later...

I followed the above video as well with the intent of using a ZFS pool for an NFS share with Proxmox.  The error is constant on my box also (getxattr).  I attempted to manually add the root location to the exports file so that unraid wasn't looking at it but nothing I do keeps the data in that file.  Any recommendations ?

PS: I am new to unraid.  I have been using a Qnap for years with NFS and no issues.  I was hoping to migrate my proxmox vm's to run off unraid like i do with qnap but the VM's eventually become unresponsive.  I am guessing it is due to the constant errors in unraid.   Loving unraid except not being able to run my VM's straight from the NAS is a killer. 

Link to comment
  • 1 year later...
On 2/23/2021 at 11:01 AM, Gee1 said:

i already use ProFTPd..

 

i found a way to fix this. i mount now to /mnt/user/TV_RECORDS/TV_RECORDS instead of /mnt/user/TV_RECORDS

I tried this but am getting the following error:

 

2023/03/29 20:05:43 Fatal error: failed to mount FUSE fs: mountpoint does not exist: /mnt/user/boxaudiobooks/boxaudiobooks
Script Finished Mar 29, 2023 20:05.43

 

This is what my script looks like:

 

#!/bin/bash
rclone mount --allow-other box:Audiobooks /mnt/user/boxaudiobooks

 

It works fine other than the errors that I want to get rid of.

 

One per second in the main log:

 

Mar 29 20:11:01 Tower  emhttpd: error: share_luks_status, 6173: Operation not supported (95): getxattr: /mnt/user/boxaudiobooks
Mar 29 20:11:02 Tower  emhttpd: error: share_luks_status, 6173: Operation not supported (95): getxattr: /mnt/user/boxaudiobooks
Mar 29 20:11:03 Tower  emhttpd: error: share_luks_status, 6173: Operation not supported (95): getxattr: /mnt/user/boxaudiobooks
Mar 29 20:11:04 Tower  emhttpd: error: share_luks_status, 6173: Operation not supported (95): getxattr: /mnt/user/boxaudiobooks


 

Edited by ryry
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.