Re: [OpenAFS] memcache or diskcache on ramdisk

2004-12-02 Thread Hartmut Reuter
EC wrote:
Hi,
Do using memory cache for AFSD 'better' (faster, more stable, etc..) than
disk cache over RAMDISK or TMPFS ?
EC. 
My experience with 1.3.74 is that memcache is really fast. We reach 70 MB/s
for write and 48 MB/s for read of an 8 GB file which is about 20 MB/s 
faster than
with ramdisk. This was on SuSE SLES-9 with kernel 2.6.5-7.

With the 2.6 kernel there is still a problem that the disk cache gets 
full which makes
the use of ramdisk nearly impossible.

Of course disk cache still makes sense if your network is slower than 
your local
disk. But in production environments such as blade centres the network 
typically
is much faster than the internal disk.

Hartmut

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

--
-
Hartmut Reuter   e-mail [EMAIL PROTECTED]
   phone +49-89-3299-1328
RZG (Rechenzentrum Garching)   fax   +49-89-3299-1301
Computing Center of the Max-Planck-Gesellschaft (MPG) and the
Institut fuer Plasmaphysik (IPP)
-
___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info


Re: [OpenAFS] Re: AFS Perl module and threaded Perl

2004-12-02 Thread Russ Allbery
Norbert Gruener [EMAIL PROTECTED] writes:

 Here is my description which I had sent to some users of my module.

  problem description -
 And this is the outcome.  Perl in the thread version is linked
 against the libpthread system library.  Therefore it gets the
 thread version of the system calls (in our case longjmp).  Whereas
 OpenAFS is using its own threading package (called LWP).  And these
 two things are not compatible.

I don't understand... LWP doesn't provide its own version of longjmp, so
far as I can tell.  It just calls the system version.

 I could prove that by linking the OpenAFS vos binary against the
 libpthread.  Then the vos binary crashed exactly on the same
 statement as the Perl AFS module.

Is it perhaps doing something that breaks some assumption made by the
pthread version of the libraries?

 The final conclusion of this case is that as long as OpenAFS is using
 its own threading, it is not possible to use Perl with 'threading'.
  problem description -

Even if this is the case, this shouldn't be an impediment to getting the
AFS Perl module working, should it?  After all, none of the *client* code
does any threading at all.  Can't it just be built with the same libraries
that Perl is built with?

-- 
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info


Re: [OpenAFS] unable to start afs client

2004-12-02 Thread Horst Birthelmer
On Dec 1, 2004, at 11:38 PM, EC wrote:
Hi Horst !!!
I have some news : I've taken my PIV kernel and changed it to PIII. 
Then
applied it to the PIII. Magic OpenAFS client works !!! Which means,
since everything is built automatically, there AFS client is dependant 
of
some options in the linux kernel (or is at least not happy with some 
option
enabled..).
I'll try to check that out !

As far as I recall you were having trouble with the creation and/or 
access to VolumeItems.
You got an error similar to ENOENT.

From your information I don't see any connection other than your 
previous kernel module perhaps wasn't build for the kernel you were 
using it on but that you should have been noticing before. ;-)

Well, anyway ...
since you got the same error  with memcache, too, it won't be any 
option of your file system.

The only thing I can think of is, you built against another kernel or 
you had some of the links the Makefile creates made to another kernel 
sourcetree.
The only option which has some influence here is the one about version 
information in kernel modules.

BTW, enjoy your working AFS :-)
Horst
___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info


[OpenAFS] OpenAFS 1.3.73 on Windows, VPN problems...

