Log File keeps filing up

[Cobragt88]

Hello all I'm not 100% why this keeps happening. Hope is nothing serious.

lowenas-diagnostics-20210428-0927.zip

[Squid]

2 reasons:

 

Apr 25 18:39:51 LoweNAS kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window]
Apr 25 18:39:51 LoweNAS kernel: caller _nv000712rm+0x1af/0x200 [nvidia] mapping multiple BARs

Which a BIOS update may fix (happens to me on occasion, and I just reboot the server)

 

And

Apr 27 06:45:10 LoweNAS kernel: NFS: server 192.168.0.4 error: fileid changed
Apr 27 06:45:10 LoweNAS kernel: fsid 0:178: expected fileid 0x901000021ec2e3d, got 0x2f000000102d1e

(I don't run NFS, so can't offer much up there)

[John_M]

Half the error messages are this:

 

Apr 25 16:00:38 LoweNAS kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window]
Apr 25 16:00:38 LoweNAS kernel: caller _nv000712rm+0x1af/0x200 [nvidia] mapping multiple BARs

 

which is a "feature" of the Nvidia driver - if you look at the support thread you'll see a discussion about it. You can stop it by removing the GPU Stats plugin.

 

The other half are this:

 

Apr 27 07:54:47 LoweNAS kernel: NFS: server 192.168.0.4 error: fileid changed
Apr 27 07:54:47 LoweNAS kernel: fsid 0:178: expected fileid 0x2f000000000103, got 0x901000010000080

 

which looks like the NFS stale file handle problem.

 

[Cobragt88]

3 minutes ago, John_M said:

Half the error messages are this:

 

Apr 25 16:00:38 LoweNAS kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window]
Apr 25 16:00:38 LoweNAS kernel: caller _nv000712rm+0x1af/0x200 [nvidia] mapping multiple BARs

 

which is a "feature" of the Nvidia driver - if you look at the support thread you'll see a discussion about it. You can stop it by removing the GPU Stats plugin.

 

The other half are this:

 

Apr 27 07:54:47 LoweNAS kernel: NFS: server 192.168.0.4 error: fileid changed
Apr 27 07:54:47 LoweNAS kernel: fsid 0:178: expected fileid 0x2f000000000103, got 0x901000010000080

 

which looks like the NFS stale file handle problem.

 

removed NFS and GPU stats plug for now. Wish I didn't have to restart to clear the log file .........

 

[John_M]

Try turning off support for hard links in User shares if you don't specifically need it. That is the main culprit for causing stale file handles.

[John_M]

See here for the Nvidia driver discussion, and here for an explanation of the NFS issue.

[Cobragt88]

16 minutes ago, John_M said:

See here for the Nvidia driver discussion, and here for an explanation of the NFS issue.

So I have 2 Unraid boxes one is my backup to my main box, what would be the best solution plugin option to backup one unraid volume to the other unraid box? Not using crappy "NFS"?

 

Thanks for all the help I read the other posts.

[John_M]

I use NFS. It isn't crappy. It's just old. I also used AFP until it was removed from Unraid. If you want a real example of crappy, I offer you the closed source Nvidia driver.

 

You could use rsync with the -e option, which doesn't require mounting the remote share.

 

[Cobragt88]

i'll let you know how it goes with the -e and not mounting the remote share.