[OpenAFS] Non-functional fileserver

2024-07-11 Thread Stephan Wonczak 

  Dear all,
  Sorry for the longish post, but I wanted to provide a bit of 
background.
  Today we had a strange problem with two of our test-AFS-Servers. Apart 
from our normal cell we created two additional cells, each one consisting 
of a single server that servers as both DB-Server and Fileserver. These 
servers were created about two years back, and were working fine then. 
Yesterday we had need to test something new and we revisited the servers.

  "bos status" came back fine with "all servers running".
  However, "vos listvol -server xxx" resulted in "possible communication 
failure" Digging a bit, we had numerous log entries in VolSerLog 
"SYNC_connect: temporary failure on circuit 'FSSYNC' (will retry)". This 
pointed to the fact, that the fssync.sock socket file was missing. Indeed, 
/var/log/messages showed that the fileserver-process had dumped core 
during startup. Interestingly, though, a fileserver process -was- running, 
just not really functioning.
  Several unsuccessful hours of debugging, tracing and googling later, I 
was ready to give up and trash the test cell and create a new one from 
scratch. During the process of purging the files I thought "OK, 
/usr/afs/etc/CellServDB for this cell stays the same, so I can keep that." 
On a hunch, I actually looked what was inside: Lo and behold! The 
configured DB-server adress for the cell had the wrong IP.
  This is when I remembered that both problematic machines were moved to a 
different network segment. We had corrected the -client- CellervDB during 
that move, but forgot about the server CellServDB.

  Now, the whole point of this story:
  The logs were spectacularily unhelpful in pinpointing this 
misconfiguration. Indeed, I would not have expected the fileserver to dump 
core instead of refusing to run at all. At the very least there should be 
a log entry that no DB-Server could be reached (and CellServDB should be 
checked).

  Recreating this behaviour is easy:
  Take a working single-server cell, and change the IP in 
/usr/afs/etc/CellServDB. Restart the fileserver and watch things go south.


  Thanks for reading my long ramble :-)

Dipl. Chem. Dr. Stephan Wonczak

Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Weyertal 121, 50931 Koeln
Tel: +49/(0)221/470-89583, Fax: +49/(0)221/470-89625
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] (no subject)

2024-07-01 Thread Stephan Wonczak 

  Hello!

On Thu, 27 Jun 2024, Cheyenne Wills wrote:


It appears that the latest CentOS-9 stream has pulled in changes from
the Linux 6.8 kernel, specifically commit 'dentry: switch the lists of
children to hlist' (da549bdd15).

I will double check to see if the latest RHEL9 kernel is pulling this
in (Centos9-Stream is the beta version that eventually feeds into RHEL9)


  Sounds reasonable.


This specific problem was addressed in the upcoming 1.8.12 by gerrit
15704 "Linux 6.8: use hlist iteration for dentry children".  1.8.12
will have support for linux kernels up to and including 6.9.

I find it odd that 1.8.10 was able to build when 1.8.11 failed.  Was
the build using the same updated kernel level?


  Yes, I did the builds with the very same kernel. Especially to recheck 
whether 1.8.10 would still build.


Dipl. Chem. Dr. Stephan Wonczak

Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Weyertal 121, 50931 Koeln
Tel: +49/(0)221/470-89583, Fax: +49/(0)221/470-89625
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

[OpenAFS] (no subject)

2024-06-27 Thread Stephan Wonczak 

  Hi everyone,
  nb: For some reason my original report did not make it to 
the list. Maybe because of my attachment; are these forbidden?

  A few days ago I hit a regression while building 1.8.11 for CentOS-9.
  As an rpm was missing from the release, I created a source-RPM from the
.bz2-tarballs as per documentation and did did a rpmbuild.
  Command line used (yes, we still have need for ka...):

  rpmbuild --rebuild --with kauth openafs-1.8.11-1.src.rpm

  This worked fine on RHEL-8 (fully updated)
  That very same src.rpm has a problem building the modules on a fully
updated CentOS-9 Stream (kernel 5.14.0-457).
Last relevant lines from the build are:

(...)
./include/linux/list.h:562:9: note: in expansion of macro 'list_entry'
  562 | list_entry((pos)->member.next, typeof(*(pos)), member)
  | ^~
./include/linux/list.h:689:20: note: in expansion of macro 
'list_next_entry'

  689 |  pos = list_next_entry(pos, member))
  |^~~
/root/rpmbuild/BUILD/openafs-1.8.11/src/libafs/MODLOAD-5.14.0-457.el9.x86_64-SP/osi_vcache.c:315:13: 
note: in expansion of macro 'list_for_each_entry'

  315 | list_for_each_entry(child, >d_subdirs, d_child) {
  | ^~~
make[4]: *** [scripts/Makefile.build:268: 
/root/rpmbuild/BUILD/openafs-1.8.11/src/libafs/MODLOAD-5.14.0-457.el9.x86_64-SP/osi_vcache.o] 
Error 1

make[4]: *** Waiting for unfinished jobs
make[3]: *** [Makefile:1942: 
/root/rpmbuild/BUILD/openafs-1.8.11/src/libafs/MODLOAD-5.14.0-457.el9.x86_64-SP] 
Error 2

make[3]: Leaving directory '/usr/src/kernels/5.14.0-457.el9.x86_64'
FAILURE: make exit code 2
make[2]: *** [Makefile.afs:283: openafs.ko] Error 1
make[2]: Leaving directory 
'/root/rpmbuild/BUILD/openafs-1.8.11/src/libafs/MODLOAD-5.14.0-457.el9.x86_64-SP'

make[1]: *** [Makefile:188: linux_compdirs] Error 2
make[1]: Leaving directory 
'/root/rpmbuild/BUILD/openafs-1.8.11/src/libafs'

make: *** [Makefile:463: libafs] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.ZUYDKT (%build)

  Full build log available on request.
  A few more data points:

- Building with "rpmbuild --rebuild --with kauth --define "build_modules 
0" works fine and creates RPMs.

- Builing 1.8.10 on that machine works fine (checked today)
- Building 1.8.12pre1 on that machine works fine, too.

  So only the released version of 1.8.11 is broken on CentOS-9 stream, and
I suspect on RHEL-9, too.

    Dipl. Chem. Dr. Stephan Wonczak

Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Weyertal 121, 50931 Koeln
Tel: +49/(0)221/470-89583, Fax: +49/(0)221/470-89625
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] How to replace pam_krb5 on RHEL 8 systems

2022-07-14 Thread Stephan Wonczak 
  (minikafs_5settoken2(cell, new_creds, uid) == 
0)) {

krb5_free_creds(ctx, new_creds);
v5_free_unparsed_name(ctx, 
unparsed_client);

krb5_free_principal(ctx, client);
krb5_free_principal(ctx, server);
return 0;
} else
if (use_v5_2b &&
(minikafs_5settoken(cell, new_creds, uid) == 
0)) {

krb5_free_creds(ctx, new_creds);
v5_free_unparsed_name(ctx, 
unparsed_client);

krb5_free_principal(ctx, client);
krb5_free_principal(ctx, server);
return 0;
}
krb5_free_creds(ctx, new_creds);
} else {
if (options->debug) {
if (etypes != NULL) {
debug("error obtaining credentials 
for "
  "'%s' (enctype=%d) on behalf 
of "

  "'%s': %s",
  principal, etypes[i],
  unparsed_client,
  v5_error_message(tmp));
} else {
   	debug("error obtaining credentials 
for "

  "'%s' on behalf of "
  "'%s': %s",
  principal,
  unparsed_client,
  v5_error_message(tmp));
        }
}
}
}