2004-12-02 Thread Lars Schimmer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
We dicovered a problem with the OpenAFS Client on windows XP ServicePack 2 on a
dell notebook.
We've got our cell on a subnet at work and bind some user in this subnet with
ppptp on a redhat fedora core 1 server. So if the users make a VPN connection
with this server, they get a IP from our subnet and acting like they were here
at work.
The problem a client discovered is with hibernating the notebook. He doesn't
reboot the notebook for quiet a long time, instead hibernate it or set it to
sleep mode. So in one session the notebook connects to our cell over WLAN,
ethernet-TP, ppptp OVER DSL. And after using the ppptp tunnel for openafs and
hibernating the notebook, the openafs client hang.
And at all the whole notebook hang, because after activate the windows, the
client wants to use the explorer and then the explorer seems to access data on
the afs-tree, and afs hangs. He can click on the afs-icon and try to get the
afs-client-window, but it is opened in the back so no chance to stop the
afs-service.
Another client is able to stop the afs-service and after stopping/starting the
afs service, everything's back to normal.
Any hint on how to prevent the locking of the notebook?
Cya
Lars
- --
- -
Technische Universität Braunschweig, Institut für Computergraphik
Tel.: +49 531 391-2109E-Mail: [EMAIL PROTECTED]
PGP-Key-ID: 0xB87A0E03
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBrt0UVguzrLh6DgMRArt3AJ4/NplfWHZ5CKgtjF++zbtHfZTweQCgwmeH
4AQ7bZKiZQFSzHI9ac3FEHk=
=i8WY
-END PGP SIGNATURE-
___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info


[OpenAFS] 1.3.74 as well as cvs 2004/12/02 TASK_ZOMBIE undeclared

2004-12-02 Thread Helmut Jarausch
Hi,

I try to build the cvs version of OpenAFS (from today) unter Linux
2.6.10-rc2
The compilation fails with the following error message.

/OBJ/OpenAFS/openafs-cvs-041202/src/libafs/MODLOAD-2.6.10-rc2-MP/afs_osi.c: In 
function `afs_osi_TraverseProcTable':
/OBJ/OpenAFS/openafs-cvs-041202/src/libafs/MODLOAD-2.6.10-rc2-MP/afs_osi.c:863: 
error: `TASK_ZOMBIE' undeclared (first use in this function)

Is there any fix for that?

Many thanks,

Helmut Jarausch

Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany

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


Re: [OpenAFS] OpenAFS 1.3.73 on Windows, VPN problems...

2004-12-02 Thread Jeffrey Altman
Lars Schimmer wrote:
Any hint on how to prevent the locking of the notebook?
Well, if this is in fact a bug which is resulting in a deadlock
situation the way to stop it is to get the bug fixed.  For that
to occur you should install a DEBUG version of OpenAFS for
Windows on the machine along with the Debugging Tools for Windows.
When the problem occurs, attach windbg to afsd_service.exe and
capture a full minidump file.  Send the minidump file to
[EMAIL PROTECTED]  Hopefully, I will be able to identify
the deadlock.
FYI, 1.3.74 fixed some thread safety issues associated with
directory searches and my current daily build fixes one with
freelance mode.  There is a chance the problem is associated
with either of these problems.
Jeffrey Altman


smime.p7s
Description: S/MIME Cryptographic Signature


Re: [OpenAFS] 'rxi_AllocPacket: packet not free' with Kernel 2.6 and OpenAFS 1.3.73

