b0m541

same problem here since Parity Check Tuning plugin got updated

@VRx Thank you so much for your effort for providing this. I had a lot of non-computer things going on and hadn't seen this for a long time. Sorry for that. I have now successfully integrated vchanger and I think your effort has paid off. I will monitor the ongoing daily use of vchanger and if it is stable I'll let you know in a while, so that it can be put into the frquently updated container. Thanks again and all the best

I have seen posts mentioning that there are plugins for Python 2 and Python 3 and a replacement for Nerd Pack called Nerd Tools. on my unRAID 6.10.3 with CA 2022.10.16 I cannot find any of these? Why is that? is CA filtering out plugins that are not compatible with the running version of unRAID?

It is an old Seagate Barracuda XT. I just saw that it seemed to be mounted, but it was not! Maybe it did report to support trim when it was mounted, and when it "fell off" fstrim stil thought it was there and tried to trim it? I now rebooted and mounted that drive and fstrim does not report this error any more.

Since a few days I am receiving the following per email: I am using the SSD trim plugin for a long time now and I did not upgrade unraid in the last weeks, I did not add or remove USB drives. Not sure why fstrim would pick a USB HDD drive for trimming, that makes no sense. I searched this topic and found 2 other people reporting it, but saw no solution or response. Maybe some can chime in. I would be interested i a solution.

thanks, I knew that thread. AFAIK it does _not_ contain the crucial information to get folder listings to work again. Just saying. See my last post where I had it highlighted.

Thank you so much. I had the fruit directives already, but the following made the difference (I can now list those folders with many files): readdir_attr:aapl_max_access = no readdir_attr:aapl_finder_info = no readdir_attr:aapl_rsize = no Do people report whether these also help with the timemachine problems?

the link to the report thread is wrong, it links to this thread, not the report thread. do you still have the correct link?

#disable SMB1 for security reasons [global] min protocol = SMB2 #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end [global] vfs objects = catia fruit streams_xattr fruit:nfs_aces = no fruit:zero_file_id = yes fruit:metadata = stream fruit:encoding = native fruit:model = MacSamba fruit:veto_appledouble = no fruit:posix_rename = yes fruit:wipe_intentionally_left_blank_rfork = yes fruit:delete_empty_adfiles = yes spotlight backend = tracker [redacted] path = /mnt/user/redacted veto files = /._*/.DS_Store/ delete veto files = yes spotlight = yes the one of the folders with really many files is in the path with spotlight. another of these folders is not in that path. It makes no difference, I can't list any of those.

That does not sound like you have a solution yet. Did you report the issues officially to limetech already?

I have now been reading the macOS SMB problem reports and posts and the newer Samba in 6.10.3 definitely has problems with macOS. I am using macOS Catalina 10.15.7 I have seen reports about slow SMB, reports about search not working, and reports about TimeMachine not continuing to work after the initial backup. I have all of these problems and more. I could solve the search problem with the hints found in the diverse posts on that problem. Still open issues me: - timemachine - smb is not performing well, although I applied all SMB tweaks to make it work better with macOS - when I try to list folders that contain literally hundreds of files/and or folders it does not work The last problem is especially bad for me as I cannot access my files in folders where I have hundreds of files and/or folders in a folder. In that case it will take a while until the result is just nothing, no matter whether I am using Finder or the shell. This problem doe not occur, if I mount the share on Linux as smb3. This is very likely a problem with the newer Samba on 6.10.3. I did not have these issue with the same macOS when the unraid was running 6.8.x Does anyone else have this issue with many files/folders with unraid 6.10.x under macOS SMB? Were you able to solve it? If not did you report it as a bug already (I did not find a report)? Please put a link to your bug report in your response. Thanks for taking your time to consider my post.

i am regularly seeing this from SMBd in syslog for 3 appdate folders: synthetic_pathref: opening [myappfolder] failed any idea what this means and how to fix it?

regarding logging: I currently have the bacula.log on unraid and I am getting the messages via email. This works fine. I also have a central syslog-ng (this is another container on unraid), where all my services and devices log to over the network. That makes it really more comfortable to identify new problems and also helps with troubleshooting because one is able to see a more complete picture of the situation at hand. I think it would be nice to also have the bacula logs in the central syslog. What would you suggest how to achieve this with your container? Is there already something in there that would allow this functionality? Or would I need to install rsyslog via apt?

regarding this: the configuration with selected FDs connecting to the director is actually legit. The feature is new in 11 and just not yet very mature and I have reported the problems elsewhere. It is quite possible that the feature is not in widespread use yet. For a better understanding: the FD side connection scheduling doesn't work fully correctly, and the FDs start to poll quite aggressively. The Director should still be able to handle this, but there seems to be a bug so that it crashes in such a situation. These things are nothing you or me can do much about (well, I have disabled these FDs for now). It is possible that bacula 13 doesn't have these problems any more, we will see.

Firstly let me clarify that I have no expectations whatsoever, as I know this is a voluntary effort. I am merely making suggestions, feel free to not implement them or to ignore them. They are not made to infuriate you, sorry that this is what you feel about them. I can certainly stop making suggestions if it is stressful for you. About bsmtp: one may actually relax some SPAM settings in postfix (which I use) to get bsmtp to work. Depending on what setup is used these settings might be more or less hidden, e.g. in Synology DMS Mail Server. I firstly tried to install postfix in the container, but apt failed (honestly). When I executed apt today it worked, so I need to apologize, whatever went wrong that day on my end has nothing to do with you. I wouldn't have thought that you take something like when someone said "X doesn't work" personal, it certainly isn't meant like that. So apalogies again, and let me assure you, on my end there are no bad vibes, just trying to make suggestions. Have a nice weekend.