Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754795AbYCLRz3 (ORCPT ); Wed, 12 Mar 2008 13:55:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751909AbYCLRzQ (ORCPT ); Wed, 12 Mar 2008 13:55:16 -0400 Received: from mail3.ldmi.net ([64.118.147.197]:52477 "EHLO mail.ldmi.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752119AbYCLRzO (ORCPT ); Wed, 12 Mar 2008 13:55:14 -0400 Message-ID: <47D818FB.8080302@m2000.com> Date: Wed, 12 Mar 2008 10:55:07 -0700 From: Adam Schrotenboer User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Neil Brown CC: Trond Myklebust , linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org, Thomas Daniel , jesper.juhl@gmail.com, Fred Revenu Subject: Re: [opensuse] nfs_update_inode: inode X mode changed, Y to Z References: <47CF0829.4020502@m2000.com> <1204752463.5035.34.camel@heimdal.trondhjem.org> <47CF157B.1010908@m2000.com> <18383.24847.381754.517731@notabene.brown> <47CF62C5.7000908@m2000.com> <18384.50909.866848.966192@notabene.brown> <47D0D8B5.6050403@m2000.com> In-Reply-To: <47D0D8B5.6050403@m2000.com> X-Enigmail-Version: 0.95.6 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig740E7F2344E950C55AEDB19E" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 8508 Lines: 187 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig740E7F2344E950C55AEDB19E Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Another excerpt from last night. Mar 12 00:53:16 wanda kernel: nfs: server 192.168.1.27 not responding,=20 still trying Mar 12 00:53:18 wanda kernel: nfs: server 192.168.1.27 OK Mar 12 00:54:29 wanda kernel: nfs_update_inode: inode 1075049148 mode=20 changed, 0040755 to 0100644 Mar 12 00:54:49 wanda kernel: nfs_update_inode: inode 1611920610 mode=20 changed, 0100644 to 0040755 Mar 12 00:54:49 wanda kernel: nfs_update_inode: inode 1611920612 mode=20 changed, 0040755 to 0100644 Mar 12 00:54:50 wanda kernel: nfs_update_inode: inode 2685631887 mode=20 changed, 0100644 to 0040755 Mar 12 00:54:50 wanda kernel: nfs_update_inode: inode 3222506021 mode=20 changed, 0100644 to 0040755 Mar 12 00:54:55 wanda kernel: nfs_update_inode: inode 1372131 mode=20 changed, 0100644 to 0040755 Mar 12 00:55:25 wanda kernel: nfs_update_inode: inode 3759413120 mode=20 changed, 0040755 to 0100644 Mar 12 00:56:05 wanda kernel: nfs_update_inode: inode 1075051607 mode=20 changed, 0100644 to 0040755 Mar 12 00:56:05 wanda kernel: nfs_update_inode: inode 1075051608 mode=20 changed, 0040755 to 0100644 Mar 12 00:56:05 wanda kernel: nfs_update_inode: inode 1075051612 mode=20 changed, 0100644 to 0040755 Mar 12 00:56:05 wanda kernel: nfs_update_inode: inode 1075051613 mode=20 changed, 0040755 to 0100644 Mar 12 00:56:06 wanda kernel: nfs_update_inode: inode 1075051616 mode=20 changed, 0100644 to 0040755 Mar 12 00:56:06 wanda kernel: nfs_update_inode: inode 1075051617 mode=20 changed, 0040755 to 0100644 Mar 12 00:56:09 wanda kernel: nfs_update_inode: inode 1075051624 mode=20 changed, 0100644 to 0040755 Mar 12 01:00:33 wanda kernel: nfs_update_inode: inode 1611926434 mode=20 changed, 0040755 to 0100644 Mar 12 01:00:33 wanda kernel: nfs_update_inode: inode 1611926438 mode=20 changed, 0040755 to 0100644 Mar 12 01:00:33 wanda kernel: nfs_update_inode: inode 1611926442 mode=20 changed, 0040755 to 0100644 Mar 12 01:00:33 wanda kernel: nfs_update_inode: inode 1611926446 mode=20 changed, 0040755 to 0100644 Mar 12 01:00:33 wanda kernel: nfs_update_inode: inode 1611926450 mode=20 changed, 0040755 to 0100644 Mar 12 01:00:33 wanda kernel: nfs_update_inode: inode 1611926454 mode=20 changed, 0040755 to 0100644 Mar 12 01:00:33 wanda kernel: nfs_update_inode: inode 1611926458 mode=20 changed, 0040755 to 0100644 Mar 12 01:00:33 wanda kernel: nfs_update_inode: inode 1611926462 mode=20 changed, 0040755 to 0100644 Mar 12 01:00:34 wanda kernel: nfs_update_inode: inode 1611926463 mode=20 changed, 0100644 to 0040755 Mar 12 09:36:46 wanda kernel: nfs_update_inode: inode 538186966 mode=20 changed, 0100644 to 0040755 Mar 12 09:36:46 wanda kernel: nfs_update_inode: inode 538186967 mode=20 changed, 0040755 to 0100644 Mar 12 09:36:46 wanda kernel: nfs_update_inode: inode 538186970 mode=20 changed, 0100644 to 0040755 Mar 12 09:36:46 wanda kernel: nfs_update_inode: inode 538186972 mode=20 changed, 0040755 to 0100644 Mar 12 09:36:47 wanda kernel: nfs_update_inode: inode 538186974 mode=20 changed, 0100644 to 0040755 Mar 12 09:36:47 wanda kernel: nfs_update_inode: inode 538186977 mode=20 changed, 0040755 to 0100644 Mar 12 09:36:47 wanda kernel: nfs_update_inode: inode 538186979 mode=20 changed, 0100644 to 0040755 Mar 12 09:36:47 wanda kernel: nfs_update_inode: inode 538186982 mode=20 changed, 0040755 to 0100644 Mar 12 09:36:47 wanda kernel: nfs_update_inode: inode 538186984 mode=20 changed, 0100644 to 0040755 Mar 12 09:36:47 wanda kernel: nfs_update_inode: inode 538186987 mode=20 changed, 0040755 to 0100644 Mar 12 09:36:47 wanda kernel: nfs_update_inode: inode 538186989 mode=20 changed, 0100644 to 0040755 Mar 12 09:36:47 wanda kernel: nfs_update_inode: inode 538186992 mode=20 changed, 0040755 to 0100644 Mar 12 09:36:47 wanda kernel: nfs_update_inode: inode 538186994 mode=20 changed, 0100644 to 0040755 Mar 12 09:36:47 wanda kernel: nfs_update_inode: inode 538186997 mode=20 changed, 0040755 to 0100644 Mar 12 09:36:47 wanda kernel: nfs_update_inode: inode 538186999 mode=20 changed, 0100644 to 0040755 Mar 12 09:36:47 wanda kernel: nfs_update_inode: inode 538187002 mode=20 changed, 0040755 to 0100644 Mar 12 09:36:47 wanda kernel: nfs_update_inode: inode 538187004 mode=20 changed, 0100644 to 0040755 It keeps going... Another machine, different times. Mar 12 03:35:19 minnow kernel: nfs_update_inode: inode 2685628653 mode=20 changed, 0100644 to 0040755 Mar 12 03:38:01 minnow kernel: nfs_update_inode: inode 2685628658 mode=20 changed, 0100644 to 0040755 Mar 12 03:38:04 minnow kernel: nfs_update_inode: inode 2685628707 mode=20 changed, 0100644 to 0040755 Mar 12 03:38:04 minnow kernel: nfs_update_inode: inode 2685628715 mode=20 changed, 0100644 to 0040755 Mar 12 03:38:04 minnow kernel: nfs_update_inode: inode 2685628719 mode=20 changed, 0100644 to 0040755 Mar 12 03:38:04 minnow kernel: nfs_update_inode: inode 2685628731 mode=20 changed, 0100644 to 0040755 Mar 12 03:38:05 minnow kernel: nfs_update_inode: inode 3222503513 mode=20 changed, 0100644 to 0040755 Mar 12 03:38:05 minnow kernel: nfs_update_inode: inode 2685628818 mode=20 changed, 0100644 to 0040755 Mar 12 03:38:06 minnow kernel: nfs_update_inode: inode 2685628842 mode=20 changed, 0100644 to 0040755 Mar 12 03:38:06 minnow kernel: nfs_update_inode: inode 2685628846 mode=20 changed, 0100644 to 0040755 Mar 12 03:38:06 minnow kernel: nfs_update_inode: inode 2685628851 mode=20 changed, 0100644 to 0040755 Mar 12 03:38:06 minnow kernel: nfs_update_inode: inode 2685628856 mode=20 changed, 0100644 to 0040755 Mar 12 03:38:07 minnow kernel: nfs_update_inode: inode 3222503585 mode=20 changed, 0100644 to 0040755 Mar 12 03:38:09 minnow kernel: nfs_update_inode: inode 2685628923 mode=20 changed, 0100644 to 0040755 Mar 12 03:38:09 minnow kernel: nfs_update_inode: inode 2685628927 mode=20 changed, 0100644 to 0040755 Mar 12 04:00:48 minnow kernel: nfs_update_inode: inode 2149158555 mode=20 changed, 0100644 to 0040755 Mar 12 04:00:51 minnow kernel: nfs_update_inode: inode 1611926234 mode=20 changed, 0040755 to 0100644 Mar 12 04:01:04 minnow kernel: nfs_update_inode: inode 1611926235 mode=20 changed, 0100644 to 0040755 Mar 12 04:01:04 minnow kernel: nfs_update_inode: inode 1611926238 mode=20 changed, 0040755 to 0100644 Mar 12 04:01:04 minnow kernel: nfs_update_inode: inode 1611926240 mode=20 changed, 0100644 to 0040755 Mar 12 04:01:04 minnow kernel: nfs_update_inode: inode 1611926243 mode=20 changed, 0040755 to 0100644 I have other machines it has occurred to as well. The only usage pattern = I have is that it happened mostly while running Mentor's Precision, but=20 I am doubting that that is relevant. This is the line from /proc/mounts on Minnow: 192.168.1.27:/mnt/storage0/users /home/users nfs=20 rw,v3,rsize=3D32768,wsize=3D32768,hard,lock,proto=3Dtcp,addr=3D192.168.1.= 27 0 0 192.168.1.27 is our machine dolphin, which is running OpenSuSE 10.2=20 x86_64 on Intel(R) Xeon(R) CPU E5310 @ 1.60GHz with 4G of RAM, and is=20 an XFS file system running on a Dell PERC5/i adam@dolphin:~$ df -h /mnt/storage0/ Filesystem Size Used Avail Use% Mounted on /dev/sdb1 2.8T 2.0T 807G 72% /mnt/storage0 from /etc/fstab /dev/disk/by-label/storage0 /mnt/storage0 xfs rw,usrquota,grpquota 0 0 It is not running with inode64, but probably should be. Hasn't become a=20 problem yet. Otoh, I understand that NFS v3 doesn't support 64bit inode=20 numbers. FYI almost all of our NFS clients are x86_64 Linux(except 2) I have CC:d Fred Revenu, who was the person who brought it to my=20 attention this morning that it had happened again last night. --------------enig740E7F2344E950C55AEDB19E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH2Bj7yWYDdvnGArwRAzQyAKCQvrE/Lez797RA9uaPnsAFTSVSCACeJCrx h6Si6jeBnX8difzuSdVg4mg= =9xrU -----END PGP SIGNATURE----- --------------enig740E7F2344E950C55AEDB19E-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/