2004-12-02 Thread Tom Fischer
On Tue, 23 Nov 2004 09:56:12 +0100
Frank Burkhardt [EMAIL PROTECTED] wrote:

 Hi,
 
 I've got a problem writing data to AFS using an OpenAFS-1.3.73-Client
 on Linux (Kernel 2.6.9, Debian GNU/Linux). Read access seems to work
 fine, i read 10 Gigabytes successfully. But after writing some data
 (some Megabytes), I Get this error message:
 
  rxi_AllocPacket: packet not free
 
 and a Kernel Oops (it's attached to this mail).
 Is there a solution for this problem?

Same here. Kernel 2.6.9 Gentoo Linux, OpenAFS 1.3.73 Client. Reading
works fine, writing a few bytes and the cache manager crashes.

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


Re: [OpenAFS] 'rxi_AllocPacket: packet not free' with Kernel 2.6 and OpenAFS 1.3.73

2004-12-02 Thread Hendrik Hoeth
Thus spake Tom Fischer ([EMAIL PROTECTED]):

 Same here. Kernel 2.6.9 Gentoo Linux, OpenAFS 1.3.73 Client. Reading
 works fine, writing a few bytes and the cache manager crashes.

No problem here. Kernel 2.6.9 vanilla, openafs 1.3.73 client. Not a
single crash yet, both reading and writing.

-- 
It's not the people who vote that count.
It's the people who count the votes.
 (Joseph Stalin)
___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info


Re: [OpenAFS] 1.3.74 as well as cvs 2004/12/02 TASK_ZOMBIE undeclared

2004-12-02 Thread Hendrik Hoeth
Thus spake Helmut Jarausch ([EMAIL PROTECTED]):

 I try to build the cvs version of OpenAFS (from today) unter Linux
 2.6.10-rc2 The compilation fails with the following error message.
 
 /OBJ/OpenAFS/openafs-cvs-041202/src/libafs/MODLOAD-2.6.10-rc2-MP/afs_osi.c: 
 In function `afs_osi_TraverseProcTable':
 /OBJ/OpenAFS/openafs-cvs-041202/src/libafs/MODLOAD-2.6.10-rc2-MP/afs_osi.c:863:
  error: `TASK_ZOMBIE' undeclared (first use in this function)
 
 Is there any fix for that?

That's what I wrote a month ago about 2.6.10-rc1. They removed
TASK_ZOMBIE from the kernel between 2.6.9 and 2.6.10-rc1 and replaced it
by something else. Don't have any idea what's all this for, though. I
simply went back to 2.6.9.

Hendrik

-- 
It's not the people who vote that count.
It's the people who count the votes.
 (Joseph Stalin)
___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info


Re: [OpenAFS] client hangs through ipsec

2004-12-02 Thread Wes Chow


I should mention that in this setup, the two IPsec gateways are on the
same subnet:

 This is a tcpdump port 7000 on the client machine:
 
 21:48:07.671387 IP confucius.ho.in.athenacr.com.afs3-callback 
 helmsley.dev.in.athenacr.com.afs3-fileserver:  rx ack first 38 serial
 0 reason delay (65)
 21:48:07.739039 IP helmsley.dev.in.athenacr.com.afs3-fileserver 
 confucius.ho.in.athenacr.com.afs3-callback:  rx data (1436)
 21:48:07.739051 IP confucius.ho.in.athenacr.com.afs3-callback 
 helmsley.dev.in.athenacr.com.afs3-fileserver:  rx ack first 38 serial
 65 reason ack requested acked 637534208 (66)
 21:48:07.742036 IP helmsley.dev.in.athenacr.com.afs3-fileserver 
 confucius.ho.in.athenacr.com.afs3-callback:  rx data (1436)
 21:48:07.742050 IP confucius.ho.in.athenacr.com.afs3-callback 
 helmsley.dev.in.athenacr.com.afs3-fileserver:  rx ack first 39 serial
 66 reason ack requested acked 654311424 (66)
 21:48:08.119058 IP helmsley.dev.in.athenacr.com.afs3-fileserver 
 confucius.ho.in.athenacr.com.afs3-callback:  rx data (1436)
 21:48:08.119075 IP confucius.ho.in.athenacr.com.afs3-callback 
 helmsley.dev.in.athenacr.com.afs3-fileserver:  rx ack first 40 serial
 69 reason ack requested acked 671088640 (66)
 21:48:08.122055 IP helmsley.dev.in.athenacr.com.afs3-fileserver 
 confucius.ho.in.athenacr.com.afs3-callback:  rx data (1436)


And in this setup, the IPsec gateways are separated by an unknown
number of routers:

 21:56:07.912736 IP berra.ho.in.athenacr.com.afs3-callback 
 hippo.dev.in.athenacr.com.afs3-fileserver:  rx ack first 1 serial 0
 reason ping (65)
 21:56:07.915493 IP hippo.dev.in.athenacr.com.afs3-fileserver 
 berra.ho.in.athenacr.com.afs3-callback:  rx ack first 2 serial 8
 reason ping response (65)
 21:56:16.072313 IP berra.ho.in.athenacr.com.afs3-callback 
 hippo.dev.in.athenacr.com.afs3-fileserver:  rx ack first 1 serial 0
 reason ping (65)
 21:56:16.074425 IP hippo.dev.in.athenacr.com.afs3-fileserver 
 berra.ho.in.athenacr.com.afs3-callback:  rx ack first 2 serial 9
 reason ping response (65)
 21:56:21.608237 IP hippo.dev.in.athenacr.com.afs3-fileserver 
 berra.ho.in.athenacr.com.afs3-callback:  rx ack first 2 serial 0
 reason ping (65)
 21:56:21.608286 IP berra.ho.in.athenacr.com.afs3-callback 
 hippo.dev.in.athenacr.com.afs3-fileserver:  rx ack first 1 serial 13
 reason ping response (65)
 21:56:31.637632 IP hippo.dev.in.athenacr.com.afs3-fileserver 
 berra.ho.in.athenacr.com.afs3-callback:  rx ack first 2 serial 0
 reason ping (65)
 21:56:31.637651 IP berra.ho.in.athenacr.com.afs3-callback 
 hippo.dev.in.athenacr.com.afs3-fileserver:  rx ack first 1 serial 15
 reason ping response (65)


-- 
http://www.woahnelly.net/~wes/  OpenPGP key = 0xA5CA6644
fingerprint = FDE5 21D8 9D8B 386F 128F  DF52 3F52 D582 A5CA 6644
___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info


Re: [OpenAFS] SQLite?

2004-12-02 Thread Jack Neely
On Tue, Nov 30, 2004 at 01:40:23PM -0500, John S. Bucy wrote:
 
 Does anyone here have any experience putting SQLite databases in AFS with
 concurrent access from multiple clients?
 
 
 
 
 john
 ___
 OpenAFS-info mailing list
 [EMAIL PROTECTED]
 https://lists.openafs.org/mailman/listinfo/openafs-info
 

I believe SQLite (which I think is great, BTW) uses POSIX advisory
locking.  The documentation suggests that you should avoid network file
systems.  I actually haven't tried this, but I wouldn't trust SQLite dbs
to work in AFS.

   http://www.sqlite.org/lockingv3.html

Jack

-- 
Jack Neely [EMAIL PROTECTED]
Realm Linux Administration and Development
PAMS Computer Operations at NC State University
GPG Fingerprint: 1917 5AC1 E828 9337 7AA4  EA6B 213B 765F 3B6A 5B89
___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info


Re: [OpenAFS] SQLite?

2004-12-02 Thread Derek Atkins
Jack Neely [EMAIL PROTECTED] writes:

 I believe SQLite (which I think is great, BTW) uses POSIX advisory
 locking.  The documentation suggests that you should avoid network file
 systems.  I actually haven't tried this, but I wouldn't trust SQLite dbs
 to work in AFS.

http://www.sqlite.org/lockingv3.html

 Jack

I haven't looked deeply into the sqlite code (yet) but I plan to use
it in a project next year.  I expect that it wont work across multiple
clients in AFS due to the write-back cache.  I doubt that sqlite
fsync()s the db file after every commit, so I wouldn't think it would
be very sharable that way.

-derek
-- 
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   [EMAIL PROTECTED]PGP key available
___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info


Re: [OpenAFS] 1.3.74 as well as cvs 2004/12/02 TASK_ZOMBIE undeclared

2004-12-02 Thread Derrick J Brashear
On Thu, 2 Dec 2004, Helmut Jarausch wrote:
Hi,
I try to build the cvs version of OpenAFS (from today) unter Linux
2.6.10-rc2
The compilation fails with the following error message.
/OBJ/OpenAFS/openafs-cvs-041202/src/libafs/MODLOAD-2.6.10-rc2-MP/afs_osi.c: In 
function `afs_osi_TraverseProcTable':
/OBJ/OpenAFS/openafs-cvs-041202/src/libafs/MODLOAD-2.6.10-rc2-MP/afs_osi.c:863: 
error: `TASK_ZOMBIE' undeclared (first use in this function)
Is there any fix for that?
use EXIT_ZOMBIE instead. if you're bored, write a configure test too and 
contribute it;-)

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