v5_free_unparsed_name(ctx, unparsed_client);
krb5_free_principal(ctx, client);
krb5_free_principal(ctx, server);

  If you or anyone else has any ideas how to tackle the problem, any help 
would be greatly appreciated.


  Cheers from Cologne,
  Stephan Wonczak


On Fri, 8 Jul 2022, Jeffrey E Altman wrote:



Sounds like the version of pam_krb5 you are attempting to build does not
include support for rxkad-kdf.

 https://lists.openafs.org/pipermail/afs3-standardization/2013-July/002738.h
tml

The version of pam_krb5 that supports rxkad-kdf contains a
minikafs_kd_derive() function at minikafs.c line 775.

See https://github.com/frozencemetery/pam_krb5.

As mentioned in my prior reply pam_krb5 should not be used in conjunction
with sssd.

Jeffrey Altman

On 7/8/2022 8:35 AM, Stephan Wonczak (a0...@rrz.uni-koeln.de) wrote:
    Hi everyone!
    (Berthold's colleague here)

    We dug a little deeper and found the part in the
  pam_krb5-sources where it fails. It is in the file "minikafs.c"
  starting in line 775. It looks like the call to
  krb5_get_credentials() gets a non-zero return value, thus making
  it bail out.
    The problem is that we (well, at least me!) have no idea which
  enctype is expected, and which enctypes are actually tried.
  Debug output is not too helpful here. Any ideas on how to get
  useful information?
    (I should mention I am waaay out of depth here with my
  knowledge of Kerberos, and my C-fu is severely lacking, too ;-)
  )

    To be absolutley clear: We can ssh-login to the machine
  running this pam_krb.so-module, and get a valid krb5-ticket. No
  AFS-token after login, thus no access to AFS. If I do
  "klog.krb5", I -do- get an AFS-Token without any issues, and
  AFS-access starts working as it should.
    It's maddening that only pam_krb5 complains, while other tools
  work out of the box.

    Any advice would be greatly appreciated!

    Stephan

  On Fri, 8 Jul 2022, Berthold Cogel wrote:

Am 07.07.22 um 19:04 schrieb Dirk Heinrichs:
   Benjamin Kaduk:

 Are you aware of
pam_afs_session
 (https://github.com/rra/pam-afs-session)?
Without knowing more about
 what you're using pam_krb5
for it's hard to make
specific suggestions
 about what alternatives
might exist.


   BTW: pam_krb5 != pam_krb5. There are
  two different modules with the same
   name out there. The one shipped with
  RedHat family distributions comes
   with integrated AFS support, while the
  one shipped with Debian

Re: [OpenAFS] How to replace pam_krb5 on RHEL 8 systems

2022-07-11 Thread Stephan Wonczak 

  Hi all!
  Jeffrey pointed us in the right direction - and most useful, a reason 
why it failed for us. Kudos to Jeffrey, as always!
  Since we won't touch SSSD with a 10-yard-stick, we gave 
pam_afs_session.so a spin. And lo and behold: It really worked!


  We have the following in our password-auth:

(...)
authsufficientpam_krb5.so forward_pass ignore_afs=true
authrequired  pam_afs_session.so program=/usr/bin/aklog
authrequired  pam_deny.so

(...)
session optional  pam_krb5.so ignore_afs=true
session required  pam_afs_session.so program=/usr/bin/aklog

  Still needs a bit more testing, but now AFS-Login is working and no sssd 
in sight ;-) Might be useful to others with a similar problem.


  Cheers from Cologne,
  Stephan

On Mon, 11 Jul 2022, Dave Botsch wrote:


I wanted to mention that we are successfully doing ssh and gnome-shell
logins with pam_sssd where sssd takes care of authN via kerberos and via
ldap provides group information, and pam_afs_session to get afs tokens.

Two difficulties... if using PAGSHs, not all processes run inside a
pagsh, which can break gnome-shell stuff. So not using PAGsh is
recommended.

and with systemd_login, it and subprocesses don't necessarily quit on
logout. Which means they are sitting there banging away against afs with
no tokens (if you use afs homedirs). There is an option to force
systemd_login to quit at logout, though this breaks the use of things
like screen and tmux, iirc.

I'm happy to provide our configs (we worked with RedHat support to get
sssd working properly migrating from nslcd and pam_krb5 on rhel6).

thanks


On Sat, Jul 09, 2022 at 10:06:06AM -0400, Ken Hornstein wrote:

Only if you let sssd touch Kerberos. There are any number of reasons not
to let it do so (no clue if the KRB5 and LDAP problems are fixed in
later versions, but the EL8 code was written by crazed weasels on
crack). But I'd use Russ' pam_krb5 instead of one from EL7
(https://www.eyrie.org/~eagle/software/pam-krb5/pam-krb5.html), which
would probably require you use pam_afs_session as suggested (unless I'm
missing something in the docs, which is very possible).


I guess this explains why when everyone talks about the Kerberos issues
they have on RHEL systems, I'm like ¯\_(ツ)_/¯, because we don't let sssd
anywhere near Kerberos and it sounds like that's a bad idea (at least
for the things we want to do).

--Ken
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info


--

David William Botsch
Programmer/Analyst
@CornellCNF
bot...@cnf.cornell.edu

___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info



Dipl. Chem. Dr. Stephan Wonczak

Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Weyertal 121, 50931 Koeln
Tel: +49/(0)221/470-89583, Fax: +49/(0)221/470-89625

Re: [OpenAFS] How to replace pam_krb5 on RHEL 8 systems (fwd)

2022-07-11 Thread Stephan Wonczak 
if (use_rxk5 &&
(minikafs_5settoken2(cell, new_creds, uid) == 0)) {
krb5_free_creds(ctx, new_creds);
v5_free_unparsed_name(ctx, unparsed_client);
 krb5_free_principal(ctx, client);
 krb5_free_principal(ctx, server);
 return 0;
 } else
 if (use_v5_2b &&
(minikafs_5settoken(cell, new_creds, uid) == 0)) {
 krb5_free_creds(ctx, new_creds);
 v5_free_unparsed_name(ctx, 
unparsed_client);

 krb5_free_principal(ctx, client);
 krb5_free_principal(ctx, server);
return 0;
 }
 krb5_free_creds(ctx, new_creds);
 } else {
 if (options->debug) {
 if (etypes != NULL) {
debug("error obtaining credentials for 
"

  "'%s' (enctype=%d) on behalf of "
   "'%s': %s",
   principal, etypes[i],
   unparsed_client,
   v5_error_message(tmp));
 } else {
   	debug("error obtaining credentials for 
"

   "'%s' on behalf of "
   "'%s': %s",
   principal,
   unparsed_client,
   v5_error_message(tmp));
     }
     }
 }
 }

 v5_free_unparsed_name(ctx, unparsed_client);
 krb5_free_principal(ctx, client);
 krb5_free_principal(ctx, server);

  If you or anyone else has any ideas how to tackle the problem, any help would 
be greatly appreciated.


   Cheers from Cologne,
   Stephan Wonczak


