Hi,
I have very strange vldb-entry:
|[EMAIL PROTECTED] ~]# vos listvldb|head
|VLDB entries for all servers
|
|
|Backup: 536936854
|number of sites - 1
| server afs4.andre.c.sn.schule.de partition /vicepa RW Site
vos exa 536936854 gives
|[EMAIL PROTECTED] ~]# vos exa 536936854
Hi,
We have a problem at customer side (in production env.): we have a SLES9,
kernel 2.6.5-7.193-smp, 586.
Every openafs clients servers are 1.4.0.
Symptom: when a client creates/deletes/modifies any file in a given directory,
it sees the changes, but a small portion of the other clients
Peter Somogyi wrote:
Symptom: when a client creates/deletes/modifies any file in a given
directory,
it sees the changes, but a small portion of the other clients don't see any
change.
And those problematic clients stay 2-3 hours in this state of out-of-sync.
The small portion means that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi. Quick question.
Up until now I've always installed using the transarc paths etc...
However I have a new server going in am thinking of changing to the
default mode (Because it's the default).
However I can only find the old docs from transarc
On Thursday 20 April 2006 14:59, Jeffrey Altman wrote:
99.9% of the time when clients do not receive callbacks it is because of
a firewall or NAT.
AFAIK there's no firewall or NAT on the network between clients and server.
The clients return in sync after the callback registrations expire and
Hi,
I have noticed there is an unwanted afs behavior with kernel 2.6.16 and
openafs 1.4.1. If I enter pagsh and obtain a token and after that I do su to
the same or another user (uid), there is no token any more. It seems like
seteuid or similar call enters a new pag.
I have been running
All,
We use the native afs backup. We currently do a full backup of the whole
cell weekly followed by daily incrementals until we cycle back to Monday
midnight and start the next full.
As the size of the cell (user vols ) grows our backup window is getting
way too big. Often it stretches into
Well, I guess I have missed in dmesg:
Warning: failed to find address of system call table
System call hooks will not be installed; proceeding anyway
Found 32-bit system call table at 0x803b3070 (exported)
Is there any newer version of osi_probe.c which could deal with 2.6.16 syscall
[apologies for the cross posting]
The AFS Kerberos Best Practices Workshop 2006 announces the Call For
Papers Talks. Come talk to your peers about
- Work completed
- Work in progress
- Theories
- Best practices
- Related research
or something else that has tickled your brain while
The problem is that the syscall table is in the ReadOnly section
and cannot be modified.
-derek
Andrej Filipcic [EMAIL PROTECTED] writes:
Well, I guess I have missed in dmesg:
Warning: failed to find address of system call table
System call hooks will not be installed; proceeding anyway
What happens if you supply --with-linux-kernel-headers=.. to configure
and point it at the kernel-source for your running kernel?
-derek
Quoting David Sonenberg [EMAIL PROTECTED]:
The configure is simply 'configure --prefix=/'
Derek Atkins wrote:
What's your ./configure and make commands?
Steve Devine said the following on 2006-04-20 17:52:
All,
We use the native afs backup. We currently do a full backup of the whole
cell weekly followed by daily incrementals until we cycle back to Monday
midnight and start the next full.
As the size of the cell (user vols ) grows our backup
12 matches
Mail list logo