[OpenAFS] RE: OpenAFS-info digest, Vol 1 #5205 - 9 msgs
sabah s. salih
sabah.salih@hep.manchester.ac.uk
Wed, 2 Feb 2011 14:21:09 +0000
Dear Derrick,=0A=
Since this morning none of our users could see their home area in=
AFS. =0A=
=0A=
Our database servers are =0A=
=0A=
afs1.hep.man.ac.uk=0A=
afs2.hep.man.ac.uk=0A=
afs3.hep.man.ac.uk=0A=
=0A=
and we have from afs5 - afs17 our fileservers=0A=
=0A=
I can do =0A=
vos listvo afs1.hep.man.ac.uk |more=0A=
.=0A=
.=0A=
.=0A=
. =0A=
vos listvo afs17.hep.manchester.ac.uk |more=0A=
=0A=
and I can list all users volumes without any problems =0A=
They are all on line.=0A=
=0A=
however none of us could type=0A=
ls =0A=
/afs/hep.man.ac.uk/u/sabah=0A=
. =0A=
.=0A=
.=0A=
.=0A=
.=0A=
=0A=
Any Idea what goes wrong ?=0A=
=0A=
Many Thanks, Sabah.=0A=
=0A=
=0A=
>From Sabah Salih=0A=
The School of Physics and Astronomy,=0A=
The University of Manchester,=0A=
Schuster Laboratory,=0A=
Brunswick Street,=0A=
Manchester M13 9PL.=0A=
Tel: +44 1612754171 or x4171=0A=
E-mail: sabah.salih@hep.manchester.ac.uk=0A=
________________________________________=0A=
From: openafs-info-admin@openafs.org [openafs-info-admin@openafs.org] on be=
half of openafs-info-request@openafs.org [openafs-info-request@openafs.org]=
=0A=
Sent: 02 February 2011 14:11=0A=
To: openafs-info@openafs.org=0A=
Subject: OpenAFS-info digest, Vol 1 #5205 - 9 msgs=0A=
=0A=
Send OpenAFS-info mailing list submissions to=0A=
openafs-info@openafs.org=0A=
=0A=
To subscribe or unsubscribe via the World Wide Web, visit=0A=
https://lists.openafs.org/mailman/listinfo/openafs-info=0A=
or, via email, send a message with subject or body 'help' to=0A=
openafs-info-request@openafs.org=0A=
=0A=
You can reach the person managing the list at=0A=
openafs-info-admin@openafs.org=0A=
=0A=
When replying, please edit your Subject line so it is more specific=0A=
than "Re: Contents of OpenAFS-info digest..."=0A=
=0A=
=0A=
Today's Topics:=0A=
=0A=
1. Re: Re: Need volume state / fileserver / salvage knowledge (Jeff Blai=
ne)=0A=
2. Re: Re: Need volume state / fileserver / salvage knowledge (Patricia =
O'Reilly)=0A=
3. Re: Need volume state / fileserver / salvage knowledge (Andrew Deason=
)=0A=
4. Re: Status of OS X 10.6 64bit kernel support ? (Chris Jones)=0A=
5. Re: Status of OS X 10.6 64bit kernel support ? (Chris Jones)=0A=
6. openafs on suse 10.2 with kernel 2.6.18.2-34-default (rosatrancoso)=
=0A=
7. RE: OpenAFS-info digest, Vol 1 #5201 - 10 msgs (sabah s. salih)=0A=
8. can not access to users home area (sabah s. salih)=0A=
9. Re: can not access to users home area (Derrick Brashear)=0A=
=0A=
--__--__--=0A=
=0A=
Message: 1=0A=
Date: Tue, 01 Feb 2011 14:39:18 -0500=0A=
From: Jeff Blaine <jblaine@kickflop.net>=0A=
To: openafs-info@openafs.org=0A=
Subject: Re: [OpenAFS] Re: Need volume state / fileserver / salvage knowled=
ge=0A=
=0A=
>>> Wed Jan 26 12:28:13 2011: upclientetc exited on signal 15=0A=
>>> Wed Jan 26 12:28:13 2011: upclientbin exited on signal 15=0A=
>>> Wed Jan 26 12:28:24 2011: fs:vol exited on signal 15=0A=
>>> Wed Jan 26 12:58:19 2011: bos shutdown: fileserver failed to shutdown w=
ithin 1800 seconds=0A=
>>> Wed Jan 26 12:58:37 2011: fs:file exited on signal 9=0A=
=0A=
Thanks for the replies.=0A=
=0A=
I can't at all fathom that our issue is one of existing=0A=
client connections and callback break completion (timing out).=0A=
=0A=
> Also, in this specific case, it may not be just that shutting down=0A=
> volumes took too long. 1.4.11 has known problems that can cause this=0A=
> (e.g. the host list gets a loop in it, and something spins forever=0A=
> trying to traverse the whole list).=0A=
=0A=
That's this, I think?:=0A=
=0A=
- Fixes to avoid issues cleaning up deleted hosts in=0A=
the fileserver (126454)=0A=
=0A=
Let's assume this issue is what caused our problem. I'm sort=0A=
of at a loss as to how to approach OpenAFS versions. On one=0A=
hand, expectations of more effort to make it clear in the=0A=
release notes what items could cause something like unclean=0A=
server shutdowns (kind of a big deal, IMO) are not really=0A=
justifiable. It's open source, etc. On the other hand,=0A=
it's not acceptable to blindly upgrade to the latest stable=0A=
release every time it comes out. I understand that the most=0A=
obvious take-away is just, "You got bit. Move on.", but=0A=
if anything can improve on our end, I'd like to do that.=0A=
=0A=
I welcome any suggestions for how others are approaching this.=0A=
=0A=
Jeff Blaine=0A=
=0A=
--__--__--=0A=
=0A=
Message: 2=0A=
Date: Tue, 01 Feb 2011 12:04:08 -0800=0A=
From: Patricia O'Reilly <oreilly@qualcomm.com>=0A=
To: Jeff Blaine <jblaine@kickflop.net>=0A=
Cc: openafs-info@openafs.org=0A=
Subject: Re: [OpenAFS] Re: Need volume state / fileserver / salvage knowled=
ge=0A=
=0A=
>From what you have described it sounds to me like you need the patch that A=
ndrew referenced earlier that allows you to configure an -offline-timeout a=
nd -offline-shutdown-timeout option on your fileservers. We have has simila=
r problems at our site and will be releasing that patch into production sho=
rtly.=0A=
=0A=
--patty=0A=
=0A=
Jeff Blaine wrote:=0A=
>>>> Wed Jan 26 12:28:13 2011: upclientetc exited on signal 15=0A=
>>>> Wed Jan 26 12:28:13 2011: upclientbin exited on signal 15=0A=
>>>> Wed Jan 26 12:28:24 2011: fs:vol exited on signal 15=0A=
>>>> Wed Jan 26 12:58:19 2011: bos shutdown: fileserver failed to=0A=
>>>> shutdown within 1800 seconds=0A=
>>>> Wed Jan 26 12:58:37 2011: fs:file exited on signal 9=0A=
>=0A=
> Thanks for the replies.=0A=
>=0A=
> I can't at all fathom that our issue is one of existing=0A=
> client connections and callback break completion (timing out).=0A=
>=0A=
>> Also, in this specific case, it may not be just that shutting down=0A=
>> volumes took too long. 1.4.11 has known problems that can cause this=0A=
>> (e.g. the host list gets a loop in it, and something spins forever=0A=
>> trying to traverse the whole list).=0A=
>=0A=
> That's this, I think?:=0A=
>=0A=
> - Fixes to avoid issues cleaning up deleted hosts in=0A=
> the fileserver (126454)=0A=
>=0A=
> Let's assume this issue is what caused our problem. I'm sort=0A=
> of at a loss as to how to approach OpenAFS versions. On one=0A=
> hand, expectations of more effort to make it clear in the=0A=
> release notes what items could cause something like unclean=0A=
> server shutdowns (kind of a big deal, IMO) are not really=0A=
> justifiable. It's open source, etc. On the other hand,=0A=
> it's not acceptable to blindly upgrade to the latest stable=0A=
> release every time it comes out. I understand that the most=0A=
> obvious take-away is just, "You got bit. Move on.", but=0A=
> if anything can improve on our end, I'd like to do that.=0A=
>=0A=
> I welcome any suggestions for how others are approaching this.=0A=
>=0A=
> Jeff Blaine=0A=
> _______________________________________________=0A=
> OpenAFS-info mailing list=0A=
> OpenAFS-info@openafs.org=0A=
> https://lists.openafs.org/mailman/listinfo/openafs-info=0A=
=0A=
--__--__--=0A=
=0A=
Message: 3=0A=
To: openafs-info@openafs.org=0A=
From: Andrew Deason <adeason@sinenomine.net>=0A=
Date: Tue, 1 Feb 2011 14:58:24 -0600=0A=
Organization: Sine Nomine Associates=0A=
Subject: [OpenAFS] Re: Need volume state / fileserver / salvage knowledge=
=0A=
=0A=
On Tue, 01 Feb 2011 12:04:08 -0800=0A=
Patricia O'Reilly <oreilly@qualcomm.com> wrote:=0A=
=0A=
> From what you have described it sounds to me like you need the patch=0A=
> that Andrew referenced earlier that allows you to configure an=0A=
> -offline-timeout and -offline-shutdown-timeout option on your=0A=
> fileservers. We have has similar problems at our site and will be=0A=
> releasing that patch into production shortly.=0A=
=0A=
Maybe, maybe not. I think the most common cause of this is just having=0A=
too many volumes that can be shut down in 30 minutes. Determining this=0A=
is easy; if it happens every single time you shut down the fileserver,=0A=
that's probably it. (But obviously that's not fun to do.)=0A=
=0A=
But it could also be the 1.4.11 host package bugs; I don't know, and I=0A=
just noted that cause to illustrate that there are several possible=0A=
reasons.=0A=
=0A=
> Jeff Blaine wrote:=0A=
> >=0A=
> > Thanks for the replies.=0A=
> >=0A=
> > I can't at all fathom that our issue is one of existing=0A=
> > client connections and callback break completion (timing out).=0A=
=0A=
I'd only say that if you have pretty good control over all of your=0A=
clients. It's possible to see some really bizarre behavior (from the=0A=
fileserver's point of view) from old clients or clients on=0A=
oddly-behaving networks or NATs.=0A=
=0A=
> >> Also, in this specific case, it may not be just that shutting down=0A=
> >> volumes took too long. 1.4.11 has known problems that can cause this=
=0A=
> >> (e.g. the host list gets a loop in it, and something spins forever=0A=
> >> trying to traverse the whole list).=0A=
> >=0A=
> > That's this, I think?:=0A=
> >=0A=
> > - Fixes to avoid issues cleaning up deleted hosts in=0A=
> > the fileserver (126454)=0A=
=0A=
There were a few issues; all of the ones known to cause problems are=0A=
included in 1.4.12. I don't have references for all of them off the top=0A=
of my head, but I can get them for you if you want.=0A=
=0A=
> > Let's assume this issue is what caused our problem. I'm sort of at=0A=
> > a loss as to how to approach OpenAFS versions. On one hand,=0A=
> > expectations of more effort to make it clear in the release notes=0A=
> > what items could cause something like unclean server shutdowns (kind=0A=
> > of a big deal, IMO) are not really justifiable.=0A=
=0A=
This wasn't an issue causing fileserver shutdowns to hang and get=0A=
killed, it was a general fileserver stability issue; that hang (or=0A=
crash, or however it manifested; I've seen both) could happen at any=0A=
time.=0A=
=0A=
And doing something like that actually isn't that difficult for at least=0A=
most of the issues I am involved with. I already generally know which=0A=
versions are affected for the bigger issues, so just writing that down=0A=
would not be that hard. (But going back through all of the changes=0A=
between 1.4.Z and 1.4 head would be a lot of work at this point) But=0A=
that's not true for all changes, and I think it may be prohibitively=0A=
difficult if we had to include information like that with every single=0A=
change to the stable branch.=0A=
=0A=
I'm not sure how useful it is, though. In the specific case of the host=0A=
list issues, the only meaningful thing I can say is that "sometimes the=0A=
fileserver crashes". It's not really possible for you to know how=0A=
susceptible you are to it (unless you get hit by it), because the=0A=
circumstances required to trigger the crash are rather complex, and they=0A=
involve access patterns of clients that you generally cannot control or=0A=
even detect.=0A=
=0A=
> > It's open source, etc. On the other hand, it's not acceptable to=0A=
> > blindly upgrade to the latest stable release every time it comes=0A=
> > out. I understand that the most obvious take-away is just, "You got=0A=
> > bit. Move on.", but if anything can improve on our end, I'd like to=0A=
> > do that.=0A=
=0A=
Perhaps not right when it comes out, but it can be a good idea to move=0A=
towards them, depending on how you do your risk/change management.=0A=
Waiting a bit after each stable release for production machines makes=0A=
sense, to see if unknown issues crop up, but if there are significant=0A=
issues, you will hear about it if you are paying attention (probably in=0A=
the form of a new release, fixing the issue).=0A=
=0A=
1.4.12 was released almost a year ago, and I don't think there are any=0A=
significant problems besides the issues that caused 1.4.14 to be=0A=
released. There are some smaller issues here and there that sometimes=0A=
get hit, but there's no fix on the 1.4.x branch for 1.4.12 that would=0A=
cause me to recommend rolling back to pre-1.4.12 if you had upgraded a=0A=
machine to 1.4.12.=0A=
=0A=
--=0A=
Andrew Deason=0A=
adeason@sinenomine.net=0A=
=0A=
=0A=
--__--__--=0A=
=0A=
Message: 4=0A=
From: Chris Jones <christopher.rob.jones@cern.ch>=0A=
Date: Tue, 1 Feb 2011 22:57:40 +0000=0A=
Cc: <openafs-info@openafs.org>=0A=
To: Brandon S Allbery KF8NH <allbery.b@gmail.com>=0A=
Subject: Re: [OpenAFS] Status of OS X 10.6 64bit kernel support ?=0A=
=0A=
=0A=
On 1 Feb 2011, at 5:31am, Brandon S Allbery KF8NH wrote:=0A=
=0A=
> -----BEGIN PGP SIGNED MESSAGE-----=0A=
> Hash: SHA1=0A=
>=3D20=0A=
> On 2/1/11 00:26 , Derrick Brashear wrote:=0A=
>> On Fri, Jan 21, 2011 at 9:41 AM, Chris Jones =3D=0A=
<jonesc@hep.phy.cam.ac.uk> wrote:=0A=
>>> I need to run the 64bit kernel, as have updated my MacBook Pro to =3D=
=0A=
8GB ram,=0A=
>>> and I need to run the 64 bit kernel to properly support this. AFS is =
=3D=0A=
so slow=0A=
>=3D20=0A=
> Coming in a bit late: is the 64-bit kernel really necessary? I've =3D=
=0A=
been=0A=
> running an iMac with 16GB using the 32-bit kernel; no doubt there's =3D=
=0A=
some=0A=
> memory wastage due to 1MB pages but not really noticeable in practice.=0A=
=0A=
Interesting side question. I was lead to believe my late 2008 MBPro =3D=0A=
(which according Apple doesn't support more than 4GB) needs the 64 bit =3D=
=0A=
kernel to run with more. I haven't tried though.=0A=
=0A=
That said, I don't think if it is or is not necessary is really that =3D=0A=
relevant. Running the 64 bit kernel has other performance benefits, so =3D=
=0A=
is desirable. Also I believe the latest Mac Pros now use the 64 bit =3D=0A=
kernel by default... The 64 bit kernel is the way of the future, so I =3D=
=0A=
think it best OpenAFS works out any niggles it has with it as soon as it =
=3D=0A=
can ... Just my opinion ...=0A=
=0A=
cheers Chris=3D=0A=
=0A=
--__--__--=0A=
=0A=
Message: 5=0A=
From: Chris Jones <christopher.rob.jones@cern.ch>=0A=
Date: Tue, 1 Feb 2011 23:01:16 +0000=0A=
To: openafs Info <openafs-info@openafs.org>=0A=
Subject: Re: [OpenAFS] Status of OS X 10.6 64bit kernel support ?=0A=
=0A=
=0A=
> Also I believe the latest Mac Pros now use the 64 bit kernel by =3D=0A=
default...=0A=
=0A=
See=0A=
=0A=
http://support.apple.com/kb/ht3770=0A=
=0A=
The 64 bit kernel is clearly the way things are going, so needs proper =3D=
=0A=
support.=0A=
=0A=
Chris=3D=0A=
=0A=
--__--__--=0A=
=0A=
Message: 6=0A=
From: rosatrancoso <rosatrancoso@gmail.com>=0A=
Date: Wed, 2 Feb 2011 13:21:24 +0000=0A=
To: openafs-info@openafs.org=0A=
Subject: [OpenAFS] openafs on suse 10.2 with kernel 2.6.18.2-34-default=0A=
=0A=
--90e6ba6e82a8c6b03e049b4c8721=0A=
Content-Type: text/plain; charset=3DISO-8859-1=0A=
=0A=
Hello!=0A=
=0A=
I am trying to install openafs in machines with:=0A=
=0A=
cat /etc/SuSE-release: openSUSE 10.2 (X86-64)=0A=
uname -r : 2.6.18.2-34-default=0A=
=0A=
I need to install openafs-client (which needs openafs) and openafs-krb5-mit=
.=0A=
=0A=
Everything installs OK but when I try to activate the service, it says that=
=0A=
openafs-client is not installed.=0A=
Why?=0A=
Do I need to install openafs-kmp-default? The problem with this is that the=
=0A=
available version of this rpm is not compatible with my kernel (2.6.18=0A=
versus=0A=
http://download.opensuse.org/repositories/filesystems/SLE_10/x86_64/openafs=
-kmp-default-1.4.12.1_2.6.16.46_0.12-11.1.x86_64.rpm)=0A=
I don't want to update the kernel as my machine has very important services=
=0A=
running,..=0A=
=0A=
So, what can I do? Compile openafs-kernel-source? Are there any other rpm's=
?=0A=
=0A=
Thank you=0A=
Rosa=0A=
=0A=
--90e6ba6e82a8c6b03e049b4c8721=0A=
Content-Type: text/html; charset=3DISO-8859-1=0A=
Content-Transfer-Encoding: quoted-printable=0A=
=0A=
Hello!<br><br>I am trying to install openafs in machines with:<br><br>cat /=
=3D=0A=
etc/SuSE-release: openSUSE 10.2 (X86-64)<br>uname -r : 2.6.18.2-34-default<=
=3D=0A=
br><br>I need to install openafs-client (which needs openafs) and openafs-k=
=3D=0A=
rb5-mit. <br>=0A=
=0A=
=0A=
Everything installs OK but when I try to activate the service, it says that=
=3D=0A=
openafs-client is not installed. <br>Why?<br>Do I need to install openafs-=
=3D=0A=
kmp-default? The problem with this is that the available version of this rp=
=3D=0A=
m is not compatible with my kernel (2.6.18 versus <a href=3D3D"http://downl=
oa=3D=0A=
d.opensuse.org/repositories/filesystems/SLE_10/x86_64/openafs-kmp-default-1=
=3D=0A=
.4.12.1_2.6.16.46_0.12-11.1.x86_64.rpm" target=3D3D"_blank">http://download=
.o=3D=0A=
pensuse.org/repositories/filesystems/SLE_10/x86_64/openafs-kmp-default-1.4.=
=3D=0A=
12.1_2.6.16.46_0.12-11.1.x86_64.rpm</a>) I don't want to update the ker=
=3D=0A=
nel as my machine has very important services running,..<br>=0A=
=0A=
=0A=
<br>So, what can I do? Compile openafs-kernel-source? Are there any other r=
=3D=0A=
pm's?<br><br>Thank you<br>Rosa<br>=0A=
=0A=
--90e6ba6e82a8c6b03e049b4c8721--=0A=
=0A=
--__--__--=0A=
=0A=
Message: 7=0A=
From: "sabah s. salih" <sabah.salih@hep.manchester.ac.uk>=0A=
To: "openafs-info@openafs.org" <openafs-info@openafs.org>=0A=
Date: Wed, 2 Feb 2011 13:59:03 +0000=0A=
Subject: [OpenAFS] RE: OpenAFS-info digest, Vol 1 #5201 - 10 msgs=0A=
=0A=
Dear All,=3D0A=3D=0A=
Does anyone know how to fix cache manager problem?=3D0A=3D=0A=
=3D0A=3D=0A=
When I do the following=3D0A=3D=0A=
=3D0A=3D=0A=
udebug afs1.hep.man.ac.uk 7001=3D0A=3D=0A=
udebug afs2.hep.man.ac.uk 7001 =3D0A=3D=0A=
udebug afs3.hep.man.ac.uk 7001=3D0A=3D=0A=
=3D0A=3D=0A=
I do not get an answer=3D0A=3D=0A=
=3D0A=3D=0A=
Many Thanks, Sabah.=3D0A=3D=0A=
=3D0A=3D=0A=
=3D0A=3D=0A=
>From Sabah Salih=3D0A=3D=0A=
The School of Physics and Astronomy,=3D0A=3D=0A=
The University of Manchester,=3D0A=3D=0A=
Schuster Laboratory,=3D0A=3D=0A=
Brunswick Street,=3D0A=3D=0A=
Manchester M13 9PL.=3D0A=3D=0A=
Tel: +44 1612754171 or x4171=3D0A=3D=0A=
E-mail: sabah.salih@hep.manchester.ac.uk=3D=0A=
=0A=
--__--__--=0A=
=0A=
Message: 8=0A=
From: "sabah s. salih" <sabah.salih@hep.manchester.ac.uk>=0A=
To: "openafs-info@openafs.org" <openafs-info@openafs.org>=0A=
Date: Wed, 2 Feb 2011 14:07:10 +0000=0A=
Subject: [OpenAFS] can not access to users home area=0A=
=0A=
Dear All,=3D0A=3D=0A=
Does anyone know how to fix cache manager problem?=3D0A=3D=0A=
=3D0A=3D=0A=
When I do the following=3D0A=3D=0A=
=3D0A=3D=0A=
udebug afs1.hep.man.ac.uk 7001=3D0A=3D=0A=
udebug afs2.hep.man.ac.uk 7001=3D0A=3D=0A=
udebug afs3.hep.man.ac.uk 7001=3D0A=3D=0A=
=3D0A=3D=0A=
I do not get an answer=3D0A=3D=0A=
=3D0A=3D=0A=
RX debug give an answer=3D0A=3D=0A=
=3D0A=3D=0A=
rxdebug afs1.hep.man.ac.uk 7001=3D0A=3D=0A=
Trying 194.36.2.3 (port 7001):=3D0A=3D=0A=
Free packets: 130, packet reclaims: 0, calls: 0, used FDs: 64=3D0A=3D=0A=
not waiting for packets.=3D0A=3D=0A=
0 calls waiting for a thread=3D0A=3D=0A=
1 threads are idle=3D0A=3D=0A=
Done.=3D0A=3D=0A=
=3D0A=3D=0A=
rxdebug afs2.hep.man.ac.uk 7001=3D0A=3D=0A=
Trying 194.36.2.4 (port 7001):=3D0A=3D=0A=
Free packets: 130, packet reclaims: 0, calls: 569, used FDs: 64=3D0A=3D=0A=
not waiting for packets.=3D0A=3D=0A=
0 calls waiting for a thread=3D0A=3D=0A=
1 threads are idle=3D0A=3D=0A=
Done.=3D0A=3D=0A=
=3D0A=3D=0A=
rxdebug afs3.hep.man.ac.uk 7001=3D0A=3D=0A=
Trying 194.36.2.5 (port 7001):=3D0A=3D=0A=
Free packets: 130, packet reclaims: 0, calls: 187, used FDs: 64=3D0A=3D=0A=
not waiting for packets.=3D0A=3D=0A=
0 calls waiting for a thread=3D0A=3D=0A=
1 threads are idle=3D0A=3D=0A=
Done.=3D0A=3D=0A=
=3D0A=3D=0A=
=3D0A=3D=0A=
=3D0A=3D=0A=
=3D0A=3D=0A=
.=3D0A=3D=0A=
.=3D0A=3D=0A=
.=3D0A=3D=0A=
.=3D0A=3D=0A=
=3D0A=3D=0A=
=3D0A=3D=0A=
Many Thanks, Sabah.=3D0A=3D=0A=
=3D0A=3D=0A=
=3D0A=3D=0A=
>From Sabah Salih=3D0A=3D=0A=
The School of Physics and Astronomy,=3D0A=3D=0A=
The University of Manchester,=3D0A=3D=0A=
Schuster Laboratory,=3D0A=3D=0A=
Brunswick Street,=3D0A=3D=0A=
Manchester M13 9PL.=3D0A=3D=0A=
Tel: +44 1612754171 or x4171=3D0A=3D=0A=
E-mail: sabah.salih@hep.manchester.ac.uk=3D0A=3D=0A=
=0A=
--__--__--=0A=
=0A=
Message: 9=0A=
Date: Wed, 2 Feb 2011 09:09:03 -0500=0A=
From: Derrick Brashear <shadow@gmail.com>=0A=
To: "sabah s. salih" <sabah.salih@hep.manchester.ac.uk>=0A=
Cc: "openafs-info@openafs.org" <openafs-info@openafs.org>=0A=
Subject: Re: [OpenAFS] can not access to users home area=0A=
=0A=
On Wed, Feb 2, 2011 at 9:07 AM, sabah s. salih=0A=
<sabah.salih@hep.manchester.ac.uk> wrote:=0A=
> =3DA0Dear All,=0A=
> =3DA0 =3DA0 =3DA0 =3DA0 =3DA0 =3DA0Does anyone know how to fix cache mana=
ger problem?=0A=
>=0A=
> =3DA0When I do the following=0A=
>=0A=
> udebug afs1.hep.man.ac.uk 7001=0A=
> udebug afs2.hep.man.ac.uk 7001=0A=
> udebug afs3.hep.man.ac.uk 7001=0A=
>=0A=
> =3DA0I do not get an answer=0A=
=0A=
perhaps you mean cmdebug?=0A=
=0A=
> =3DA0RX debug give an answer=0A=
>=0A=
> rxdebug afs1.hep.man.ac.uk 7001=0A=
> Trying 194.36.2.3 (port 7001):=0A=
> Free packets: 130, packet reclaims: 0, calls: 0, used FDs: 64=0A=
> not waiting for packets.=0A=
> 0 calls waiting for a thread=0A=
> 1 threads are idle=0A=
> Done.=0A=
>=0A=
> rxdebug afs2.hep.man.ac.uk 7001=0A=
> Trying 194.36.2.4 (port 7001):=0A=
> Free packets: 130, packet reclaims: 0, calls: 569, used FDs: 64=0A=
> not waiting for packets.=0A=
> 0 calls waiting for a thread=0A=
> 1 threads are idle=0A=
> Done.=0A=
>=0A=
> rxdebug afs3.hep.man.ac.uk 7001=0A=
> Trying 194.36.2.5 (port 7001):=0A=
> Free packets: 130, packet reclaims: 0, calls: 187, used FDs: 64=0A=
> not waiting for packets.=0A=
> 0 calls waiting for a thread=0A=
> 1 threads are idle=0A=
> Done.=0A=
=0A=
what problem are you trying to solve?=0A=
=0A=
=0A=
--__--__--=0A=
=0A=
_______________________________________________=0A=
OpenAFS-info mailing list=0A=
OpenAFS-info@openafs.org=0A=
https://lists.openafs.org/mailman/listinfo/openafs-info=0A=
=0A=
=0A=
End of OpenAFS-info Digest=0A=