A very odd situation here......
A very odd situation here.
I have a (freebsd) server serving a tree of photos and information
files. It's large, and the paths quite long - whether that's relevant I don't know.
On two of three machines all running mint at various versions all is
well; I have problems on the third, which happens to be my desktop box.
An example good listing would be (sorry about wrap):
mike@troi ~ $ ls /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.* /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.exif /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--info.html /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.sha /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.html /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.png /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--thumb.png
That corresponds exactly to what's on the server.
However, on my desktop m/c, the same command complains about a missing
file, and triplicates all the lines bar the first, which is duplicated,
and there's an error about not finding a file that has an incorrect name anyway:
Desktop> ls /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.*
ls: cannot access '/nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.2': No such file or directory
/nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.exif /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.exif /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--info.html /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--info.html /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--info.html /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.sha /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.sha /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.sha /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.html /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.html /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.html /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.png /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.png /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.png /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--thumb.png /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--thumb.png /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--thumb.png
If I unmount and remount the file system, I get different results -
always works on the other machines, and fails /differently/ each time on mine.
I've also seen this happen in a virtual machine running on my box.
It happens whether I hard mount or use the automounter.
The OS versions are different - I'm running mint 21.2, the VM is at
21.3; while the others are both rather older versions (and different hardware). The machines are all configured the same.
I'm at a loss! Can anyone suggest what's going on here please? I'm sure
this used to work!
Thanks.
Wild guess, running out of disk space?
A very odd situation here.
I have a (freebsd) server serving a tree of photos and information
files. It's large, and the paths quite long - whether that's relevant
I don't know.
On two of three machines all running mint at various versions all is
well; I have problems on the third, which happens to be my desktop
box. An example good listing would be (sorry about wrap):
mike@troi ~ $ ls /nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.*
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.exif
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--info.html
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.sha
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.html
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.png
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--thumb.png
That corresponds exactly to what's on the server.
However, on my desktop m/c, the same command complains about a missing
file, and triplicates all the lines bar the first, which is
duplicated, and there's an error about not finding a file that has an incorrect name anyway:
Desktop> ls /nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.*
ls: cannot access '/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.2':
No such file or directory /nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.exif
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.exif
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--info.html
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--info.html
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--info.html
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.sha
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.sha
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.sha
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.html
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.html
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.html
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.png
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.png
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.png
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--thumb.png
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--thumb.png
/nfs/mmedia/pictures/originals-index4/mike/camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--thumb.png
If I unmount and remount the file system, I get different results -
always works on the other machines, and fails /differently/ each time
on mine.
I've also seen this happen in a virtual machine running on my box.
It happens whether I hard mount or use the automounter.
The OS versions are different - I'm running mint 21.2, the VM is at
21.3; while the others are both rather older versions (and different hardware). The machines are all configured the same.
I'm at a loss! Can anyone suggest what's going on here please? I'm
sure this used to work!
A very odd situation here.
I have a (freebsd) server serving a tree of photos and information
files. It's large, and the paths quite long - whether that's relevant I don't know.
On 2025-01-24 17:56, Mike Scott wrote:
A very odd situation here.
I have a (freebsd) server serving a tree of photos and information files. >> It's large, and the paths quite long - whether that's relevant I don't know.
If you are using nfs version 3, perhaps try version 4.
If version 4, what's in the exports file?
All client machines have the same fstab nfs entry?
A very odd situation here.
I have a (freebsd) server serving a tree of photos and information
files. It's large, and the paths quite long - whether that's relevant I don't know.
On two of three machines all running mint at various versions all is
well; I have problems on the third, which happens to be my desktop box.
An example good listing would be (sorry about wrap):
The OS versions are different - I'm running mint 21.2, the VM is at
21.3; while the others are both rather older versions (and different hardware). The machines are all configured the same.
I'm at a loss! Can anyone suggest what's going on here please? I'm sure
this used to work!
On Fri, 1/24/2025 4:56 PM, Carlos E.R. wrote:
On 2025-01-24 17:56, Mike Scott wrote:
A very odd situation here.
The FreeBSD have their own taste in software, so there's no reason
for anything to particularly match Linux.
I would be examining the versions on the cases that work,
and checking the versions in the non-working case.
In mo9dern times, some of the computers have "power management"
and that could influence whether things like "stale mounts"
are showing up. You would want to find a log and see if
there is any sign of behaviors like that (mount malfunctions
because the disk could not be accessed in time, like a stat()
check).
Even your NIC can be set to power down when not in use.
On 2025-01-24 17:56, Mike Scott wrote:
A very odd situation here.
I have a (freebsd) server serving a tree of photos and information
files. It's large, and the paths quite long - whether that's relevant
I don't know.
If you are using nfs version 3, perhaps try version 4.
If version 4, what's in the exports file?
All client machines have the same fstab nfs entry?
find /nfs/mmedia/pictures/ -ls >/dev/nullfind: ‘/nfs/mmedia/pictures/originals-index4/mike/camera2018/20181210/2018-12-10/’:
On two of three machines all running mint at various versions all is
well; I have problems on the third, which happens to be my desktop box.
A very odd situation here.
I have a (freebsd) server serving a tree of photos and information
files. It's large, and the paths quite long - whether that's relevant I don't know.
On two of three machines all running mint at various versions all is
well; I have problems on the third, which happens to be my desktop box.
An example good listing would be (sorry about wrap):
mike@troi ~ $ ls /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.* /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.exif /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--info.html /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.sha /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.html /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.png /nfs/mmedia/pictures/originals-index4/mike/ camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--thumb.png
That corresponds exactly to what's on the server.
However, on my desktop m/c, the same command complains about a missing
file, and triplicates all the lines bar the first, which is duplicated,
and there's an error about not finding a file that has an incorrect name anyway:
If I unmount and remount the file system, I get different results -
always works on the other machines, and fails /differently/ each time on mine.
I've also seen this happen in a virtual machine running on my box.
It happens whether I hard mount or use the automounter.
The OS versions are different - I'm running mint 21.2, the VM is at
21.3; while the others are both rather older versions (and different hardware). The machines are all configured the same.
I'm at a loss! Can anyone suggest what's going on here please? I'm sure
this used to work!
Mike Scott <usenet.16@scottsonline.org.uk.invalid> writes:
A very odd situation here.
I have a (freebsd) server serving a tree of photos and information
files. It's large, and the paths quite long - whether that's relevant
I don't know.
I'm at a loss! Can anyone suggest what's going on here please? I'm
sure this used to work!
Formerly, Linux NFS servers could get confused by large directories. https://lwn.net/Articles/544520/ is the best writeup I’ve found.
In your case the server is FreeBSD, so Linux’s historical bugs aren’t directly relevant, beyond highlighting that merely listing a directory
is more complex than you might initially imagine. I’m not sure why a hypothetical similar bug in FreeBSD would only be visible on a subset of clients either.
In spite of my assertion (which I should have checked and didn't), the
mount options differed. The working machines all specified rsize=8192.
My box was using a much larger figure, of 131072 (ie 32 * 4096).
It seems anything over 8192 causes this issue - that filenames get truncated.
Whether that's a linux client issue or a freebsd server issue, or the
result of interworking, I've no idea. Nor can I imagine why it should
happen without errors being flagged up somewhere (I checked the logs at
both ends) -- which is nasty, because I had a system that met the specs
and mostly worked but very occasionally (< about 1 in 100k times, I
reckon) failed silently. Ouch.
On Mon, 27 Jan 2025 15:41:37 +0000, Mike Scott wrote:
In spite of my assertion (which I should have checked and didn't), the
mount options differed. The working machines all specified rsize=8192.
My box was using a much larger figure, of 131072 (ie 32 * 4096).
It seems anything over 8192 causes this issue - that filenames get
truncated.
I don’t understand why increasing rsize on its own would have any
effect: according to the docs, that only controls the maximum size of
packets that this end can receive; the maximum size the other end can
send is limited by that end’s wsize value. So increasing rsize on its
own should have no effect.
Looking up NFS mount options online, this page <https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/4/html/reference_guide/s2-nfs-client-config-options#s2-nfs-client-config-options>
does say “be careful when changing these values; some older Linux
kernels and network cards do not work well with larger block sizes”.
Whether that's a linux client issue or a freebsd server issue, or the
result of interworking, I've no idea. Nor can I imagine why it should
happen without errors being flagged up somewhere (I checked the logs at
both ends) -- which is nasty, because I had a system that met the specs
and mostly worked but very occasionally (< about 1 in 100k times, I
reckon) failed silently. Ouch.
That really baffles me, that you don’t see any errors indicating there was a problem.
On 27/01/2025 23:24, Lawrence D'Oliveiro wrote:
On Mon, 27 Jan 2025 15:41:37 +0000, Mike Scott wrote:
So I'll have to settle for 'it works now'. But as I noted, I'm very discomforted that such a problem is even possible without errors being flagged somewhere.
On 27/01/2025 23:24, Lawrence D'Oliveiro wrote:
On Mon, 27 Jan 2025 15:41:37 +0000, Mike Scott wrote:
In spite of my assertion (which I should have checked and didn't), the
mount options differed. The working machines all specified rsize=8192.
My box was using a much larger figure, of 131072 (ie 32 * 4096).
It seems anything over 8192 causes this issue - that filenames get
truncated.
I don’t understand why increasing rsize on its own would have any
effect: according to the docs, that only controls the maximum size of packets that this end can receive; the maximum size the other end can
send is limited by that end’s wsize value. So increasing rsize on its
own should have no effect.
Looking up NFS mount options online, this page <https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/4/html/reference_guide/s2-nfs-client-config-options#s2-nfs-client-config-options>
does say “be careful when changing these values; some older Linux
kernels and network cards do not work well with larger block sizes”.
Whether that's a linux client issue or a freebsd server issue, or the
result of interworking, I've no idea. Nor can I imagine why it should
happen without errors being flagged up somewhere (I checked the logs at
both ends) -- which is nasty, because I had a system that met the specs
and mostly worked but very occasionally (< about 1 in 100k times, I
reckon) failed silently. Ouch.
That really baffles me, that you don’t see any errors indicating there was
a problem.
Yes, it's an odd one in many ways. Not least because rsize/wsize are supposed to be irrelevant for tcp mounts (which is all the server
provides anyway)
I've just tried a loopback NFS mount on the server (it's the only fbsd
box I have to hand) and can't force the problem to show. So presumably
it's something to do with the inter-system working, but I don't have the knowledge to delve further :-{
So I'll have to settle for 'it works now'. But as I noted, I'm very discomforted that such a problem is even possible without errors being flagged somewhere.
Thanks again to all who've responded.
--
Mike Scott
Harlow, England
| Sysop: | Luis Silva |
|---|---|
| Location: | Lisbon |
| Users: | 764 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 54:54:40 |
| Calls: | 270 |
| Files: | 46,971 |
| Messages: | 12,678 |