Re: [OpenAFS] 'rxi_AllocPacket: packet not free' with Kernel 2.6 and OpenAFS 1.3.73

2004-12-02 Thread Tom Fischer
On Thu, 2 Dec 2004 15:04:49 +0100
Hendrik Hoeth [EMAIL PROTECTED] wrote:

 Thus spake Tom Fischer ([EMAIL PROTECTED]):
 
  Same here. Kernel 2.6.9 Gentoo Linux, OpenAFS 1.3.73 Client. Reading
  works fine, writing a few bytes and the cache manager crashes.
 
 No problem here. Kernel 2.6.9 vanilla, openafs 1.3.73 client. Not a
 single crash yet, both reading and writing.

My Kernel is also vanilla. Are there some Kernel Options which are
related to afs?

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


Re: [OpenAFS] 'rxi_AllocPacket: packet not free' with Kernel 2.6 and OpenAFS 1.3.73

2004-12-02 Thread Hendrik Hoeth
Thus spake Tom Fischer ([EMAIL PROTECTED]):

 My Kernel is also vanilla. Are there some Kernel Options which are
 related to afs?

nothing I know.

-- 
It's not the people who vote that count.
It's the people who count the votes.
 (Joseph Stalin)
___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info


[OpenAFS] [OpenAFS]How to change IP addresses of Database and File servers??

2004-12-02 Thread Tom Jones
HI

We have two DB as well as File servers running on Redhat linux 3.0 OpenAFS 1.2.11

There is a requirement to move both servers to different subnet. What are the consequences of chaning IP adresses of OpenAFS servers We are not worried abt clients.

Do we need to configure entire cell from scratch

Appreciate your inputs

Thanks

-tom
		Do you Yahoo!? 
The all-new My Yahoo! – What will yours do?

Re: [OpenAFS] [OpenAFS]How to change IP addresses of Database and File servers??

2004-12-02 Thread Derek Atkins
Tom Jones [EMAIL PROTECTED] writes:

 HI
  
 We have two DB as well as File servers running on Redhat linux 3.0  OpenAFS 
 1.2.11
  
 There is a requirement to move both servers to different subnet. What are the
 consequences of chaning IP adresses of OpenAFS servers  We are not 
 worried abt
 clients.

Oh, I _would_ be worried about clients, because you'll need to
reconfigure every one of them with the new set of IPs.

 Do we need to configure entire cell from scratch

No.

-derek

-- 
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   [EMAIL PROTECTED]PGP key available
___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info


Re: [OpenAFS] [OpenAFS]How to change IP addresses of Database and File servers??

2004-12-02 Thread Chris Huebsch
On Thu, 2 Dec 2004, Tom Jones wrote:
Do we need to configure entire cell from scratch
No you don't:
http://www.openafs.org/pages/doc/AdminGuide/auagd008.htm#Header_160
Perhaps it is wise to use afsdb-entries in DNS in order to reduce work
in case of future IP-changes.
http://www.jhsoft.com/help/index.html?rec_afsdb.htm
http://grand.central.org/twiki/bin/view/AFSLore/AFSDB
Use option -afsdb to enable it on each client.
Chris
--
Chris Huebschwww.huebsch-gemacht.de | TU Chemmnitz, Informatik, RNVS
GPG-Encrypted mail welcome! ID:7F2B4DBA |   Str. d. Nationen 62, B204
 Chemnitzer Linux-Tage 2005, 5.-6.Maerz |   D-09107 Chemnitz
http://chemnitzer.linux-tage.de/|  +49 371 531-1377, Fax -1803
___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info


Re: [OpenAFS] 1.3.74 as well as cvs 2004/12/02 TASK_ZOMBIE undeclared

2004-12-02 Thread Chaskiel M Grundman
--On Thursday, December 02, 2004 10:32:44 -0500 Derrick J Brashear
[EMAIL PROTECTED] wrote:

 use EXIT_ZOMBIE instead. if you're bored, write a configure test too and
 contribute it;-)

