Groups | Search | Server Info | Login | Register
Groups > comp.os.linux.networking > #8535
| From | Mike Scott <usenet.16@scottsonline.org.uk.invalid> |
|---|---|
| Newsgroups | alt.os.linux.mint, comp.os.linux.networking |
| Subject | Re: very odd nfs behaviour |
| Date | 2025-01-25 17:02 +0000 |
| Organization | Scott family |
| Message-ID | <vn35fb$2tv0e$1@dont-email.me> (permalink) |
| References | <vn0gn0$2ajlc$1@dont-email.me> <eted6lx2bv.ln2@Telcontar.valinor> |
Cross-posted to 2 groups.
On 24/01/2025 21:56, Carlos E.R. wrote: > 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? > > > Thanks to all for commenting. To clarify a few points: The clients in question all use autofs, and the tables are copies of a central master. So nfs options should be the same. On my own machine, it made no difference whether the fs was automounted, or manually. The precise point of error changes when the fs is remounted, manually or by reboot. BTW NFSv4 isn't really an option. A very different beast, and doesn't seem to offer anything I need. It used to work, I'm (nearly) sure - it affects my software to make a photo index which dates back years. I'm sure I'd have noticed an issue. The directories can each have several hundred files. Currently, I see: Desktop> find /nfs/mmedia/pictures/originals-index4/mike/master_digital_camera/2008_0418/ -ls >/dev/null find: ‘/nfs/mmedia/pictures/originals-index4/mike/master_digital_camera/2008_0418/2008_040’: No such file or directory ls /nfs/mmedia/pictures/originals-index4 [linewrapped] /mike/master_digital_camera[/2008_0418/ <skip> 2008_0216_102631.jpg--slide.png 2008_0216_102631.jpg--thumb.png 2008_040 <<<<< odd extra entry 2008_0406_070443.jpg.exif etc I copied just that folder to within /tmp, so local: the initial copy failed because of that bad entry, so I did a copy-and-paste of the originals. A 'diff -r' on the two directories moaned that 2008_040 only existed on the nfs folder, so at least at the moment, it's a spurious extra entry rather than a mangled real one. FWIW my machine is on Linux Mint 21.2 Victoria; one of the working ones is on Linux Mint 21.1 Vera, so not too different. The lappy I can't check ATM. ...... Oh, I've just rebooted after an abortive attempt to run a DVD live system. Now I get ~> find /nfs/mmedia/pictures/ -ls >/dev/null find: ‘/nfs/mmedia/pictures/originals-index4/mike/camera2018/20181210/2018-12-10/’: No such file or directory find: ‘/nfs/mmedia/pictures/originals-nokeys-index/mike/master_digital_camera/2008_1219/2008_121’: No such file or directory find: ‘/nfs/mmedia/pictures/originals-nokeys-index/mike/camera2018/20181210/2018-12-10/’: No such file or directory ~> I'm pretty sure I had a "filename too long" yesterday as well. I'm at a loss as to what to try next - the live DVD seemed a good idea, but wouldn't boot: I'll have to think about a fresh thread for that one. -- Mike Scott Harlow, England
Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar
very odd nfs behaviour Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-01-24 16:56 +0000
Re: very odd nfs behaviour Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-01-24 17:00 +0000
Re: very odd nfs behaviour Edmund <nomail@hotmail.com> - 2025-01-24 18:01 +0100
Re: very odd nfs behaviour Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-01-24 17:30 +0000
Re: very odd nfs behaviour Richard Kettlewell <invalid@invalid.invalid> - 2025-01-24 17:55 +0000
(resolved) Re: very odd nfs behaviour Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-01-27 15:41 +0000
Re: (resolved) Re: very odd nfs behaviour Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-27 23:24 +0000
Re: (resolved) Re: very odd nfs behaviour Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-01-28 08:06 +0000
Re: (resolved) Re: very odd nfs behaviour "Carlos E.R." <robin_listas@es.invalid> - 2025-01-28 12:34 +0100
Re: (resolved) Re: very odd nfs behaviour pinnerite <pinnerite@gmail.com> - 2025-01-28 22:58 +0000
Re: very odd nfs behaviour "Carlos E.R." <robin_listas@es.invalid> - 2025-01-24 22:56 +0100
Re: very odd nfs behaviour Paul <nospam@needed.invalid> - 2025-01-24 17:34 -0500
Re: very odd nfs behaviour "Carlos E.R." <robin_listas@es.invalid> - 2025-01-25 01:45 +0100
Re: very odd nfs behaviour Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-01-25 17:02 +0000
Re: very odd nfs behaviour "Arti F. Idiot" <addr@is.invalid> - 2025-01-24 17:13 -0700
Re: very odd nfs behaviour Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-26 00:01 +0000
Re: very odd nfs behaviour Grant Taylor <gtaylor@tnetconsulting.net> - 2025-01-25 20:08 -0600
csiph-web