Hi all,
Looking back at the archives=20
(http://marc.theaimsgroup.com/?t=3D101707335800002&r=3D1&w=3D2) I see tha=
t you=20
(Trond) say that these copious "RPC: Unable..." messages shouldn't be a=20
problem. Could they be a problem?
The reason I ask is, occassionally, we're getting these strange files=20
created with 0 size, date, and some gobble-dee-gook names, and they just =
so=20
happen to show up when we get this error message in the logs. Here's wha=
t=20
one looks like:
bash-2.04$ ls -l |egrep -v '(fit|ps|fp|mem)'
total 5742612
-rwxr-xr-x 1 jen_a sdss 0 Dec 31 1969
:N=A8TL8=D5 =E4=F0=FF=FF=EB=FE=FF=F5@ =
=A6,
The rest of the files are OK, but this is slightly disconcerting.
This is 2.4.18 + XFS + NFS_ALL - rpc_tweaks, IIRC (it's been a long time =
since I've built this kernel). The system has 2GB RAM and 4GB swap (himem=
is=20
enabled).
Any thoughts?
Thanks,
Dan
--=20
Dan Yocum
Sloan Digital Sky Survey, Fermilab 630.840.6509
[email protected], http://www.sdss.org
SDSS. Mapping the Universe.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
>>>>> " " =3D=3D Dan Yocum <[email protected]> writes:
> Hi all, Looking back at the archives
> (http://marc.theaimsgroup.com/?t=3D101707335800002&r=3D1&w=3D2) I see
> that you (Trond) say that these copious "RPC: Unable..."=20
> messages shouldn't be a problem. Could they be a problem?
> The reason I ask is, occassionally, we're getting these strange
> files created with 0 size, date, and some gobble-dee-gook
> names, and they just so happen to show up when we get this
> error message in the logs. Here's what one looks like:
> bash-2.04$ ls -l |egrep -v '(fit|ps|fp|mem)' total 5742612
> -rwxr-xr-x 1 jen_a sdss 0 Dec 31 1969 :N=A8TL8=D5 =E4=F0=FF=FF=EB=FE=
=FF=F5@ =A6,
> The rest of the files are OK, but this is slightly
> disconcerting.
That's totally unrelated to the above message, and looks rather like a
server bug. Is the server also 2.4.18+XFS?
Cheers,
Trond
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Yes, the error message is on the server system and it is running 2.4.18+X=
FS.
I guess I didn't realize that the error message is being created by the c=
lient.
Dan
Trond Myklebust wrote:
>>>>>>" " =3D=3D Dan Yocum <[email protected]> writes:
>>>>>
>=20
> > Hi all, Looking back at the archives
> > (http://marc.theaimsgroup.com/?t=3D101707335800002&r=3D1&w=3D2) =
I see
> > that you (Trond) say that these copious "RPC: Unable..."=20
> > messages shouldn't be a problem. Could they be a problem?
>=20
>=20
> > The reason I ask is, occassionally, we're getting these strange
> > files created with 0 size, date, and some gobble-dee-gook
> > names, and they just so happen to show up when we get this
> > error message in the logs. Here's what one looks like:
>=20
>=20
> > bash-2.04$ ls -l |egrep -v '(fit|ps|fp|mem)' total 5742612
> > -rwxr-xr-x 1 jen_a sdss 0 Dec 31 1969 :N=A8TL8=D5 =E4=F0=FF=FF=EB=
=FE=FF=F5@ =A6,
>=20
> > The rest of the files are OK, but this is slightly
> > disconcerting.
>=20
> That's totally unrelated to the above message, and looks rather like a
> server bug. Is the server also 2.4.18+XFS?
>=20
> Cheers,
> Trond
>=20
--=20
Dan Yocum
Sloan Digital Sky Survey, Fermilab 630.840.6509
[email protected], http://www.sdss.org
SDSS. Mapping the Universe.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs