> On 6. Mar 2025, at 13:41, Udo Grabowski (IMKASF) <udo.grabow...@kit.edu> > wrote: > > On 05-03-2025 12:47, Udo Grabowski (IMKASF) wrote: >> Hi, >> for a while now, we see NFS problems quite often we've not seen >> before, here between an oi_151a9 client and a recent 2024:12:12 >> illumos-b7fe974ee3 server; starts with a file <null string>, then >> mixed up seqids, loosing track for several file openings: >> Mar 5 10:08:34 imksuns11 nfs: [ID 435015 kern.info] NOTICE: [NFS4] [Server: >> imksunth11][Mntpt: /home/Processor/Work_22]Operation open for file <null >> string> (rnode_pt 0x0), pid 0 using seqid 1 got NFS4ERR_BAD_SEQID. Last >> good seqid was 0 for operation . >> Mar 5 10:08:38 imksuns11 nfs: [ID 435015 kern.info] NOTICE: [NFS4] [Server: >> imksunth11][Mntpt: /home/Processor/Work_22]Operation open for file >> ./CEDRO_2_ES/SF6:X_262.0/bout/create_coarse_inp_30300.log (rnode_pt >> 0xfffffeed90af63f8), pid 0 using seqid 2 got NFS4ERR_BAD_SEQID. Last good >> seqid was 1 for operation open. >> Mar 5 10:08:40 imksuns11 nfs: [ID 435015 kern.info] NOTICE: [NFS4] [Server: >> imksunth11][Mntpt: /home/Processor/Work_22]Operation open for file >> ./CEDRO_2_ES/SF6:X_262.0/bout/create_coarse_inp_30300.log (rnode_pt >> 0xfffffeed90af63f8), pid 0 using seqid 1 got NFS4ERR_BAD_SEQID. Last good >> seqid was 1 for operation open. >> ... > > This probably also has happened with new clients, but I'm yet not sure > > about that. It's happening often enough that it is significantly > > disturbing operations here. > > We now know that this definitely happens with recent clients, too.
what kind of operations are done there? maybe 'snoop rpc nfs’ ? Just plain mount and edit file and save has no problem… rgds, toomas ------------------------------------------ illumos: illumos-discuss Permalink: https://illumos.topicbox.com/groups/discuss/T939fcf899d5526b0-M73a48ff56ae211b895d9e5e0 Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