On Fri, 8 Jul 2022, Jeffrey E Altman wrote:



 Sounds like the version of pam_krb5 you are attempting to build does not
 include support for rxkad-kdf.

  https://lists.openafs.org/pipermail/afs3-standardization/2013-July/002738.h
 tml

 The version of pam_krb5 that supports rxkad-kdf contains a
 minikafs_kd_derive() function at minikafs.c line 775.

 See https://github.com/frozencemetery/pam_krb5.

 As mentioned in my prior reply pam_krb5 should not be used in conjunction
 with sssd.

 Jeffrey Altman

 On 7/8/2022 8:35 AM, Stephan Wonczak (a0...@rrz.uni-koeln.de) wrote:
     Hi everyone!
     (Berthold's colleague here)

     We dug a little deeper and found the part in the
   pam_krb5-sources where it fails. It is in the file "minikafs.c"
   starting in line 775. It looks like the call to
   krb5_get_credentials() gets a non-zero return value, thus making
   it bail out.
     The problem is that we (well, at least me!) have no idea which
   enctype is expected, and which enctypes are actually tried.
   Debug output is not too helpful here. Any ideas on how to get
   useful information?
     (I should mention I am waaay out of depth here with my
   knowledge of Kerberos, and my C-fu is severely lacking, too ;-)
  ) 


     To be absolutley clear: We can ssh-login to the machine
   running this pam_krb.so-module, and get a valid krb5-ticket. No
   AFS-token after login, thus no access to AFS. If I do
   "klog.krb5", I -do- get an AFS-Token without any issues, and
   AFS-access starts working as it should.
     It's maddening that only pam_krb5 complains, while other tools
   work out of the box.

     Any advice would be greatly appreciated!

     Stephan

   On Fri, 8 Jul 2022, Berthold Cogel wrote:

 Am 07.07.22 um 19:04 schrieb Dirk Heinrichs:
    Benjamin Kaduk:

  Are you aware of
 pam_afs_session
  (https://github.com/rra/pam-afs-session)?
 Without knowing more about
  what you're using pam_krb5
 for it's hard to make
 specific suggestions
  about what alternatives
 might exist.


    BTW: pam_krb5 != pam_krb5. There are
   two different modules with the same
    name out there.

Re: [OpenAFS] How to replace pam_krb5 on RHEL 8 systems

2022-07-08 Thread Stephan Wonczak 

  Hi everyone!
  (Berthold's colleague here)

  We dug a little deeper and found the part in the pam_krb5-sources where 
it fails. It is in the file "minikafs.c" starting in line 775. It looks 
like the call to krb5_get_credentials() gets a non-zero return value, thus 
making it bail out.
  The problem is that we (well, at least me!) have no idea which enctype 
is expected, and which enctypes are actually tried. Debug output is not 
too helpful here. Any ideas on how to get useful information?
  (I should mention I am waaay out of depth here with my knowledge of 
Kerberos, and my C-fu is severely lacking, too ;-) )


  To be absolutley clear: We can ssh-login to the machine running this 
pam_krb.so-module, and get a valid krb5-ticket. No AFS-token after login, 
thus no access to AFS. If I do "klog.krb5", I -do- get an AFS-Token 
without any issues, and AFS-access starts working as it should.
  It's maddening that only pam_krb5 complains, while other tools work 
out of the box.


  Any advice would be greatly appreciated!

  Stephan

On Fri, 8 Jul 2022, Berthold Cogel wrote:


Am 07.07.22 um 19:04 schrieb Dirk Heinrichs:

 Benjamin Kaduk:


 Are you aware of pam_afs_session
 (https://github.com/rra/pam-afs-session)? Without knowing more about
 what you're using pam_krb5 for it's hard to make specific suggestions
 about what alternatives might exist.


 BTW: pam_krb5 != pam_krb5. There are two different modules with the same
 name out there. The one shipped with RedHat family distributions comes
 with integrated AFS support, while the one shipped with Debian family
 distributions doesn't. That's the reason why Debian also ships
 pam_afs_session and RH does not.

 Bye...

      Dirk



We're using the pam_krb5 shipped with Red Hat.

I've rebuild the module from the RHEL 7 source rpm on RHEL 8. And it seems to 
work for some value of working


Supported enctypes in our kdc:
aes256-cts-hmac-sha1-96:normal des-cbc-crc:normal des:afs3

We 'rekeyed' our AFS environment with aes256-cts-hmac-sha1-96:normal to get 
connections from newer Ubuntu/Debian and Fedora 35 working.


We get a krb5 ticket and a login, but getting the AFS token gives errors:

"error obtaining credentials for 'afs/rrz.uni-koeln...@rrz.uni-koeln.de' 
(enctype=1) on behalf of : No credentials found with supported encryption 
types"


Same for two other enctypes.

So something else changed in RHEL 8, which we haven't found yet.


Regards
Berthold
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info



    Dipl. Chem. Dr. Stephan Wonczak

Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Weyertal 121, 50931 Koeln
Tel: +49/(0)221/470-89583, Fax: +49/(0)221/470-89625

Re: [OpenAFS] Strange caching failures

2013-03-01 Thread Stephan Wonczak 

  Hi Russ!

On Thu, 28 Feb 2013, Russ Allbery wrote:


Stephan Wonczak a0...@rrz.uni-koeln.de writes:


  for the past few weeks, we are struck with a very weird behavior
regarding cache updates of AFS clients. It looks like sometimes the
callback does not work and one client is stuck with an older version of
the file in question. Example:



  Write to file 'foo' on client A every five minutes.
  Clients B,C and D dutifully update their caches and see the updates
  After some time, suddenly Client B dows not see the updates any more,
while clients C and D continue working fine.


When this happens, does the write to the file on client A block for a few
seconds?


  Very difficult to say since the behavior is so non-deterministic.
  What my colleague did was to write a cronjob on one machine (client 
version 1.4.11) to write to a short status file every five minutes, and 
subsequently do a 'ls -l' on several other clients (both 1.4 and 1.6).
  So far it *looks* like it is only the 1.6.x-clients that stop updating, 
but for this specific file it takes between 4 and 12 hours for the effect 
to show up.


Dipl. Chem. Dr. Stephan Wonczak

Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Weyertal 121, 50931 Koeln
Tel: +49/(0)221/470-89583, Fax: +49/(0)221/470-89625
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

[OpenAFS] Strange caching failures

2013-02-28 Thread Stephan Wonczak 

  Hi all!
  for the past few weeks, we are struck with a very weird behavior 
regarding cache updates of AFS clients. It looks like sometimes the 
callback does not work and one client is stuck with an older version of 
the file in question. Example:


  Write to file 'foo' on client A every five minutes.
  Clients B,C and D dutifully update their caches and see the updates
  After some time, suddenly Client B dows not see the updates any more, 
while clients C and D continue working fine.

  A 'fs flush foo' on client B corrects the problem.
  Other files are *NOT* affected and are updated fine on Client B.

  This behavior is not really repeatable, though, sometimes it is client D 
that stops working, or any other client.
  When taking into account that the clients I am talking about here are 
web servers, you can imagine that this behavior is less than desirable.


  Now for the versions:
  Clients are a mix of 1.4.x and 1.6.x (mainly 1.6.1-1.el5 and 1.4.12-el5, 
with other versions thrown into the mix).

  Servers are version 1.4.11-el5.
  OS on both clients and server is RHEL5

  It might be a coincidence, but we became aware of this problem shortly 
after updating a bunch of clients to 1.6.1-1.el5.


  Any ideas on how to go about debugging this?

Dipl. Chem. Dr. Stephan Wonczak

Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Weyertal 121, 50931 Koeln
Tel: +49/(0)221/470-89583, Fax: +49/(0)221/470-89625
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Strange caching failures

2013-02-28 Thread Stephan Wonczak 

  Hi Derrick!

On Thu, 28 Feb 2013, Derrick Brashear wrote:

start with FileLog on the fileserver and see what errors for B (or D 
or...) at around the time it breaks.


  Unfortunately nothing jumps out. A colleague managed to pinpoint a 
failure to a period of five minutes, but nothing was logged on the 
fileserver. The only remotely suspicious message(s) are of the type


Feb 28 14:45:03 vmfs05 fileserver[4346]: FindClient: stillborn client 
ac460e20(e8d98fa0); conn ac406ba0 (host XX.XX.XX.XX:7001) had client 
a718bf0(e8d98fa0)


but according to older posts this is a harmless, informative message. 
Additionally, I have seen these messages for years, and they did not 
coincide with the pinpointed incident.

  Maybe jacking up the loglevel might help?

  Stephan



Derrick


On Feb 28, 2013, at 9:39, Stephan Wonczak a0...@rrz.uni-koeln.de wrote:


 Hi all!
 for the past few weeks, we are struck with a very weird behavior regarding 
cache updates of AFS clients. It looks like sometimes the callback does not 
work and one client is stuck with an older version of the file in question. 
Example:

 Write to file 'foo' on client A every five minutes.
 Clients B,C and D dutifully update their caches and see the updates
 After some time, suddenly Client B dows not see the updates any more, while 
clients C and D continue working fine.
 A 'fs flush foo' on client B corrects the problem.
 Other files are *NOT* affected and are updated fine on Client B.

 This behavior is not really repeatable, though, sometimes it is client D that 
stops working, or any other client.
 When taking into account that the clients I am talking about here are web 
servers, you can imagine that this behavior is less than desirable.

 Now for the versions:
 Clients are a mix of 1.4.x and 1.6.x (mainly 1.6.1-1.el5 and 1.4.12-el5, with 
other versions thrown into the mix).
 Servers are version 1.4.11-el5.
 OS on both clients and server is RHEL5

 It might be a coincidence, but we became aware of this problem shortly after 
updating a bunch of clients to 1.6.1-1.el5.

 Any ideas on how to go about debugging this?

   Dipl. Chem. Dr. Stephan Wonczak

   Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
   Universitaet zu Koeln, Weyertal 121, 50931 Koeln
   Tel: +49/(0)221/470-89583, Fax: +49/(0)221/470-89625
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info





Dipl. Chem. Dr. Stephan Wonczak

Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Weyertal 121, 50931 Koeln
Tel: +49/(0)221/470-89583, Fax: +49/(0)221/470-89625
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Volumes offlined during reclone

2009-05-26 Thread Stephan Wonczak 

  Hi Jeffrey!

On Mon, 25 May 2009, Jeffrey Altman wrote:


Stephan Wonczak wrote:

  Hi all!
  On two consecutive weekends we had volumes going offline on one of our
just-upgraded 1.4.10 fileservers. This seems to happen during the
nightly 'vos backupsys'-runs. The effect is that the 'salvage' flag is
set on one or two volumes, effectively bringing them offline.


Thanks to Derrick this is fixed by

http://www.openafs.org/cgi-bin/wdelta/openafs-stable-1_4_x/STABLE14-background-fsync-consistency-issues-20090522?diff


  Ah, great. So it was a bug after all. Kudos to Derrick for fixing this. 
Any idea when a fixed 1.4.11 will be available? This bug is a kind of 
showstopper for us.


Dipl. Chem. Dr. Stephan Wonczak

Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Robert-Koch-Strasse 10, 50931 Koeln
Tel: +49/(0)221/478-5577, Fax: +49/(0)221/478-5590

___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

[OpenAFS] Volumes offlined during reclone

2009-05-25 Thread Stephan Wonczak 

  Hi all!
  On two consecutive weekends we had volumes going offline on one of our 
just-upgraded 1.4.10 fileservers. This seems to happen during the nightly 
'vos backupsys'-runs. The effect is that the 'salvage' flag is set on one 
or two volumes, effectively bringing them offline.

  Here are snips from the logs

May 24 09:13:34 lvr5 volserver[6346]: VAttachVolume: volume salvage flag 
is ON for /vicepba/V0536940603.vol; volume needs salvage
May 24 09:13:34 lvr5 volserver[6346]: 1 Volser: ListVolumes: Could not 
attach volume 536940603 (/vicepba:V0536940603.vol), error=101
May 24 09:18:01 lvr5 volserver[6346]: VAttachVolume: volume salvage flag 
is ON for /vicepba/V0536940603.vol; volume needs salvage
May 24 09:18:01 lvr5 volserver[6346]: 1 Volser: ListVolumes: Could not 
attach volume 536940603 (/vicepba:V0536940603.vol), error=101
May 24 09:27:27 lvr5 volserver[6346]: VAttachVolume: volume salvage flag 
is ON for /vicepba/V0536940603.vol; volume needs salvage
May 24 09:27:27 lvr5 volserver[6346]: 1 Volser: ListVolumes: Could not 
attach volume 536940603 (/vicepba:V0536940603.vol), error=101
May 24 09:28:10 lvr5 volserver[6346]: VAttachVolume: volume salvage flag 
is ON for /vicepba/V0536940603.vol; volume needs salvage
May 24 09:28:10 lvr5 volserver[6346]: 1 Volser: ListVolumes: Could not 
attach volume 536940603 (/vicepba:V0536940603.vol), error=101
May 24 10:36:15 lvr5 volserver[6346]: VAttachVolume: volume salvage flag 
is ON for /vicepba/V0537184886.vol; volume needs salvage
May 24 10:36:15 lvr5 volserver[6346]: 1 Volser: ListVolumes: Could not 
attach volume 537184886 (/vicepba:V0537184886.vol), error=101
May 24 10:50:17 lvr5 volserver[6346]: VAttachVolume: volume salvage flag 
is ON for /vicepba/V0537184886.vol; volume needs salvage
May 24 10:50:17 lvr5 volserver[6346]: 1 Volser: ListVolumes: Could not 
attach volume 537184886 (/vicepba:V0537184886.vol), error=101


and FileLog:
May 24 07:05:01 lvr5 fileserver[6344]: Volume 537184886 now offline, must 
be salvaged.

May 24 07:05:32 lvr5 last message repeated 242 times
May 24 07:05:32 lvr5 last message repeated 3 times
May 24 07:05:33 lvr5 fileserver[6344]: VAttachVolume: volume salvage flag 
is ON for /vicepba//V0537184886.vol; volume needs salvage

snip
May 24 07:20:50 lvr5 fileserver[6344]: Volume 536940603 now offline, must 
be salvaged.

May 24 07:20:50 lvr5 last message repeated 2 times
May 24 07:21:39 lvr5 fileserver[6344]: VAttachVolume: volume salvage flag 
is ON for /vicepba//V0536940603.vol; volume needs salvage

snip
May 24 09:13:34 lvr5 fileserver[6344]: VAttachVolume: volume salvage flag 
is ON for /vicepba//V0536940603.vol; volume needs salvage
May 24 09:18:01 lvr5 fileserver[6344]: VAttachVolume: volume salvage flag 
is ON for /vicepba//V0536940603.vol; volume needs salvage
May 24 09:27:27 lvr5 fileserver[6344]: VAttachVolume: volume salvage flag 
is ON for /vicepba//V0536940603.vol; volume needs salvage
May 24 09:28:10 lvr5 fileserver[6344]: VAttachVolume: volume salvage flag 
is ON for /vicepba//V0536940603.vol; volume needs salvage


(full logs are available on request). The two volumes affected are named 
'v.www.projekt' and 'c.smail.data', respectively.
  What I find most surprising is the time when the volumes are set 
offline, since the backupsys-run happens several hours earlier (excerpt 
from BosConfig):


bnode cron backupvolwww 1
parm /usr/afs/bin/vos backupsys -prefix v.www -localauth
parm 20:00
end

  There are 170 Volumes in this set and they are all finished by 20:00:56, 
i.e. in less than one minute, without any errors whatsoever.

  Any ideas what could be happening here?


Dipl. Chem. Dr. Stephan Wonczak

Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Robert-Koch-Strasse 10, 50931 Koeln
Tel: +49/(0)221/478-5577, Fax: +49/(0)221/478-5590

___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Serious trouble, mounting /afs, ptserver, database rebuilding

2008-07-29 Thread Stephan Wonczak 

  Hi Kanou!

On Sun, 27 Jul 2008, kanou wrote:

snip

Don't be so unpatient, your reluctance to give proper information

I'm sorry and I thought I was giving you all the information I found.


First of all, 2 database-servers are a really bad idea.

Allright. I will change that.


After that, go to your boss and ask for a third database-server.

I did and I will install a third one.


  While more redundancy (i.e. a third database server) is always a good 
idea, it is not strictly necessary, much less 'a bad idea to run with two 
database servers'.
  Christof probably was thinking about the 'split brain' problem, which 
does not come into play with the AFS architecture; we are proof against 
that one. I made a posting about this a while ago; it should be in the 
archives.


Dipl. Chem. Dr. Stephan Wonczak

Zentrum fuer Angewandte Informatik (ZAIK)
Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Robert-Koch-Strasse 10, 50931 Koeln
Tel: ++49/(0)221/478-5577, Fax: ++49/(0)221/478-5590

___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Serious trouble, mounting /afs, ptserver, database rebuilding

2008-07-29 Thread Stephan Wonczak 

  Hi Brandon!

On Tue, 29 Jul 2008, Brandon S. Allbery KF8NH wrote:



On 2008 Jul 29, at 3:44, Stephan Wonczak wrote:

While more redundancy (i.e. a third database server) is always a good idea, 
it is not strictly necessary, much less 'a bad idea to run with two 
database servers'.
Christof probably was thinking about the 'split brain' problem, which does 
not come into play with the AFS architecture; we are proof against that 
one. I made a posting about this a while ago; it should be in the archives.



Actually he's thinking about a screw condition that used to happen with 
voting for a sync site if you have 2 database servers and the 
lower-IP-numbered one goes missing.  I *think* it has been fixed now.


  Not really a bug. If the lowest numbered DB server goes AWOL the 
remaining server has no chance to become master. I cannot distinguish 
(without human help) wether there is a simple communication problem or if 
the lower server really is down. So it stays in RO-Mode, as it should.
  As an admin you then have the choice to go back to a single-server 
scenario, or bring the other one back online. I do agree however that this 
is not too nice, and you are probably better off with three DB servers.


Dipl. Chem. Dr. Stephan Wonczak

Zentrum fuer Angewandte Informatik (ZAIK)
Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Robert-Koch-Strasse 10, 50931 Koeln
Tel: ++49/(0)221/478-5577, Fax: ++49/(0)221/478-5590

___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] no quorum elected

2008-06-03 Thread Stephan Wonczak 

  Hi Robert!

On Mon, 2 Jun 2008, Robert Banz wrote:



On Jun 2, 2008, at 11:30 PM, TIARA System Man wrote:

thank you russ.. i just check my CellServDB files on each file server. i 
just found one has wrong db info in the file. :$




it's generally good to have at least three DB servers (an odd number is 
important!). The two most common causes of the quorum error are not having a 
majority of the DB servers available, or, having a time split between them.


