Hello,
In one of recent posts on this list, I found a magical parameter list to
optimize performance of the file server for 'modern systems'. The magic
suggested is copied below for reference:
-p 23 -busyat 600 -rxpck 400 -s 1200 -l 1200 -cb 65535 -b 240 -vc
1200
While running
Hello,
On Mon, 11 Sep 2006, Jakub Witkowski wrote:
While running /usr/lib/openafs/fileserver -help suggested some meaning
of the parameters listed above, it did not provide enough information to
allow more conscious adjustment of server settings.
More information about those parameters can
The namei interface uses file locking extensively, implemented using
lockf() on Solaris, AIX HP-UX.
Unfortunately lockf() locks and unlocks from the *current position* to
whatever the argument says (end of file), moving the file pointer in
between becomes a problem for the subsequent unlock!
Hm. Your patch seems to do this:
change:
lock/unlock from current to eof
to:
seek 0
lock/unlock from (current=0) to eof
Which means you're potentially destroying the notion of current (I
don't know if that's important in AFS code or not, but it seems like,
at best, a bad idea ... and at
John Rudd wrote:
Hm. Your patch seems to do this:
change:
lock/unlock from current to eof
to:
seek 0
lock/unlock from (current=0) to eof
Which means you're potentially destroying the notion of current (I
don't know if that's important in AFS code or not, but it seems like, at
best, a bad
Chris Huebsch wrote:
Hello,
On Mon, 11 Sep 2006, Jakub Witkowski wrote:
While running /usr/lib/openafs/fileserver -help suggested some meaning
of the parameters listed above, it did not provide enough information to
allow more conscious adjustment of server settings.
More information
I'm getting a similar error now, with different versions.
Server1 is 1.5.8 (on linux-i386), server2 is 1.4.2fc3 (on
linux-alpha). When I release from server1 to server2 the latter tells
me:
VolserLog.old:Sun Sep 10 08:01:49 2006 1 Volser: RestoreVolume: End
of dump not found; restore aborted
Kevin wrote:
I realize that various filesystem tools (ext2, ext3, etc.) have utilities to
map bad blocks and avoid having the system use them, but is it a good rule
of thumb that a HDD with bad blocks is failing? ie, that finding bad blocks
is an indicator that the HDD will soon fail
Right, only that for a correct flock() emulation you'd also have to
hold the necessary locks to prevent another thread from seeking
away between the two calls... ideally something that is independent
of the namei locking. And the code would gain in readability had
the ifdefs been packed
Can someone take a look at [grand.central.org #39552]
AutoReply: 1.5.8 libafs unknown symbols?
tedc
And, although John didn't mention it, yeah... there is something strange
going on. Our setup here is a might funky. Enough old transarc bits and
hard coded segments of our old account management system so that I can
dream for a 10 minute upgrade, but it's pretty soundly in the dream
state. :p
The obtain new tokens button in afsclient
returns cant find KDC.
If NetIdMgr is used, tokens are found correctly.
I dont know if this is expected behaviour or not?
tedc
On Monday, September 11, 2006 12:45:40 PM -0400 Tom Keiser
[EMAIL PROTECTED] wrote:
As it turns out, the way we use file locks in the volume package is
quite broken. The spec says that once a process closes *any* file
descriptor, all fcntl locks held for that file are immediately
On Mon, 11 Sep 2006, ted creedon wrote:
Can someone take a look at [grand.central.org #39552] AutoReply: 1.5.8
libafs unknown symbols?
Did you answer my reply? If so, I will get to your reply in a few hours.
If not, maybe you should do that.
___
Yes, I did. Your question is not clear to me.
Can you clarify what additional info you need?
tedc
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Derrick J Brashear
Sent: Monday, September 11, 2006 11:10 AM
To: openafs-info@openafs.org
Subject: Re:
Hi, all,
I downloaded kernel 2.6.17.7 from kernel.org and built it as
usual for my environment. I needed the newer kernel because
I have some machines with recent NIC and SCSI interfaces
that don't get picked up under the old 2.6.13-1.1532_FC4 kernel
I've been using for my FC4 machines. Using
--On Monday, September 11, 2006 1:04 PM +0200 Rainer Toebbicke
[EMAIL PROTECTED] wrote:
Right, only that for a correct flock() emulation you'd also have to hold
the necessary locks to prevent another thread from seeking away between
the two calls... ideally something that is independent of the
On 9/11/06, Jeffrey Hutzelman [EMAIL PROTECTED] wrote:
On Monday, September 11, 2006 12:45:40 PM -0400 Tom Keiser
[EMAIL PROTECTED] wrote:
As it turns out, the way we use file locks in the volume package is
quite broken. The spec says that once a process closes *any* file
descriptor, all
Chris Huebsch [EMAIL PROTECTED] writes:
More information about those parameters can be found - as always - in
the manual:
http://www.openafs.org/pages/doc/AdminReference/auarf129.htm
Note that a lot of new parameters have been added, so the manual is sadly
out of date in this area. Right
Hi,
Is there anybody who had success in installating an OpenAFS server AND an
OpenAFS client on a SLES9 or SLES10 ?
If yes, could you try to give me some clues...I tried to follow some
documentation on internet and to compile last version but no way...
If a Novell/Suse guy can also tell me if it
Francois Pernet wrote:
Hi,
Is there anybody who had success in installating an OpenAFS server AND an
OpenAFS client on a SLES9 or SLES10 ?
If yes, could you try to give me some clues...I tried to follow some
documentation on internet and to compile last version but no way...
If a Novell/Suse
On Saturday 09 September 2006 04:29, Francois Pernet wrote:
Hi,
Is there anybody who had success in installating an OpenAFS server AND an
OpenAFS client on a SLES9 or SLES10 ?
If yes, could you try to give me some clues...I tried to follow some
documentation on internet and to compile last
Compile your own 1.4.2 client and server, 1.5.8 has some minor variable
problems both 32 and 64 bit ..
Works fine on SuSE 9.xx -10.1
The 1.4.x Windows clients work fine and 1.5.08 windows clients are in test
The lack of a long term stable OpenAFS gets in the way of SUSE's release
criteria. If
On Mon, 11 Sep 2006, ted creedon wrote:
Compile your own 1.4.2 client and server, 1.5.8 has some minor variable
problems both 32 and 64 bit ..
If you don't have nfs server turned on in your kernel, you can't use the
nfs translator kernel module.
Derrick
It would help if you said what version of OpenAFS you were using.
Mike Polek wrote:
Hi, all,
I downloaded kernel 2.6.17.7 from kernel.org and built it as
usual for my environment. I needed the newer kernel because
I have some machines with recent NIC and SCSI interfaces
that don't get
I propose we move this discussion to -devel.
On 9/11/06, Rainer Toebbicke [EMAIL PROTECTED] wrote:
The namei interface uses file locking extensively, implemented using
lockf() on Solaris, AIX HP-UX.
Unfortunately lockf() locks and unlocks from the *current position* to
whatever the argument
On Tue, 12 Sep 2006, Jeff Blaine wrote:
Has anyone solved this? :( I'm using OpenAFS 1.4.1.
Patch 113273-11 (sshd SPARC) has killed off token-getting via
pam_afs.so.1
Lemme guess. It forks and the PAG is in the child, and so goes away...
___
Has anyone solved this? :( I'm using OpenAFS 1.4.1.
Patch 113273-11 (sshd SPARC) has killed off token-getting via
pam_afs.so.1
I'm syslogging *.debug to /var/adm/debug.log and all I get is
the following (even with 'debug' as an option to pam_afs.so.1)
Sep 12 00:11:12 noodle.domain.com
Oops... openafs 1.4.1, compiled from source rpm, built 5/24/2006.
The kernel module was compiled in the last few weeks from the
same original source RPM openafs-1.4.1-fc4.1.src.rpm.
Thx,
Mike
Jeffrey Altman wrote:
It would help if you said what version of OpenAFS you were using.
Mike
29 matches
Mail list logo