not quite that simple. You need to look at task-exit_state, not
task-state  (this is based on reading exit.c; signal.c seems to think that
task-state might also get EXIT_ZOMBIE ORed into it, but I think it is
wrong).

Who needs a configure test for this? A #if defined EXIT_ZOMBIE/#elif
defined TASK_ZOMBIE/#else/#error [...]/#endif construct ought to handle it

What we do need to deal with in autoconf is EXPORTED_TASKLIST_LOCK for 2.6.
Our current behavior is unsafe.


p7s5aHu2bOx6t.p7s
Description: S/MIME cryptographic signature


Re: [OpenAFS] OpenAFS 1.2.13 and fsck problems on Solaris 9

2004-12-02 Thread Douglas E. Engert
I did some more testing using OpenAFS 1.3.74 vfsck on a small partition
on a Solaris9 system to look at why it might fail. Here is a patch
to help debug the vfsck to get more debugging info if it fails.
There are two failure situations I ran into: A files system  1Tb
and logging.
If a file system was created with the newfs -T option or mkfs_ufs -o mtb=y
this is creating a file system the can exceed 1Tb. This uses a different
magic number in the super block, and the OpenAFS fsck will fail with
MAGIC NUMBER WRONG. It might take major changes to support this.
Logging allows for fast recovery. It can be turned on and off using the
mount command. See man mount_ufs. Logging may also be turned on
for a large partition, IIRC some one said Solaris 10 will do this?
The fs_logbno filed of the first super block contains the block # of the
embedded log. It appears to be only in the first super block.
The vfsck does not account for this difference when comparing the first
and alternate super blocks, and you can get the  BAD SUPER BLOCK:
VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE.
Note this field is saved over a mount and may even be used as a flag
to continue logging on subsequent mounts.
If I mounted the file system with -o nologging then unmount,
it appears to have cleared this field, and the OpenAFS vfsck works
as expected.
following is a patch to src/vfsck/setup.c for 1.3.74 to dump
the super block and if the memcmp fails dump the alternate super block
so you can see what was different. You might want to try this, to see
if it is the fs_logbno at offest 0x052c or some other problem.
--- ,setup.cWed Aug 25 02:22:22 2004
+++ setup.c Thu Dec  2 13:41:09 2004
@@ -112,6 +112,23 @@
 char *malloc(), *calloc();
 struct disklabel *getdisklabel();