File it away for future reference!


  This, of course, is wrong in the case of AFS DB-Servers. The 
master-server (usually the one with the lowest IP) has an additional 
half-vote. So no split-brain possible here.
  If you have 2 servers, and connection is severed, you have 1.5 votes on 
one side, and 1 on the other. Since the cluster knows there are supposed 
to be 2.5 votes in total, the single slave server will refuse to accept 
changes (while happily continuing to serve requests with older data)
  In the case of 4 servers (which we have in Cologne) you will get the 
exact same scenarion, only with 2.5 to 2.0 votes. If only the master 
server is isolated you get 1.5 to 3.0 votes. This will result in the three 
still connected servers voting for a new master, and the old master will 
stop accepting changes since it knows that it is in the minority in this 
situation.


  Cheers from Cologne,

Dipl. Chem. Dr. Stephan Wonczak

Zentrum fuer Angewandte Informatik (ZAIK)
Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Robert-Koch-Strasse 10, 50931 Koeln
Tel: ++49/(0)221/478-5577, Fax: ++49/(0)221/478-5590

___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Changing reserved block on ext3 with fs running

2005-10-06 Thread Stephan Wonczak 
  Hi!

On Wed, 5 Oct 2005, Tim Spriggs wrote:

 Isn't there something about needing a small percentage of space to be able
 to keep the ext3/ext2 filesystem from fragmenting too much? Does this
 apply here?

  Not that I know of. Even so, 25 GB on a 500 GB filesystem is a bit
