Re: [OpenAFS] How to stop the access to an AFS volume ?
On Wednesday 27 October 2004 19:57, Jeffrey Hutzelman wrote: On Wednesday, October 27, 2004 09:26:49 +0200 giovanni bracco In my AFS cell many volumes have an anomalous Vol ID: it can be seen in the previous example: ID=2258391753 Ow. I didn't notice that until you pointed it out. I'm not sure I want to know how you got such large volume ID's. we haven't not understood that; it happened quite long ago, so it means we have a substantial numer of volumes with anomalous ID number. Now I would like to go back to a normal situation, so that I can use OpenAFS software on file server. To attain this I have to convert volumes with anomalous Vol ID into standard volumes and I have seen that I can do that by a vos dump and vos restore sequence. You can, but you should be aware that anytime a volume ID is needed for a new volume and you didn't provide one (and there are cases where you _cannot_ provide one, such as with the temporary ID's used during volume moves), an ID is allocated by asking the vlserver for the next available volume ID. This is managed using a counter kept in the VLDB, so if you want to stop having huge volume ID's, you will need some way to reset the counter. I do not believe there is currently any interface for this, which means you'll need to either write some code, convince someone else to do so, or manually modify the database (rather perilous). Yes, I have looked into that. I have seen that the relevant value is the value MaxVolumeId which can be retrieved giving on the dbserver the command: vldb_check -vheader /usr/afs/db/vldb.DB0 I have also understood that the exact meaning of MaxVolumeId is the volume ID for the next volume to be created. I have also located the position in the vldb.DB0 file where the value MaxVolumeId is stored and I have prepared a script to change it by using xxd and sed utility programs. It works nicely. I have tried it on a test cell and I am confident to be able to apply it on our production cell. On the test cell have selected the machine which is the sync site and I have run on that a script which does the following: 1) stop the vlserver 2) apply the patch on vldb.DB0 3) restart the vlserver All that takes just a few seconds, so soon after the restart the same dbserver is again the sync site for vldb. At that point when a new volume is created it is created with the new good id and the value of MaxVolumeId is updated on all the other dbservers. I have also noticed, it may be obvious of course, that just changing the MaxVolumeId in the vldb.DB0 does not triggers the update on the other dbservers. The update happens only when a new volume is created. Of course I can also stop all the vlservers, patch all the vldb.DB0, and restart them but I don't think is really necessary. I would like to be sure that any user is not able to make any modification to a selected volume while the vos dump and vos restore sequence is in progress and that is the reason to look for a off-line feature. Alas the vos offline command seems not to be what I was looking for. I do not envy you the problem you have on your hands. Changing volume ID's is not going to be transparent no matter what you do -- clients cache name-to-ID lookups, so once you renumber a volume any clients that care will have to do an 'fs checkv' in order to notice the change -- and I'm not positive even that will work (it should be easy to test). I will make tests on all that: thank you for pointing out that kind of problems. However, I do think you can get the effect you want, in one of at least acouple of ways. They're both going to involve building some stuff of your own... (1) Build yourself a patched copy of vos in which 'vos dump' leaves the volume offline after dumping it. This is a relatively simple change in src/volser/vsprocs.c:UV_DumpVolume(). Just above the error_exit: label, you want to insert a call to AFSVolSetFlags() to set the volume's flags so it stays offline after the transaction. You can copy the relevant call from UV_SetVolume(); you want the third parameter to be VTOutOfService. With this approach, the volume will go offline when you start the dump, and will stay that way after the dump is complete. As with 'vos offline', the state is temporary, so if the fileserver restarts the volume will go online again. (2) Build the vol-bless and vol-unbless utilities, which allow you to manipulate the persistent Blessed bit on a volume. Unblessing a volume will take it out of service indefinitely. You should still be able to dump and restore the volume without problems. The state of the blessed bit is recorded in the volume dump, so the newly-restored volume may have to be manually blessed before it will be available. The downside here is that vol-bless/vol-unbless must be run on the fileserver containing the volume whose blessed bit you want to manipulate. Also, while these utilities
[OpenAFS] Unable to authenticate to AFS because internal error encountered in kaserver.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I compiled openafs 1.3.73 with SuSE Linux 9.1 (Kernel 2.6.5-7.111-smp). afsd starts and I can see /afs/... But if I do a klog: Unable to authenticate to AFS because internal error encountered in kaserver. No entry in server logs All old Linux, Solaris and Windows clients are working. Server version is : OpenAFS 1.2.11 built 2004-01-13 Ulf -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBgLBC8cc/MGdmyloRAnh0AJ9IvJ3mjaAFT32sCOrXQUhNMle02wCgunN8 BnEdPhUxoAYEjTTFK5IyZV4= =SWhv -END PGP SIGNATURE- ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Unable to authenticate to AFS because internal error encountered in kaserver.
I compiled openafs 1.3.73 with SuSE Linux 9.1 (Kernel 2.6.5-7.111-smp). afsd starts and I can see /afs/... But if I do a klog: Unable to authenticate to AFS because internal error encountered in kaserver. That's interesting. I get the same error with the FreeBSD client built from cvs head yesterday. ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
RE: [OpenAFS] Installation instructions for openafs client?
Thanks much. I had rh9.0 reinstalled and was successfully able to install and start afs client. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Derek Atkins Sent: Friday, October 15, 2004 8:47 AM To: Saundra Saylor Cc: [EMAIL PROTECTED] Subject: Re: [OpenAFS] Installation instructions for openafs client? You're clearly not running RH9 with a stock kernel. There are no RPMs for any 2.6-based systems (at least there are no offical rpms). -derek Saundra Saylor [EMAIL PROTECTED] writes: I did that and then tried to start afs client (/etc/init.d/afs start) and I get this error: open /proc/ksyms: No such file or directory Did not find matching module in SymTable AFS module /usr/vice/etc/modload/libafs-2.6.5-1.358smp.mp.o does not exist. Not starting AFS. Does anyone know what I'm missing? Thanks. -Original Message- From: Derek Atkins [mailto:[EMAIL PROTECTED] Sent: Thursday, October 14, 2004 6:13 PM To: Saundra Saylor Cc: [EMAIL PROTECTED] Subject: Re: [OpenAFS] Installation instructions for openafs client? Download the RH9 RPMS and run rpm -Uvh openafs-*.rpm -derek Saundra Saylor [EMAIL PROTECTED] writes: Hi, Can someone point me to a detailed set of instructions for intalling openafs client (1.2.10 or 1.2.11) on RedHat Linux 9? -- 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 -- 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 ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
[OpenAFS] IPUT Bad refCount 0 on inode 0xf8abadb8 in openafs-1.2.11
I've had this happen twice now on an SMP machine (debian 2.4.27 kernel, 1.2.11 openafs packages from debian sarge) Is this a known bug that's fixed in a newer version? It looks like an SMP race condition to me. IPUT Bad refCount 0 on inode 0xf8abadb8 Unable to handle kernel paging request at virtual address printing eip: f8973b10 *pde = 4063 *pte = Oops: 0002 CPU:1 EIP:0010:[f8973b10]Tainted: PF EFLAGS: 00010282 eax: 0028 ebx: f8abadb8 ecx: 0002 edx: 0001 esi: f89a0c44 edi: f8ab0c94 ebp: d1e34000 esp: d1e35f18 ds: 0018 es: 0018 ss: 0018 Process imapd (pid: 1011, stackpage=d1e35000) Stack: f89976c0 f8abadb8 f8983340 d1e34000 f8ab0c04 f89a0c44 f8980168 f89976c0 f8abadb8 f8983340 cbd5d440 cbd5d440 f8abadb8 c015c93b f8abadb8 f8abadb8 f8ab0c04 c0153d66 cbd5d440 cbd5d440 cbd5d440 Call Trace:[f89976c0] [f8983340] [f89a0c44] [f8980168] [f89976c0] [f8983340] [c015c93b] [c0153d66] [c0153f1b] [c0108efb] Code: c6 05 ff ff ff ff 2a 83 c4 1c c3 90 8d 74 26 00 b8 02 8e 99 ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] IPUT Bad refCount 0 on inode 0xf8abadb8 in openafs-1.2.11
On Thu, 28 Oct 2004, Troy Benjegerdes wrote: I've had this happen twice now on an SMP machine (debian 2.4.27 kernel, 1.2.11 openafs packages from debian sarge) Is this a known bug that's fixed in a newer version? It looks like an SMP race condition to me. IPUT Bad refCount 0 on inode 0xf8abadb8 The below would be more useful if you ran it through ksymoops. In particular, nothing about the error message in the line above is useful; However, it's not fixed in 1.2.x, and may be fixed in 1.3.x. Unable to handle kernel paging request at virtual address printing eip: f8973b10 *pde = 4063 *pte = Oops: 0002 CPU:1 EIP:0010:[f8973b10]Tainted: PF EFLAGS: 00010282 eax: 0028 ebx: f8abadb8 ecx: 0002 edx: 0001 esi: f89a0c44 edi: f8ab0c94 ebp: d1e34000 esp: d1e35f18 ds: 0018 es: 0018 ss: 0018 Process imapd (pid: 1011, stackpage=d1e35000) Stack: f89976c0 f8abadb8 f8983340 d1e34000 f8ab0c04 f89a0c44 f8980168 f89976c0 f8abadb8 f8983340 cbd5d440 cbd5d440 f8abadb8 c015c93b f8abadb8 f8abadb8 f8ab0c04 c0153d66 cbd5d440 cbd5d440 cbd5d440 Call Trace:[f89976c0] [f8983340] [f89a0c44] [f8980168] [f89976c0] [f8983340] [c015c93b] [c0153d66] [c0153f1b] [c0108efb] Code: c6 05 ff ff ff ff 2a 83 c4 1c c3 90 8d 74 26 00 b8 02 8e 99 ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] How to stop the access to an AFS volume ?
On Thursday, October 28, 2004 08:54:51 +0200 giovanni bracco [EMAIL PROTECTED] wrote: On the test cell have selected the machine which is the sync site and I have run on that a script which does the following: 1) stop the vlserver 2) apply the patch on vldb.DB0 3) restart the vlserver All that takes just a few seconds, so soon after the restart the same dbserver is again the sync site for vldb. OK. That will work as long as you keep the server down for a short enough time that it is not possible for another server to win the coordinator election. If another site becomes coordinator, it will relabel the database and your change will not take effect even if there were no changes to the contents of the VLDB. I have also noticed, it may be obvious of course, that just changing the MaxVolumeId in the vldb.DB0 does not triggers the update on the other dbservers. The update happens only when a new volume is created. Yes; the update will happen only when the database version changes. You can insure that the update will happen right away by bumping the database version at the same time you make the other change. The version consists of an epoch and sequence number, and is part of the data stored in vldb.DBSYS1. The option (2) seems more attractive to me and I think it can be a very usefull utility - it is exactely what I was looking for - so if you can find some time I am very interested in having that! No problem; I'll try to do that shortly. -- Jeffrey T. Hutzelman (N3NHS) [EMAIL PROTECTED] Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Pro's Con's of /usr/local on AFS....
On Wednesday, October 27, 2004 12:37:52 -0400 Derrick J Brashear [EMAIL PROTECTED] wrote: On Wed, 27 Oct 2004, Derek Atkins wrote: Jim Rees [EMAIL PROTECTED] writes: 3. (Optional) Create a symbolic link to a shortened cell name, to reduce the length of pathnames for users in the local cell. For example, in the abc.com cell, /afs/abc is a link to /afs/abc.com. That really needs to be removed from the documentation. Why? It's extremely useful. I like using /afs/athena, /afs/dev, /afs/sipb Which cell is /afs/cs? Mine, obviously. :-) But that doesn't make tab-completion work for me. Seriously, having short-name aliases in /afs is convenient for typing commands interactively, but such names should _never_ be used in any kind of reference that is expected to be portable. Don't use them in scripts, or programs, or symlinks, or email messages, or IM, or anyplace else where they might be used other than on your workstation the way it looks right now. Otherwise you _will_ regret it later. -- Jeff ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Pro's Con's of /usr/local on AFS....
Jim Rees wrote: Mount points is worse. At least with a symlink you can pwd and get a correct global name. But if you are going through a local mount point, that won't work. Ken Hornstein and I checked the Unix dynamic roots mode. It supports a static symlink like functionality through the CellAlias file. This allows you to name/value pair which points to a complex path. Symlinks can also be created on the fly for the length of the current session. For Windows, I have now added the ability to use the symlink.exe tool to create symlinks to directories and files. These will be maintained in the registry to survive service session restart. Jeffrey Altman smime.p7s Description: S/MIME Cryptographic Signature
[OpenAFS] win32 client 1.3.73
Hello, I have been running OpenAFS 1.2.10 on redhat 8 for sometime with linux/windows(1.2.10) clients. When I tried the 1.3.73 client on XP I experienced some difficulty. I have our entire cell (neuro.ucsd.edu) mounted to /afs, NOT /afs/neuro.ucsd.edu. I believe this is confusing the client. After a successful install, and successfully obtaining tokens, any attempt to view the mapped drive reveal only an empty directory named neuro.ucsd.edu. Is there some way to force the client to recognize my cell setup? --Gabe Castillo ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] win32 client 1.3.73
Gabe\ wrote: Hello, I have been running OpenAFS 1.2.10 on redhat 8 for sometime with linux/windows(1.2.10) clients. When I tried the 1.3.73 client on XP I experienced some difficulty. I have our entire cell (neuro.ucsd.edu) mounted to /afs, NOT /afs/neuro.ucsd.edu. I believe this is confusing the client. After a successful install, and successfully obtaining tokens, any attempt to view the mapped drive reveal only an empty directory named neuro.ucsd.edu. Is there some way to force the client to recognize my cell setup? --Gabe Castillo You have not provided enough information for us to help you. First if you have not already read the afs-install-notes.txt file which is posted with the OpenAFS for Windows installers I suggest you do so. Pay attention to the notes on Freelance mode and the use of Kerberos 5 as tokens (assuming you have installed KFW). Are you mounting /afs to the root.cell volume or the root.afs volume on Linux? Are you using Freelance mode or not? What have you added to the CellServDB file for your cell? If you are using Freelance mode, then Windows will map \\AFS\neuro.ucsd.edu to the root.cell volume on the neuro.ucsd.edu cell. If that volume is empty, then you will not see any data. You can manually modify the mount point to refer to root.afs using the fs mkmount and fs rmmount commands. If you are not using Freelance, then Windows will mount the root.afs volume of the default cell. Jeffrey Altman smime.p7s Description: S/MIME Cryptographic Signature