+static
+void hexdump(char * comment, void * in, int len)
+{
+unsigned char *p = (unsigned char *)in;
+int i;
+
+fprintf(stderr,%s,comment);
+for (i=0; ilen; i++)
+{
+if ((i  31) == 0) fprintf(stderr,\n%06x ,i);
+if ((i  3) == 0) fprintf(stderr,  );
+/*if ((i  31) == 0) fprintf(stderr,\n); */
+fprintf(stderr,%02x, p[i]);
+}
+fprintf(stderr,\n);
+}
+
 setup(dev)
  char *dev;
 {
@@ -632,6 +649,7 @@
 /*
  * run a few consistency checks of the super block
  */
+hexdump(main SB,(char *)sblock, (int)sblock.fs_sbsize);
 #ifdef AFS_HPUX_ENV
 #if defined(FD_FSMAGIC)
 if ((sblock.fs_magic != FS_MAGIC)  (sblock.fs_magic != FS_MAGIC_LFN)
@@ -752,7 +770,9 @@
 #if defined(AFS_HPUX110_ENV)
 UpdateAlternateSuper(sblock, altsblock);
 #endif /* AFS_HPUX110_ENV */
-if (memcmp((char *)sblock, (char *)altsblock, (int)sblock.fs_sbsize)) {
+   {
+   int mismatch = 0;
+if (mismatch = memcmp((char *)sblock, (char *)altsblock, 
(int)sblock.fs_sbsize)) {
 #ifdef __alpha
if (memcmp
((char *)sblock.fs_blank[0], (char *)altsblock.fs_blank[0],
@@ -760,9 +780,13 @@
memset((char *)sblock.fs_blank, 0, sizeof(sblock.fs_blank));
} else {
 #endif /* __alpha */
+   /* dump for debugging the two blocks */
+   fprintf(stderr,SB dont match= %d\n,mismatch);
+   hexdump(Alternate SB,(char *)altsblock, 
(int)sblock.fs_sbsize);
badsb(listerr,
  VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST 
ALTERNATE);
return (0);
+   }
 #ifdef __alpha
}
 #endif /* __alpha */

Andy Malato wrote:
! Date: Wed, 01 Dec 2004 08:06:05 -0600
! From: Douglas E. Engert [EMAIL PROTECTED]
! To: Andy Malato [EMAIL PROTECTED]
! Cc: [EMAIL PROTECTED]
! Subject: Re: [OpenAFS] OpenAFS 1.2.13 and fsck problems on Solaris 9
!
!
!
!
!
! Andy Malato wrote:
!
!  I have seen similar postings on this topic in the mail archives, however,
!  I don't know if this issue has been completly resolved.
! 
!  I am running OpenAFS 1.2.13 on Solaris 9 with kernel patch 117171-07.
!  According to what I have read in the archive postings it appears that Sun
!  has made some changes to the UFS data structures, which causes the OpenAFS
!  fsck to break.
! 
!  I get similar messages during each reboot :
! 
! 
!  checking ufs filesystems
!  Open AFS (R) openafs 1.2.13 fsck
!  /dev/rdsk/c2t5d1s0: IMPOSSIBLE INTERLEAVE=0 IN SUPERBLOCK (FIXED)
!  /dev/rdsk/c2t5d1s0: is clean.
!  Open AFS (R) openafs 1.2.13 fsck
!  /dev/rdsk/c3t5d0s0: IMPOSSIBLE INTERLEAVE=0 IN SUPERBLOCK (FIXED)
!  /dev/rdsk/c3t5d0s0: is clean.
! 
!
! This is caused by the fsck checking the old lnterleave field
! that was replaced.
!
! 
!  If I manually run /usr/lib/fs/afs/fsck -y against these devices the
!  problem appears to go away.  However, this still indicates that something
!  may be wrong and I can't help to have limited confidence in
!  /usr/lib/fs/afs/fsck should one of the vice partitions need to be
!  recovered via fsck after a system crash.
! 
! 
!  I discovered this posting :
! 
!  

[OpenAFS] root.afs gone, what now?

2004-12-02 Thread Gabe\\
Hello,
 I had the RAID subsystem that my root.afs volume was on crash. I'll be 
rebuilding that array. In the mean time is there a way to mount /afs. 
root.afs was the mount point for /afs, so none of the other mountpoints 
are valid. Without  the volume online I can't even rename it. Is there a 
way to make the rest of my volumes available

P.S. I had a RAID 5 with 8 disks in it, and apparently 2 of them 
crashed. Does anybody know of RAID data recovery specialists.

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


Re: [OpenAFS] root.afs gone, what now?

2004-12-02 Thread Chris Huebsch
On Thu, 2 Dec 2004, Gabe\ wrote:
I had the RAID subsystem that my root.afs volume was on crash. I'll be 
rebuilding that array. In the mean time is there a way to mount /afs. 
root.afs was the mount point for /afs, so none of the other mountpoints are 
valid. Without  the volume online I can't even rename it. Is there a way to 
make the rest of my volumes available
You can force afsd to mount an other volume as /afs instead of root.afs.
You can also specify an alternative mountpoint in the local filesystem.
Chris
--
Chris Huebschwww.huebsch-gemacht.de | TU Chemmnitz, Informatik, RNVS
GPG-Encrypted mail welcome! ID:7F2B4DBA |   Str. d. Nationen 62, B204
 Chemnitzer Linux-Tage 2005, 5.-6.Maerz |   D-09107 Chemnitz
http://chemnitzer.linux-tage.de/|  +49 371 531-1377, Fax -1803
___
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info