excessive, wouldn't you agree? I had intended to leave 1 blocks
reserved (makes 40 MB) to give root some breathing room.
  But I still would like a comment from someone knowledgable if it is safe
to change the number of reserved blocks while the fileserver is running.
(Anyone, please ... *whine* :-) )

 Also, is there a problem with running on ext3? I only ask because I know
 openafs can not use journaling filesystems under Solaris.

  ext3 works fine. We have about 10 TB online currently, and we are using
ext3 for about two years without any trouble. IIRC ext3 is a supported FS.
We also used XFS for the vice partitions and this also worked fine.

  I remeber some issues with Solaris UFS, some semantics changes IIRC.
There was a bit of discussion about that a while back, but I don't
remember the details.


Dipl. Chem. Dr. Stephan Wonczak

Zentrum fuer Angewandte Informatik (ZAIK)
Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Robert-Koch-Strasse 10, 50931 Koeln
Tel: ++49/(0)221/478-5577, Fax: ++49/(0)221/478-5590


___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Changing reserved block on ext3 with fs running

2005-10-05 Thread Stephan Wonczak 
  Hi!

On Wed, 5 Oct 2005, Frank Burkhardt wrote:

snip
Now the question: Are there any repercussions when changing the number
  of reserved blocks in this way, or are there any subtle side effects on
  the fileserver?

 AFAIK there should be no problem using 'tune2fs -r' or 'tune2fs -m' on
 a mounted filesystem (I just tried it).

  'Should' is a word we are very reluctant to use in a production
environment :-)

 But you most probably needn't do that. The reserved blocks are only
 accessible to a given user (see 'tune2fs -l /dev/ice | grep uid') when the
 limit is reached. But this given user is root by default and AFS-Fileservers
 are running as root. Reserved blocks simply don't matter in this case.

  Well, in principle you are correct. But the fileserver seems to use only
the non-reserved blocks (you can check this with vos partinfo). So the fs
will report 'no space left' even if the reserved blocks are available.
There is nothing wrong with this behavior, actually this is correct as far
as I am concerned (this way root has a chance of some cleanup even if the
fs started to scribble like mad).
  So the question remains: Any nasty sideffects on changing the number of
reserved blocks and thus the usable capacity of a vice partition while the
fileserver is running?

Dipl. Chem. Dr. Stephan Wonczak

Zentrum fuer Angewandte Informatik (ZAIK)
Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Robert-Koch-Strasse 10, 50931 Koeln
Tel: ++49/(0)221/478-5577, Fax: ++49/(0)221/478-5590


___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

[OpenAFS] Build failure on ia64

2005-03-03 Thread Stephan Wonczak 
  Hello again!
  I am still trying to get a working openafs-client for out SGI Altix. I
just tried building 1.3.79, but still no go. The build error is a little
different from the last two times I reported (with 1.3.74 and 77):

cc -I. -I.. -I../nfs -I/service/openafs/source-1.3.79/openafs-1.3.79/src
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/afs
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/afs/LINUX
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/config
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rx/LINUX
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rxkad
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rxkad/domestic
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/util
-I/service/openafs/source-1.3.79/openafs-1.3.79/src
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/afs
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/afs/LINUX
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/util
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rxkad
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/config
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/fsint
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/vlserver
-I/service/openafs/source-1.3.79/openafs-1.3.79/include
-I/service/openafs/source-1.3.79/openafs-1.3.79/include/afs-O2
-fomit-frame-pointer -fno-strength-reduce -fno-strict-aliasing -fno-common
-pipe -ffixed-r13 -mfixed-range=f10-f15,f32-f127 -falign-functions=32
-mb-step -D__KERNEL__ -DKERNEL -D_KERNEL -DMODULE -DAFS_SMP   -I. -I../
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/config
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rx
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rxstat -c
/service/openafs/source-1.3.79/openafs-1.3.79/src/afs/LINUX/osi_sleep.c
cc -I. -I.. -I../nfs -I/service/openafs/source-1.3.79/openafs-1.3.79/src
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/afs
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/afs/LINUX
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/config
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rx/LINUX
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rxkad
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rxkad/domestic
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/util
-I/service/openafs/source-1.3.79/openafs-1.3.79/src
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/afs
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/afs/LINUX
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/util
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rxkad
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/config
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/fsint
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/vlserver
-I/service/openafs/source-1.3.79/openafs-1.3.79/include
-I/service/openafs/source-1.3.79/openafs-1.3.79/include/afs-O2
-fomit-frame-pointer -fno-strength-reduce -fno-strict-aliasing -fno-common
-pipe -ffixed-r13 -mfixed-range=f10-f15,f32-f127 -falign-functions=32
-mb-step -D__KERNEL__ -DKERNEL -D_KERNEL -DMODULE -DAFS_SMP   -I. -I../
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/config
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rx
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rxstat -c
/service/openafs/source-1.3.79/openafs-1.3.79/src/afs/LINUX/osi_syscall.c
/service/openafs/source-1.3.79/openafs-1.3.79/src/afs/LINUX/osi_syscall.c:
In function `osi_syscall_init':
/service/openafs/source-1.3.79/openafs-1.3.79/src/afs/LINUX/osi_syscall.c:258:
`_NR_setgroups' undeclared (first use in this function)
/service/openafs/source-1.3.79/openafs-1.3.79/src/afs/LINUX/osi_syscall.c:258:
(Each undeclared identifier is reported only once
/service/openafs/source-1.3.79/openafs-1.3.79/src/afs/LINUX/osi_syscall.c:258:
for each function it appears in.)
make[4]: *** [osi_syscall.o] Error 1
make[4]: Leaving directory
`/service/openafs/source-1.3.79/openafs-1.3.79/src/libafs/MODLOAD-2.4.21-sgi301r1-MP'
make[3]: *** [linux_compdirs] Error 2
make[3]: Leaving directory
`/service/openafs/source-1.3.79/openafs-1.3.79/src/libafs'
make[2]: *** [libafs] Error 2
make[2]: Leaving directory `/service/openafs/source-1.3.79/openafs-1.3.79'
make[1]: *** [build] Error 2
make[1]: Leaving directory `/service/openafs/source-1.3.79/openafs-1.3.79'
make: *** [all] Error 2

  Any suggestions what I might try to do next?

Dipl. Chem. Dr. Stephan Wonczak

Zentrum fuer Angewandte Informatik (ZAIK)
Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Robert-Koch-Strasse 10, 50931 Koeln
Tel: ++49/(0)221/478-5577, Fax: ++49/(0)221/478-5590


___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Build failure on ia64

2005-03-03 Thread Stephan Wonczak 
  Hi Chas!

On Thu, 3 Mar 2005, chas williams - CONTRACTOR wrote:

 In message [EMAIL PROTECTED]
 ,Stephan Wonczak writes:
 /service/openafs/source-1.3.79/openafs-1.3.79/src/afs/LINUX/osi_syscall.c:258:
 `_NR_setgroups' undeclared (first use in this function)

 try this.  i believe i have already submitted this to openafs-bugs.  it
 didnt make the 1.3.79 release.

 --- src/afs/LINUX/osi_syscall.c.000   2005-03-03 09:36:35.0 -0500
 +++ src/afs/LINUX/osi_syscall.c   2005-03-03 09:36:51.0 -0500
 @@ -255,7 +255,7 @@
   SYSCALL2POINTER afs_sys_call_table[_S(__NR_setgroups)];
   ((struct fptr *)sys_setgroupsp)-gp = kernel_gp;

 - afs_sys_call_table[_S(_NR_setgroups)] =
 + afs_sys_call_table[_S(__NR_setgroups)] =
   POINTER2SYSCALL((struct fptr *)afs_xsetgroups_stub)-ip;
  }

  Yes, this got me a bit further. But not quite to the finish line :-)
  Here's the next error:

cc -I. -I.. -I../nfs -I/service/openafs/source-1.3.79/openafs-1.3.79/src
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/afs
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/afs/LINUX
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/config
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rx/LINUX
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rxkad
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rxkad/domestic
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/util
-I/service/openafs/source-1.3.79/openafs-1.3.79/src
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/afs
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/afs/LINUX
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/util
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rxkad
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/config
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/fsint
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/vlserver
-I/service/openafs/source-1.3.79/openafs-1.3.79/include
-I/service/openafs/source-1.3.79/openafs-1.3.79/include/afs   -O2  -O2
-fomit-frame-pointer -fno-strength-reduce -fno-strict-aliasing -fno-common
-pipe -ffixed-r13 -mfixed-range=f10-f15,f32-f127 -falign-functions=32
-mb-step -D__KERNEL__ -DKERNEL -D_KERNEL -DMODULE  -I. -I../
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/config
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rx
-I/service/openafs/source-1.3.79/openafs-1.3.79/src/rxstat -c
/service/openafs/source-1.3.79/openafs-1.3.79/src/afs/afs_analyze.c
In file included from ../asm/uaccess.h:36,
 from
/service/openafs/source-1.3.79/openafs-1.3.79/src/afs/sysincludes.h:84,
 from
/service/openafs/source-1.3.79/openafs-1.3.79/src/afs/afs_analyze.c:20:
../asm/pgtable.h: In function `ptep_get_and_set':
../asm/pgtable.h:400: incompatible types in assignment
make[4]: *** [afs_analyze.o] Error 1
make[4]: Leaving directory
`/service/openafs/source-1.3.79/openafs-1.3.79/src/libafs/MODLOAD-2.4.21-sgi301r1-SP'
make[3]: *** [linux_compdirs] Error 2
make[3]: Leaving directory
`/service/openafs/source-1.3.79/openafs-1.3.79/src/libafs'
make[2]: *** [libafs] Error 2
make[2]: Leaving directory `/service/openafs/source-1.3.79/openafs-1.3.79'
make[1]: *** [build] Error 2
make[1]: Leaving directory `/service/openafs/source-1.3.79/openafs-1.3.79'
make: *** [all] Error 2

  Any more suggestions? I'll try any patches!

Dipl. Chem. Dr. Stephan Wonczak

Zentrum fuer Angewandte Informatik (ZAIK)
Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Robert-Koch-Strasse 10, 50931 Koeln
Tel: ++49/(0)221/478-5577, Fax: ++49/(0)221/478-5590


___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

[OpenAFS] Compile failure of 1.3.77 on ia64

2005-01-13 Thread Stephan Wonczak 
  Hi list!
  In december I already reported compilation failures of 1.3.74 und 75.
After my christmas vacation I decided to try 1.3.77. Still the same error:

cc -I. -I.. -I../nfs -I/service/openafs/source-1.3.77/openafs-1.3.77/src
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/afs
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/afs/LINUX
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/config
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/rx/LINUX
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/rxkad
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/rxkad/domestic
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/util
-I/service/openafs/source-1.3.77/openafs-1.3.77/src
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/afs
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/afs/LINUX
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/util
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/rxkad
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/config
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/fsint
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/vlserver
-I/service/openafs/source-1.3.77/openafs-1.3.77/include
-I/service/openafs/source-1.3.77/openafs-1.3.77/include/afs-O2
-fomit-frame-pointer -fno-strength-reduce -fno-strict-aliasing -fno-common
-pipe -ffixed-r13 -mfixed-range=f10-f15,f32-f127 -falign-functions=32
-mb-step -D__KERNEL__ -DKERNEL -D_KERNEL -DMODULE -DAFS_SMP   -I. -I../
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/config
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/rx
-I/service/openafs/source-1.3.77/openafs-1.3.77/src/rxstat -c
/service/openafs/source-1.3.77/openafs-1.3.77/src/afs/LINUX/osi_module.c
/service/openafs/source-1.3.77/openafs-1.3.77/src/afs/LINUX/osi_module.c:
In function `afs_init':
/service/openafs/source-1.3.77/openafs-1.3.77/src/afs/LINUX/osi_module.c:376:
`sys_chdir' undeclared (first use in this function)
/service/openafs/source-1.3.77/openafs-1.3.77/src/afs/LINUX/osi_module.c:376:
(Each undeclared identifier is reported only once
/service/openafs/source-1.3.77/openafs-1.3.77/src/afs/LINUX/osi_module.c:376:
for each function it appears in.)
/service/openafs/source-1.3.77/openafs-1.3.77/src/afs/LINUX/osi_module.c:378:
`sys_write' undeclared (first use in this function)
make[4]: *** [osi_module.o] Error 1
make[4]: Leaving directory
`/service/openafs/source-1.3.77/openafs-1.3.77/src/libafs/MODLOAD-2.4.21-sgi301r1-MP'
make[3]: *** [linux_compdirs] Error 2
make[3]: Leaving directory
`/service/openafs/source-1.3.77/openafs-1.3.77/src/libafs'
make[2]: *** [libafs] Error 2
make[2]: Leaving directory `/service/openafs/source-1.3.77/openafs-1.3.77'
make[1]: *** [build] Error 2
make[1]: Leaving directory `/service/openafs/source-1.3.77/openafs-1.3.77'
make: *** [all] Error 2

  My version of gcc is:

[EMAIL PROTECTED] openafs-1.3.77]# gcc --version
gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-34)

  and make:

[EMAIL PROTECTED] openafs-1.3.77]# make --version
GNU Make version 3.79.1, by Richard Stallman and Roland McGrath.
Built for ia64-unknown-linux-gnu

  I am willing to test patches, suggestions or anything anyone might
decide to bounce my way.

Dipl. Chem. Dr. Stephan Wonczak

Zentrum fuer Angewandte Informatik (ZAIK)
Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Robert-Koch-Strasse 10, 50931 Koeln
Tel: ++49/(0)221/478-5577, Fax: ++49/(0)221/478-5590


___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Compile falure on ia64

2004-12-13 Thread Stephan Wonczak 
  Answering to my own mail...

On Wed, 8 Dec 2004, Stephan Wonczak wrote:

   Hi all!
   Last week we got a new, shiny SGI Altix for our machine room. Naturally
 I want to put an OpenAFS-Client on in. As there are no binary packages
 available (... hint, hint :-) ), I tried to build from source.
   I tried both 1.2.13 and 1.3.74. Both builds start fine ('configure'
 reports no errors), but later it bails out. The spot is different between
 the versions, though. On 1.2.13 I get:
errors snipped

  I just downloaded 1.3.75. Still no cigar:

cc -I. -I.. -I../nfs -I/service/openafs/source-1.3.75/openafs-1.3.75/src
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/afs
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/afs/LINUX
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/config
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/rx/LINUX
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/rxkad
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/rxkad/domestic
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/util
-I/service/openafs/source-1.3.75/openafs-1.3.75/src
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/afs
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/afs/LINUX
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/util
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/rxkad
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/config
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/fsint
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/vlserver
-I/service/openafs/source-1.3.75/openafs-1.3.75/include
-I/service/openafs/source-1.3.75/openafs-1.3.75/include/afs-O2
-fomit-frame-pointer -fno-strength-reduce -fno-strict-aliasing -fno-common
-pipe -ffixed-r13 -mfixed-range=f10-f15,f32-f127 -falign-functions=32
-mb-step -D__KERNEL__ -DKERNEL -D_KERNEL -DMODULE -DAFS_SMP   -I. -I../
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/config
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/rx
-I/service/openafs/source-1.3.75/openafs-1.3.75/src/rxstat -c
/service/openafs/source-1.3.75/openafs-1.3.75/src/afs/LINUX/osi_module.c
/service/openafs/source-1.3.75/openafs-1.3.75/src/afs/LINUX/osi_module.c:
In function `afs_init':
/service/openafs/source-1.3.75/openafs-1.3.75/src/afs/LINUX/osi_module.c:376:
`sys_chdir' undeclared (first use in this function)
/service/openafs/source-1.3.75/openafs-1.3.75/src/afs/LINUX/osi_module.c:376:
(Each undeclared identifier is reported only once
/service/openafs/source-1.3.75/openafs-1.3.75/src/afs/LINUX/osi_module.c:376:
for each function it appears in.)
/service/openafs/source-1.3.75/openafs-1.3.75/src/afs/LINUX/osi_module.c:378:
`sys_write' undeclared (first use in this function)
make[4]: *** [osi_module.o] Error 1
make[4]: Leaving directory
`/service/openafs/source-1.3.75/openafs-1.3.75/src/libafs/MODLOAD-2.4.21-sgi301r1-MP'
make[3]: *** [linux_compdirs] Error 2
make[3]: Leaving directory
`/service/openafs/source-1.3.75/openafs-1.3.75/src/libafs'
make[2]: *** [libafs] Error 2
make[2]: Leaving directory `/service/openafs/source-1.3.75/openafs-1.3.75'
make[1]: *** [build] Error 2
make[1]: Leaving directory `/service/openafs/source-1.3.75/openafs-1.3.75'
make: *** [all] Error 2

Version of gcc is:
[EMAIL PROTECTED] openafs-1.3.75]# gcc --version
gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-34)

any pointers at all?

Dipl. Chem. Dr. Stephan Wonczak

Zentrum fuer Angewandte Informatik (ZAIK)
Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Robert-Koch-Strasse 10, 50931 Koeln
Tel: ++49/(0)221/478-5577, Fax: ++49/(0)221/478-5590


___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Compile falure on ia64

2004-12-13 Thread Stephan Wonczak 
On Mon, 13 Dec 2004, Derrick J Brashear wrote:

 On Mon, 13 Dec 2004, Stephan Wonczak wrote:

  /service/openafs/source-1.3.75/openafs-1.3.75/src/afs/LINUX/osi_module.c:376:
  `sys_chdir' undeclared (first use in this function)
  /service/openafs/source-1.3.75/openafs-1.3.75/src/afs/LINUX/osi_module.c:376:
  (Each undeclared identifier is reported only once

 for some reason it thinks it can use these, i'm surprised they've gone
 away. jeff hutzelman should have a better version of this function shortly
 based on the method arla uses. but as far as i know he's not quite done
 yet.

  Hmmm, ok, this probably means I'll just have to wait.
  By the way: The machine is not in production yet, so I am able to do
some testing if required. At least, for the remainder of the week; I'll
leave for vacation on sunday.
  Anyway, thanks for looking into this.

Dipl. Chem. Dr. Stephan Wonczak

Zentrum fuer Angewandte Informatik (ZAIK)
Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Robert-Koch-Strasse 10, 50931 Koeln
Tel: ++49/(0)221/478-5577, Fax: ++49/(0)221/478-5590


___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info

[OpenAFS] Compile falure on ia64

2004-12-08 Thread Stephan Wonczak 
  Hi all!
  Last week we got a new, shiny SGI Altix for our machine room. Naturally
I want to put an OpenAFS-Client on in. As there are no binary packages
available (... hint, hint :-) ), I tried to build from source.
  I tried both 1.2.13 and 1.3.74. Both builds start fine ('configure'
reports no errors), but later it bails out. The spot is different between
the versions, though. On 1.2.13 I get:

gcc   -O2 -fomit-frame-pointer -fno-strength-reduce -fno-strict-aliasing
-fno-common -pipe -ffixed-r13 -mfixed-range=f10-f15,f32-f127
-falign-functions=32 -mb-step -D__KERNEL__ -DKERNEL -D_KERNEL  -DMODULE
-I. -I../ -I/service/openafs/source-1.2.13/openafs-1.2.13/src/config -c
../afs/afs_analyze.c;
In file included from ../asm/uaccess.h:36,
 from ../afs/sysincludes.h:65,
 from ../afs/afs_analyze.c:19:
../asm/pgtable.h: In function `ptep_get_and_set':
../asm/pgtable.h:400: incompatible types in assignment
make[4]: *** [afs_analyze.o] Error 1
make[4]: Leaving directory
`/service/openafs/source-1.2.13/openafs-1.2.13/src/libafs/MODLOAD-2.4.21-sgi301r1-SP'
make[3]: *** [linux_compdirs] Error 2
make[3]: Leaving directory
`/service/openafs/source-1.2.13/openafs-1.2.13/src/libafs'
make[2]: *** [libafs] Error 2
make[2]: Leaving directory `/service/openafs/source-1.2.13/openafs-1.2.13'
make[1]: *** [build] Error 2
make[1]: Leaving directory `/service/openafs/source-1.2.13/openafs-1.2.13'
make: *** [all] Error 2

  while on 1.3.74

cc -I. -I.. -I../nfs -I/service/openafs/source-1.3.74/openafs-1.3.74/src
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/afs
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/afs/LINUX
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/config
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/rx/LINUX
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/rxkad
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/rxkad/domestic
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/util
-I/service/openafs/source-1.3.74/openafs-1.3.74/src
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/afs
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/afs/LINUX
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/util
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/rxkad
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/config
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/fsint
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/vlserver
-I/service/openafs/source-1.3.74/openafs-1.3.74/include
-I/service/openafs/source-1.3.74/openafs-1.3.74/include/afs-O2
-fomit-frame-pointer -fno-strength-reduce -fno-strict-aliasing -fno-common
-pipe -ffixed-r13 -mfixed-range=f10-f15,f32-f127 -falign-functions=32
-mb-step -D__KERNEL__ -DKERNEL -D_KERNEL -DMODULE -DAFS_SMP   -I. -I../
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/config
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/rx
-I/service/openafs/source-1.3.74/openafs-1.3.74/src/rxstat -c
/service/openafs/source-1.3.74/openafs-1.3.74/src/afs/LINUX/osi_module.c
/service/openafs/source-1.3.74/openafs-1.3.74/src/afs/LINUX/osi_module.c:
In function `afs_init':
/service/openafs/source-1.3.74/openafs-1.3.74/src/afs/LINUX/osi_module.c:327:
`sys_chdir' undeclared (first use in this function)
/service/openafs/source-1.3.74/openafs-1.3.74/src/afs/LINUX/osi_module.c:327:
(Each undeclared identifier is reported only once
/service/openafs/source-1.3.74/openafs-1.3.74/src/afs/LINUX/osi_module.c:327:
for each function it appears in.)
/service/openafs/source-1.3.74/openafs-1.3.74/src/afs/LINUX/osi_module.c:329:
`sys_write' undeclared (first use in this function)
make[4]: *** [osi_module.o] Error 1
make[4]: Leaving directory
`/service/openafs/source-1.3.74/openafs-1.3.74/src/libafs/MODLOAD-2.4.21-sgi301r1-MP'
make[3]: *** [linux_compdirs] Error 2
make[3]: Leaving directory
`/service/openafs/source-1.3.74/openafs-1.3.74/src/libafs'
make[2]: *** [libafs] Error 2
make[2]: Leaving directory `/service/openafs/source-1.3.74/openafs-1.3.74'
make[1]: *** [build] Error 2
make[1]: Leaving directory `/service/openafs/source-1.3.74/openafs-1.3.74'
make: *** [all] Error 2


  Any ideas on how to proceed?

Dipl. Chem. Dr. Stephan Wonczak

Zentrum fuer Angewandte Informatik (ZAIK)
Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Robert-Koch-Strasse 10, 50931 Koeln
Tel: ++49/(0)221/478-5577, Fax: ++49/(0)221/478-5590


___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info