From xud@ihep.ac.cn Thu Apr 1 03:33:07 2010 From: xud@ihep.ac.cn (=?gb2312?B?0O22rA==?=) Date: Thu, 1 Apr 2010 10:33:07 +0800 Subject: [OpenAFS] volume 536871264 is busy or server is down, recheck Message-ID: <201004011033061568426@ihep.ac.cn> This is a multi-part message in MIME format. --=====003_Dragon421077404754_===== Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit Hi, I want to know how many parallel read requests for one volume at the same time? or how many parallel read requests for one replication volume at the same time? In our afs system, there are about one hundred people to read a volume parallelly, and each people will issus about 500 read requests. I found the afs client's /var/log/message file often appear some error information, such as "volume 536871264 is busy or server is down, recheck ". so, I want to know its reason. Thank you! With best regards ! Yours sincerely Dong xu --=====003_Dragon421077404754_===== Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: 7bit
Hi,
 
I want to know how many parallel  read requests for one volume at the same time? or how many parallel read requests for one replication volume at the same time?
 
In our afs system, there are about one hundred people to read a volume parallelly, and each people will issus about 500 read requests. I found the afs client's /var/log/message file often appear  some error information, such as "volume 536871264 is busy or server is down, recheck ".
 
so, I want to know its reason.
 
Thank you!
 

With best regards !

 

Yours sincerely

 

Dong xu

--=====003_Dragon421077404754_=====-- From adeason@sinenomine.net Thu Apr 1 04:58:01 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Wed, 31 Mar 2010 22:58:01 -0500 Subject: [OpenAFS] Re: volume 536871264 is busy or server is down, recheck References: <201004011033061568426@ihep.ac.cn> Message-ID: <20100331225801.75bc666f.adeason@sinenomine.net> On Thu, 1 Apr 2010 10:33:07 +0800 "许冬" wrote: > Hi, > > I want to know how many parallel read requests for one volume at the > same time? or how many parallel read requests for one replication > volume at the same time? There is no real useful answer for that. There is a limit, however, to the number of outstanding requests on a server (described below). If 100 requests in parallel is your only load on that server, though, the server should be able to handle that just fine. > In our afs system, there are about one hundred people to read a > volume parallelly, and each people will issus about 500 read > requests. Are these on different AFS clients, or all on the same one? > I found the afs client's /var/log/message file often appear some > error information, such as "volume 536871264 is busy or server is > down, recheck ". > > so, I want to know its reason. Do you mean the message "Waiting for busy volume 536871264"? There are a number of reasons for that; only one I can think of is caused by load. Is there anything in FileLog or VolserLog around the time that you see these messages? I believe it is possible to get this message if the server is overloaded (possibly for a long enough period of time). If the number of outstanding calls waiting for a servicing thread ("calls waiting") exceeds a certain threshold, the client will get an error that can result in that message. This threshold is by default the -rxpck setting multiplied by 3/2. The default -rxpck setting is 150 (200 for -L), so the default threshold is around 225 (or 300 for -L). You can see how many calls are waiting for a thread with 'rxdebug '. For example: % rxdebug 192.168.1.100 Trying 192.168.1.100 (port 7000): Free packets: 265, packet reclaims: 0, calls: 0, used FDs: 34 not waiting for packets. 0 calls waiting for a thread 11 threads are idle Done. shows that there are "0 calls waiting for a thread". -- Andrew Deason adeason@sinenomine.net From jaltman@secure-endpoints.com Thu Apr 1 05:55:27 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Thu, 01 Apr 2010 00:55:27 -0400 Subject: [OpenAFS] volume 536871264 is busy or server is down, recheck In-Reply-To: <201004011033061568426@ihep.ac.cn> References: <201004011033061568426@ihep.ac.cn> Message-ID: <4BB4273F.2090809@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms090908040804010104090601 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 3/31/2010 10:33 PM, =E8=AE=B8=E5=86=AC wrote: > Hi, > =20 > I want to know how many parallel read requests for one volume at the > same time? or how many parallel read requests for one replication volum= e > at the same time? > =20 > In our afs system, there are about one hundred people to read a volume > parallelly, and each people will issus about 500 read requests. I found= > the afs client's /var/log/message file often appear some error > information, such as "volume 536871264 is busy or server is down, reche= ck ". > =20 > so, I want to know its reason. > =20 > Thank you! > =20 >=20 > With best regards ! >=20 > =20 >=20 > Yours sincerely >=20 > =20 >=20 > Dong xu >=20 Which operating system? Which OpenAFS client version and which server version? Are the clients only reading from the volume or are they writing as well?= Jeffrey Altman --------------ms090908040804010104090601 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MDEwNDU1MjdaMCMGCSqGSIb3DQEJBDEWBBQKdbpS 4Q9qIuDU9QYggLucQk5jwjBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAI8M0izFg8PlY70AJ1tJO89h+uo7WjCjxNCh 3VucK79k1qxTBf/Fokb4odMEnfSO3MMuVw5usrkQukpzx7qRgHVydkHkPIOXNUT+EZ8p0zM9 6BW1pW36crJfAG2wOO38yI5PJrIIjQLxZGw+cXiIUCHMP/H0Au6+POznZukc2t7uFvKNc0f0 G5vCnzD/fBA3//p0x+jQi96oxVgckTiJfD50VFmkaQM3LToOnce4pAeG41MRRnKhwy6Zbqow 8z4afgq1vBuwfz5pAPKw6OpyitT+oJ+5xruaGmYahWWrJx0BYsy04Xm7DHA7QbGb3bn4GRki T2ViDKPwwNdzMHLKplAAAAAAAAA= --------------ms090908040804010104090601-- From bbense@slac.stanford.edu Thu Apr 1 20:44:23 2010 From: bbense@slac.stanford.edu (Booker Bense) Date: Thu, 1 Apr 2010 12:44:23 -0700 (PDT) Subject: [OpenAFS] volume 536871264 is busy or server is down, recheck In-Reply-To: <4BB4273F.2090809@secure-endpoints.com> References: <201004011033061568426@ihep.ac.cn> <4BB4273F.2090809@secure-endpoints.com> Message-ID: On Thu, 1 Apr 2010, Jeffrey Altman wrote: > On 3/31/2010 10:33 PM, ?? wrote: >> Hi, >> >> I want to know how many parallel read requests for one volume at the >> same time? or how many parallel read requests for one replication volume >> at the same time? >> >> In our afs system, there are about one hundred people to read a volume >> parallelly, and each people will issus about 500 read requests. I found >> the afs client's /var/log/message file often appear some error >> information, such as "volume 536871264 is busy or server is down, recheck ". >> Our experience is that AFS and a large batch farm is a denial of service waiting to happen for rw volumes. What happens is that each batch process registers a callback for volume it is writing to and eventually the server gets starved for available threads and all the volumes served by that server suffer performance hits. Essentially the read requests are limited by the number of threads on the server for the volume. We have a constant user education problem with this, especially since the tipping point doesn't get triggered until the user is sure everything is working and "scales up" their runs to several hundred simultaneous batch jobs. In theory a read only replica volume should not be nearly as resource intensive. However, we have found this is rarely the case. I suspect your real problem is that the jobs are opening dot files or configuration/logging files in some volume that is also on the same server as the volume you are reading from. Most applications have some library that assumes reading/writing to small files in the home directory will never be a problem. AFS scales really well under the assumption of many machines each accessing different volumes, it crashes and burns when the scenario switches to many machines accessing the same volume. _ Booker C. Bense From Richard.Brittain@dartmouth.edu Fri Apr 2 21:17:25 2010 From: Richard.Brittain@dartmouth.edu (Richard Brittain) Date: Fri, 2 Apr 2010 16:17:25 -0400 (EDT) Subject: [OpenAFS] Specify size reported by 'df' ? In-Reply-To: References: <201004011033061568426@ihep.ac.cn> <4BB4273F.2090809@secure-endpoints.com> Message-ID: Hi, I'm wondering if anyone has tried to customize the (fake) size reported by 'df', and specifically if anyone has looked into how hard it might be to make that configurable per-client, with something like a root-only 'fs setdfsize' ? We occasionally run into problems with the 9000000 k value when some tool wants to start dumping 10GB into AFS and decides to check first. Richard -- Richard Brittain, Research Computing Group, Kiewit Computing Services, 6224 Baker/Berry Library Dartmouth College, Hanover NH 03755 Richard.Brittain@dartmouth.edu 6-2085 From fbo2@gmx.net Sat Apr 3 09:06:02 2010 From: fbo2@gmx.net (Frank Burkhardt) Date: Sat, 3 Apr 2010 10:06:02 +0200 Subject: [OpenAFS] Specify size reported by 'df' ? In-Reply-To: References: <201004011033061568426@ihep.ac.cn> <4BB4273F.2090809@secure-endpoints.com> Message-ID: <20100403080602.GA2978@postman.alpha> Hi, On Fri, Apr 02, 2010 at 04:17:25PM -0400, Richard Brittain wrote: > Hi, > I'm wondering if anyone has tried to customize the (fake) size > reported by 'df', and specifically if anyone has looked into how hard it > might be to make that configurable per-client, with something like a > root-only > 'fs setdfsize' ? > > We occasionally run into problems with the 9000000 k value when some tool > wants to start dumping 10GB into AFS and decides to check first. I've got a similiar problem here. For MacOSX, I've to compile AFS myself - changing the free-space-constant before that. Otherwise, our beloved "Finder" refuses to copy largish data sets (which I have to move around a lot) into AFS. However, another fs subcommand might not be necessary - just increasing the reported free space to 2TiB-1Block should be sufficient since most volumes' quota is considerably smaller than that. Are there any programs known to break when reported free space is that high? Regards, Frank From shadow@gmail.com Sat Apr 3 16:34:19 2010 From: shadow@gmail.com (Derrick Brashear) Date: Sat, 3 Apr 2010 11:34:19 -0400 Subject: [OpenAFS] Specify size reported by 'df' ? In-Reply-To: <20100403080602.GA2978@postman.alpha> References: <201004011033061568426@ihep.ac.cn> <4BB4273F.2090809@secure-endpoints.com> <20100403080602.GA2978@postman.alpha> Message-ID: On Sat, Apr 3, 2010 at 4:06 AM, Frank Burkhardt wrote: > Hi, > > On Fri, Apr 02, 2010 at 04:17:25PM -0400, Richard Brittain wrote: >> Hi, >> =A0 =A0I'm wondering if anyone has tried to customize the (fake) size >> reported by 'df', and specifically if anyone has looked into how hard it >> might be to make that configurable per-client, with something like a >> root-only >> 'fs setdfsize' ? >> >> We occasionally run into problems with the 9000000 k value when some too= l >> wants to start dumping 10GB into AFS and decides to check first. > > I've got a similiar problem here. For MacOSX, I've to compile AFS myself = - > changing the free-space-constant before that. Otherwise, our beloved > "Finder" refuses to copy largish data sets (which I have to move around a > lot) into AFS. MacOS reports 1TB free for a while now. If you're trying to copy more than that in, well, let's just say I don't have a terabyte laying around to play with. From sac@cheesecake.org Sun Apr 4 12:00:17 2010 From: sac@cheesecake.org (Sidney Cammeresi) Date: Sun, 4 Apr 2010 13:00:17 +0200 Subject: [OpenAFS] Vos move/release failure Message-ID: <20100404110017.GA12901@cheesecake.org> One of my fileservers is returning errors when I try to move or release certain volumes to it. For example, ---------- $ vos ex test test 536871126 RW 2 K On-line good /vicepa RWrite 536871126 ROnly 536871133 Backup 0 MaxQuota 5000 K Creation Sun Apr 4 12:40:27 2010 Copy Sun Apr 4 12:41:53 2010 Backup Never Last Update Never RWrite: 536871126 number of sites -> 1 server good partition /vicepa RW Site $ vos move test good a bad a Failed to move data for the volume 536871126 : No such file or directory vos move: operation interrupted, cleanup in progress... clear transaction contexts move incomplete - attempt cleanup of target partition - no guarantee cleanup complete - user verify desired result ---------- All I see in VolserLog on the bad server is Sun Apr 4 12:50:09 2010 VAttachVolume: Failed to open /vicepa/V0536871126.vol (errno 2) Sun Apr 4 12:50:09 2010 1 Volser: CreateVolume: volume 536871126 (test) created Sun Apr 4 12:50:12 2010 1 Volser: Delete: volume 536871126 deleted I deleted the volume "test," and then I performed this sequence of commands to get a different failure: ---------- $ vos create bad a test Volume 536871134 created on partition /vicepa of bad $ vos addsite bad a test Added replication site bad /vicepa for volume test $ vos addsite good a test Added replication site good /vicepa for volume test $ vos release test Released volume test successfully $ vos move test bad a good a WARNING : readOnly copies still exist Volume 536871134 moved from bad /vicepa to good /vicepa $ vos release test Release failed: VOLSER: Problems encountered in doing the dump ! The volume 536871134 could not be released to the following 1 sites: bad /vicepa VOLSER: release could not be completed Error in vos release command. VOLSER: release could not be completed ---------- Does anyone have any idea what's going on here? Thanks for your suggestions. -- Sidney August Cammeresi IV http://www.cheesecake.org/sac/ From jason@rampaginggeek.com Sun Apr 4 18:14:57 2010 From: jason@rampaginggeek.com (Jason Edgecombe) Date: Sun, 04 Apr 2010 13:14:57 -0400 Subject: [OpenAFS] Vos move/release failure In-Reply-To: <20100404110017.GA12901@cheesecake.org> References: <20100404110017.GA12901@cheesecake.org> Message-ID: <4BB8C911.5010604@rampaginggeek.com> Sidney Cammeresi wrote: > One of my fileservers is returning errors when I try to move or release > certain volumes to it. For example, > > ---------- > > $ vos ex test > test 536871126 RW 2 K On-line > good /vicepa > RWrite 536871126 ROnly 536871133 Backup 0 > MaxQuota 5000 K > Creation Sun Apr 4 12:40:27 2010 > Copy Sun Apr 4 12:41:53 2010 > Backup Never > Last Update Never > > RWrite: 536871126 > number of sites -> 1 > server good partition /vicepa RW Site > $ vos move test good a bad a > > Failed to move data for the volume 536871126 > : No such file or directory > vos move: operation interrupted, cleanup in progress... > clear transaction contexts > move incomplete - attempt cleanup of target partition - no guarantee > cleanup complete - user verify desired result > > ---------- > > All I see in VolserLog on the bad server is > > Sun Apr 4 12:50:09 2010 VAttachVolume: Failed to open /vicepa/V0536871126.vol (errno 2) > Sun Apr 4 12:50:09 2010 1 Volser: CreateVolume: volume 536871126 (test) created > Sun Apr 4 12:50:12 2010 1 Volser: Delete: volume 536871126 deleted > > > > I deleted the volume "test," and then I performed this sequence of > commands to get a different failure: > > ---------- > > $ vos create bad a test > Volume 536871134 created on partition /vicepa of bad > $ vos addsite bad a test > Added replication site bad /vicepa for volume test > $ vos addsite good a test > Added replication site good /vicepa for volume test > $ vos release test > Released volume test successfully > $ vos move test bad a good a > WARNING : readOnly copies still exist > Volume 536871134 moved from bad /vicepa to good /vicepa > $ vos release test > Release failed: VOLSER: Problems encountered in doing the dump ! > The volume 536871134 could not be released to the following 1 sites: > bad /vicepa > VOLSER: release could not be completed > Error in vos release command. > VOLSER: release could not be completed > > ---------- > > Does anyone have any idea what's going on here? Thanks for your > suggestions. > What platform, OS, and fileystem do the servers run? Have you tried salvaging the servers (requires downtime), if not, run: bos salvage -server good -part /vicepa bos salvage -server bad -part /vicepa Jason From shadow@gmail.com Sun Apr 4 18:21:07 2010 From: shadow@gmail.com (Derrick Brashear) Date: Sun, 4 Apr 2010 13:21:07 -0400 Subject: [OpenAFS] Vos move/release failure In-Reply-To: <20100404110017.GA12901@cheesecake.org> References: <20100404110017.GA12901@cheesecake.org> Message-ID: On Sun, Apr 4, 2010 at 7:00 AM, Sidney Cammeresi wrote= : > One of my fileservers is returning errors when I try to move or release > certain volumes to it. =A0For example, > > ---------- > > $ vos ex test > test =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0536871126= RW =A0 =A0 =A0 =A0 =A02 K =A0On-line > =A0 =A0good /vicepa > =A0 =A0RWrite =A0536871126 ROnly =A0536871133 Backup =A0 =A0 =A0 =A0 =A00 > =A0 =A0MaxQuota =A0 =A0 =A0 5000 K > =A0 =A0Creation =A0 =A0Sun Apr =A04 12:40:27 2010 > =A0 =A0Copy =A0 =A0 =A0 =A0Sun Apr =A04 12:41:53 2010 > =A0 =A0Backup =A0 =A0 =A0Never > =A0 =A0Last Update Never > > =A0 =A0RWrite: 536871126 > =A0 =A0number of sites -> 1 > =A0 =A0 =A0 server good partition /vicepa RW Site > $ vos move test good a bad a > > Failed to move data for the volume 536871126 > =A0 : No such file or directory > vos move: operation interrupted, cleanup in progress... > clear transaction contexts > move incomplete - attempt cleanup of target partition - no guarantee > cleanup complete - user verify desired result > > ---------- > > All I see in VolserLog on the bad server is > > Sun Apr =A04 12:50:09 2010 VAttachVolume: Failed to open /vicepa/V0536871= 126.vol (errno 2) > Sun Apr =A04 12:50:09 2010 1 Volser: CreateVolume: volume 536871126 (test= ) created > Sun Apr =A04 12:50:12 2010 1 Volser: Delete: volume 536871126 deleted > > > > I deleted the volume "test," and then I performed this sequence of > commands to get a different failure: > > ---------- > > $ vos create bad a test > Volume 536871134 created on partition /vicepa of bad > $ vos addsite bad a test > Added replication site bad /vicepa for volume test > $ vos addsite good a test > Added replication site good /vicepa for volume test > $ vos release test > Released volume test successfully > $ vos move test bad a good a > WARNING : readOnly copies still exist > Volume 536871134 moved from bad /vicepa to good /vicepa > $ vos release test > Release failed: VOLSER: Problems encountered in doing the dump ! So you gave us one log. There are 2 servers in play. How about that other l= og? From sac@cheesecake.org Mon Apr 5 08:12:57 2010 From: sac@cheesecake.org (Sidney Cammeresi) Date: Mon, 5 Apr 2010 09:12:57 +0200 Subject: [OpenAFS] Re: Vos move/release failure In-Reply-To: References: <20100404110017.GA12901@cheesecake.org> Message-ID: <20100405071257.GB18095@cheesecake.org> On Sun, 04 Apr 2010 at 13.21.07 -0400, Derrick Brashear wrote: > On Sun, Apr 4, 2010 at 7:00 AM, Sidney Cammeresi w= rote: > > One of my fileservers is returning errors when I try to move or relea= se > > certain volumes to it. =A0For example, > > > > ---------- > > > > $ vos ex test > > test =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A053687= 1126 RW =A0 =A0 =A0 =A0 =A02 K =A0On-line > > =A0 =A0good /vicepa > > =A0 =A0RWrite =A0536871126 ROnly =A0536871133 Backup =A0 =A0 =A0 =A0 = =A00 > > =A0 =A0MaxQuota =A0 =A0 =A0 5000 K > > =A0 =A0Creation =A0 =A0Sun Apr =A04 12:40:27 2010 > > =A0 =A0Copy =A0 =A0 =A0 =A0Sun Apr =A04 12:41:53 2010 > > =A0 =A0Backup =A0 =A0 =A0Never > > =A0 =A0Last Update Never > > > > =A0 =A0RWrite: 536871126 > > =A0 =A0number of sites -> 1 > > =A0 =A0 =A0 server good partition /vicepa RW Site > > $ vos move test good a bad a > > > > Failed to move data for the volume 536871126 > > =A0 : No such file or directory > > vos move: operation interrupted, cleanup in progress... > > clear transaction contexts > > move incomplete - attempt cleanup of target partition - no guarantee > > cleanup complete - user verify desired result > > > > ---------- > > > > All I see in VolserLog on the bad server is > > > > Sun Apr =A04 12:50:09 2010 VAttachVolume: Failed to open /vicepa/V053= 6871126.vol (errno 2) > > Sun Apr =A04 12:50:09 2010 1 Volser: CreateVolume: volume 536871126 (= test) created > > Sun Apr =A04 12:50:12 2010 1 Volser: Delete: volume 536871126 deleted > > > > > > > > I deleted the volume "test," and then I performed this sequence of > > commands to get a different failure: > > > > ---------- > > > > $ vos create bad a test > > Volume 536871134 created on partition /vicepa of bad > > $ vos addsite bad a test > > Added replication site bad /vicepa for volume test > > $ vos addsite good a test > > Added replication site good /vicepa for volume test > > $ vos release test > > Released volume test successfully > > $ vos move test bad a good a > > WARNING : readOnly copies still exist > > Volume 536871134 moved from bad /vicepa to good /vicepa > > $ vos release test > > Release failed: VOLSER: Problems encountered in doing the dump ! >=20 > So you gave us one log. There are 2 servers in play. How about that oth= er log? If I do the create, addsite, addsite, release sequence that I previously described, I get the following in the VolserLog on the good server: Mon Apr 5 09:05:17 2010 1 Volser: CreateVolume: volume 536871141 (test) = created Mon Apr 5 09:06:19 2010 1 Volser: Clone: Cloning volume 536871141 to new= volume 536871142 and the following in the VolserLog on the bad server: Mon Apr 5 09:06:27 2010 VAttachVolume: Failed to open /vicepa/V053687114= 2.vol (errno 2) Mon Apr 5 09:06:27 2010 1 Volser: CreateVolume: volume 536871142 (test.r= eadonly) created Regarding other suggestions I've received, I've tried running bos salvage= , which had no effect, and I have tried running vos release -v, which provi= ded this output: test RWrite: 536871141 ROnly: 536871142 RClone: 536871142 number of sites -> 3 server good partition /vicepa RW Site -- New release server good partition /vicepa RO Site -- New release server bad partition /vicepa RO Site -- Old release This is a completion of a previous release Starting transaction on cloned volume 536871142... done Updating existing ro volume 536871142 on bad ... Starting ForwardMulti from 536871142 to 536871142 on bad (full release). Failed to dump volume from clone to a ro site: : No such file or director= y The volume 536871141 could not be released to the following 1 sites: bad /vicepa VOLSER: release could not be completed Error in vos release command. VOLSER: release could not be completed --=20 Sidney August Cammeresi IV http://www.cheesecake.org/sac/ From shadow@gmail.com Mon Apr 5 12:56:19 2010 From: shadow@gmail.com (Derrick Brashear) Date: Mon, 5 Apr 2010 07:56:19 -0400 Subject: [OpenAFS] Re: Vos move/release failure In-Reply-To: <20100405071257.GB18095@cheesecake.org> References: <20100404110017.GA12901@cheesecake.org> <20100405071257.GB18095@cheesecake.org> Message-ID: On Mon, Apr 5, 2010 at 3:12 AM, Sidney Cammeresi wrote= : > On Sun, 04 Apr 2010 at 13.21.07 -0400, Derrick Brashear wrote: >> On Sun, Apr 4, 2010 at 7:00 AM, Sidney Cammeresi wr= ote: >> > One of my fileservers is returning errors when I try to move or releas= e >> > certain volumes to it. =A0For example, >> > >> > ---------- >> > >> > $ vos ex test >> > test =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0536871= 126 RW =A0 =A0 =A0 =A0 =A02 K =A0On-line >> > =A0 =A0good /vicepa >> > =A0 =A0RWrite =A0536871126 ROnly =A0536871133 Backup =A0 =A0 =A0 =A0 = =A00 >> > =A0 =A0MaxQuota =A0 =A0 =A0 5000 K >> > =A0 =A0Creation =A0 =A0Sun Apr =A04 12:40:27 2010 >> > =A0 =A0Copy =A0 =A0 =A0 =A0Sun Apr =A04 12:41:53 2010 >> > =A0 =A0Backup =A0 =A0 =A0Never >> > =A0 =A0Last Update Never >> > >> > =A0 =A0RWrite: 536871126 >> > =A0 =A0number of sites -> 1 >> > =A0 =A0 =A0 server good partition /vicepa RW Site >> > $ vos move test good a bad a >> > >> > Failed to move data for the volume 536871126 >> > =A0 : No such file or directory >> > vos move: operation interrupted, cleanup in progress... >> > clear transaction contexts >> > move incomplete - attempt cleanup of target partition - no guarantee >> > cleanup complete - user verify desired result >> > >> > ---------- >> > >> > All I see in VolserLog on the bad server is >> > >> > Sun Apr =A04 12:50:09 2010 VAttachVolume: Failed to open /vicepa/V0536= 871126.vol (errno 2) >> > Sun Apr =A04 12:50:09 2010 1 Volser: CreateVolume: volume 536871126 (t= est) created >> > Sun Apr =A04 12:50:12 2010 1 Volser: Delete: volume 536871126 deleted >> > >> > >> > >> > I deleted the volume "test," and then I performed this sequence of >> > commands to get a different failure: >> > >> > ---------- >> > >> > $ vos create bad a test >> > Volume 536871134 created on partition /vicepa of bad >> > $ vos addsite bad a test >> > Added replication site bad /vicepa for volume test >> > $ vos addsite good a test >> > Added replication site good /vicepa for volume test >> > $ vos release test >> > Released volume test successfully >> > $ vos move test bad a good a >> > WARNING : readOnly copies still exist >> > Volume 536871134 moved from bad /vicepa to good /vicepa >> > $ vos release test >> > Release failed: VOLSER: Problems encountered in doing the dump ! >> >> So you gave us one log. There are 2 servers in play. How about that othe= r log? > > If I do the create, addsite, addsite, release sequence that I previously > described, I get the following in the VolserLog on the good server: > > Mon Apr =A05 09:05:17 2010 1 Volser: CreateVolume: volume 536871141 (test= ) created > Mon Apr =A05 09:06:19 2010 1 Volser: Clone: Cloning volume 536871141 to n= ew volume 536871142 > > and the following in the VolserLog on the bad server: > > Mon Apr =A05 09:06:27 2010 VAttachVolume: Failed to open /vicepa/V0536871= 142.vol (errno 2) > Mon Apr =A05 09:06:27 2010 1 Volser: CreateVolume: volume 536871142 (test= .readonly) created Yeah, but you're still not telling us about the source server's log during the release to the "bad" server. What appears in the good server's log at 9:06:27? What OpenAFS versions are in play, again? From sac@cheesecake.org Mon Apr 5 15:10:25 2010 From: sac@cheesecake.org (Sidney Cammeresi) Date: Mon, 5 Apr 2010 16:10:25 +0200 Subject: [OpenAFS] Re: Re: Vos move/release failure In-Reply-To: References: <20100404110017.GA12901@cheesecake.org> <20100405071257.GB18095@cheesecake.org> Message-ID: <20100405141025.GA24644@cheesecake.org> On Mon, 05 Apr 2010 at 07.56.19 -0400, Derrick Brashear wrote: > On Mon, Apr 5, 2010 at 3:12 AM, Sidney Cammeresi w= rote: > > On Sun, 04 Apr 2010 at 13.21.07 -0400, Derrick Brashear wrote: > >> On Sun, Apr 4, 2010 at 7:00 AM, Sidney Cammeresi wrote: > >> > One of my fileservers is returning errors when I try to move or re= lease > >> > certain volumes to it. =A0For example, > >> > > >> > ---------- > >> > > >> > $ vos ex test > >> > test =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A053= 6871126 RW =A0 =A0 =A0 =A0 =A02 K =A0On-line > >> > =A0 =A0good /vicepa > >> > =A0 =A0RWrite =A0536871126 ROnly =A0536871133 Backup =A0 =A0 =A0 =A0= =A00 > >> > =A0 =A0MaxQuota =A0 =A0 =A0 5000 K > >> > =A0 =A0Creation =A0 =A0Sun Apr =A04 12:40:27 2010 > >> > =A0 =A0Copy =A0 =A0 =A0 =A0Sun Apr =A04 12:41:53 2010 > >> > =A0 =A0Backup =A0 =A0 =A0Never > >> > =A0 =A0Last Update Never > >> > > >> > =A0 =A0RWrite: 536871126 > >> > =A0 =A0number of sites -> 1 > >> > =A0 =A0 =A0 server good partition /vicepa RW Site > >> > $ vos move test good a bad a > >> > > >> > Failed to move data for the volume 536871126 > >> > =A0 : No such file or directory > >> > vos move: operation interrupted, cleanup in progress... > >> > clear transaction contexts > >> > move incomplete - attempt cleanup of target partition - no guarant= ee > >> > cleanup complete - user verify desired result > >> > > >> > ---------- > >> > > >> > All I see in VolserLog on the bad server is > >> > > >> > Sun Apr =A04 12:50:09 2010 VAttachVolume: Failed to open /vicepa/V= 0536871126.vol (errno 2) > >> > Sun Apr =A04 12:50:09 2010 1 Volser: CreateVolume: volume 53687112= 6 (test) created > >> > Sun Apr =A04 12:50:12 2010 1 Volser: Delete: volume 536871126 dele= ted > >> > > >> > > >> > > >> > I deleted the volume "test," and then I performed this sequence of > >> > commands to get a different failure: > >> > > >> > ---------- > >> > > >> > $ vos create bad a test > >> > Volume 536871134 created on partition /vicepa of bad > >> > $ vos addsite bad a test > >> > Added replication site bad /vicepa for volume test > >> > $ vos addsite good a test > >> > Added replication site good /vicepa for volume test > >> > $ vos release test > >> > Released volume test successfully > >> > $ vos move test bad a good a > >> > WARNING : readOnly copies still exist > >> > Volume 536871134 moved from bad /vicepa to good /vicepa > >> > $ vos release test > >> > Release failed: VOLSER: Problems encountered in doing the dump ! > >> > >> So you gave us one log. There are 2 servers in play. How about that = other log? > > > > If I do the create, addsite, addsite, release sequence that I previou= sly > > described, I get the following in the VolserLog on the good server: > > > > Mon Apr =A05 09:05:17 2010 1 Volser: CreateVolume: volume 536871141 (= test) created > > Mon Apr =A05 09:06:19 2010 1 Volser: Clone: Cloning volume 536871141 = to new volume 536871142 > > > > and the following in the VolserLog on the bad server: > > > > Mon Apr =A05 09:06:27 2010 VAttachVolume: Failed to open /vicepa/V053= 6871142.vol (errno 2) > > Mon Apr =A05 09:06:27 2010 1 Volser: CreateVolume: volume 536871142 (= test.readonly) created >=20 > Yeah, but you're still not telling us about the source server's log > during the release to the "bad" server. What appears in the good > server's log at 9:06:27? >=20 > What OpenAFS versions are in play, again? Sorry for omitting the OpenAFS versions. Initially the good machine was running 1.4.2, but I have upgraded it to Lenny and the corresponding package of 1.4.7. The bad machine is also running Lenny's 1.4.7. There was nothing in the good server's log at 9:06:27. Testing again, I see on good: VolserLog Mon Apr 5 16:02:28 2010 1 Volser: Clone: Recloning volume 536871151 to v= olume 536871152 FileLog Mon Apr 5 16:02:28 2010 fssync: volume 536871152 restored; breaking all = call backs And on bad: VolserLog Mon Apr 5 16:02:36 2010 VAttachVolume: Failed to open /vicepa/V053687115= 2.vol (errno 2) Mon Apr 5 16:02:36 2010 1 Volser: CreateVolume: volume 536871152 (test.r= eadonly) created There is nothing in the good server's logs at 16:02:36. --=20 Sidney August Cammeresi IV http://www.cheesecake.org/sac/ From shadow@gmail.com Mon Apr 5 15:17:51 2010 From: shadow@gmail.com (Derrick Brashear) Date: Mon, 5 Apr 2010 10:17:51 -0400 Subject: [OpenAFS] Re: Re: Vos move/release failure In-Reply-To: <20100405141025.GA24644@cheesecake.org> References: <20100404110017.GA12901@cheesecake.org> <20100405071257.GB18095@cheesecake.org> <20100405141025.GA24644@cheesecake.org> Message-ID: >> What OpenAFS versions are in play, again? > > Sorry for omitting the OpenAFS versions. =A0Initially the good machine > was running 1.4.2, but I have upgraded it to Lenny and the corresponding > package of 1.4.7. =A0The bad machine is also running Lenny's 1.4.7. It sounds offhand familiar, like something we fixed, but 1.4.7 is quite old. Not as elderly as 1.4.2, but... From sac@cheesecake.org Mon Apr 5 16:11:54 2010 From: sac@cheesecake.org (Sidney Cammeresi) Date: Mon, 5 Apr 2010 17:11:54 +0200 Subject: [OpenAFS] Re: Vos move/release failure In-Reply-To: References: <20100404110017.GA12901@cheesecake.org> <20100405071257.GB18095@cheesecake.org> <20100405141025.GA24644@cheesecake.org> Message-ID: <20100405151154.GA27158@cheesecake.org> On Mon, 05 Apr 2010 at 10.17.51 -0400, Derrick Brashear wrote: > > > What OpenAFS versions are in play, again? > >=20 > > Sorry for omitting the OpenAFS versions. =A0Initially the good > > machine was running 1.4.2, but I have upgraded it to Lenny and the > > corresponding package of 1.4.7. =A0The bad machine is also running > > Lenny's 1.4.7. >=20 > It sounds offhand familiar, like something we fixed, but 1.4.7 is > quite old. Not as elderly as 1.4.2, but... Hmm, I upgraded both servers in question to 1.4.11 from backports.org and am still seeing the same issue. --=20 Sidney August Cammeresi IV http://www.cheesecake.org/sac/ From adeason@sinenomine.net Mon Apr 5 17:49:13 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Mon, 5 Apr 2010 11:49:13 -0500 Subject: [OpenAFS] Re: Vos move/release failure References: <20100404110017.GA12901@cheesecake.org> Message-ID: <20100405114913.e22d190e.adeason@sinenomine.net> On Sun, 4 Apr 2010 13:00:17 +0200 Sidney Cammeresi wrote: > One of my fileservers is returning errors when I try to move or release > certain volumes to it. For example, Try 'vos dump'ing a volume from the good server, and 'vos restore'ing it to the bad server (restore it as some new volume). What happens? I assume one of those will fail with 'No such file or directory', probably at the 'vos restore' step. Also, neither of these machines has something silly like a 127.foo entry in /etc/hosts for their hostname, do they? -- Andrew Deason adeason@sinenomine.net From shadow@gmail.com Mon Apr 5 18:31:08 2010 From: shadow@gmail.com (Derrick Brashear) Date: Mon, 5 Apr 2010 13:31:08 -0400 Subject: [OpenAFS] Re: Vos move/release failure In-Reply-To: <20100405114913.e22d190e.adeason@sinenomine.net> References: <20100404110017.GA12901@cheesecake.org> <20100405114913.e22d190e.adeason@sinenomine.net> Message-ID: On Mon, Apr 5, 2010 at 12:49 PM, Andrew Deason wro= te: > On Sun, 4 Apr 2010 13:00:17 +0200 > Sidney Cammeresi wrote: > >> One of my fileservers is returning errors when I try to move or release >> certain volumes to it. =A0For example, > > Try 'vos dump'ing a volume from the good server, and 'vos restore'ing it > to the bad server (restore it as some new volume). What happens? I > assume one of those will fail with 'No such file or directory', probably > at the 'vos restore' step. > > Also, neither of these machines has something silly like a 127.foo entry > in /etc/hosts for their hostname, do they? His last reply was private. That was it. From sabah.salih@hep.manchester.ac.uk Mon Apr 5 18:35:06 2010 From: sabah.salih@hep.manchester.ac.uk (sabah s. salih) Date: Mon, 5 Apr 2010 18:35:06 +0100 Subject: [OpenAFS] knfs Message-ID: <75828F93B3A771439C6F9F4B67CFE58B0477D7108C@exchange.hep.manchester.ac.uk> Dear All, Is knfs is still supported by openafs. Thanks, Sabah. >From Sabah Salih The School of Physics and Astronomy, The University of Manchester, Schuster Laboratory, Brunswick Street, Manchester M13 9PL. Tel: +44 1612754171 or x4171 E-mail: sabah.salih@hep.manchester.ac.uk= From adeason@sinenomine.net Mon Apr 5 18:54:45 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Mon, 5 Apr 2010 12:54:45 -0500 Subject: [OpenAFS] Re: Vos move/release failure References: <20100404110017.GA12901@cheesecake.org> <20100405114913.e22d190e.adeason@sinenomine.net> Message-ID: <20100405125445.096cb61c.adeason@sinenomine.net> On Mon, 5 Apr 2010 13:31:08 -0400 Derrick Brashear wrote: > On Mon, Apr 5, 2010 at 12:49 PM, Andrew Deason > wrote: > > > Also, neither of these machines has something silly like a 127.foo > > entry in /etc/hosts for their hostname, do they? > > His last reply was private. That was it. Would it be feasible for viced to refuse to register addrs in 127/8, or at least yell at you or something? -- Andrew Deason adeason@sinenomine.net From shadow@gmail.com Mon Apr 5 19:16:29 2010 From: shadow@gmail.com (Derrick Brashear) Date: Mon, 5 Apr 2010 14:16:29 -0400 Subject: [OpenAFS] Re: Vos move/release failure In-Reply-To: <20100405125445.096cb61c.adeason@sinenomine.net> References: <20100404110017.GA12901@cheesecake.org> <20100405114913.e22d190e.adeason@sinenomine.net> <20100405125445.096cb61c.adeason@sinenomine.net> Message-ID: On Mon, Apr 5, 2010 at 1:54 PM, Andrew Deason wrote: > On Mon, 5 Apr 2010 13:31:08 -0400 > Derrick Brashear wrote: > >> On Mon, Apr 5, 2010 at 12:49 PM, Andrew Deason >> wrote: >> >> > Also, neither of these machines has something silly like a 127.foo >> > entry in /etc/hosts for their hostname, do they? >> >> His last reply was private. That was it. > > Would it be feasible for viced to refuse to register addrs in 127/8, or > at least yell at you or something? we had people using other-than-127.0.0.1 complain once about that. yelling otoh seems plausible. From shadow@gmail.com Mon Apr 5 19:17:25 2010 From: shadow@gmail.com (Derrick Brashear) Date: Mon, 5 Apr 2010 14:17:25 -0400 Subject: [OpenAFS] knfs In-Reply-To: <75828F93B3A771439C6F9F4B67CFE58B0477D7108C@exchange.hep.manchester.ac.uk> References: <75828F93B3A771439C6F9F4B67CFE58B0477D7108C@exchange.hep.manchester.ac.uk> Message-ID: On Mon, Apr 5, 2010 at 1:35 PM, sabah s. salih wrote: > Dear All, > =A0 =A0 =A0 =A0 =A0 =A0Is knfs is still supported by openafs. If it works, it works. You need OpenAFS 1.5 and certain Linux versions, or any OpenAFS with Solaris. YMMV. From crestani@informatik.uni-tuebingen.de Tue Apr 6 08:10:44 2010 From: crestani@informatik.uni-tuebingen.de (Marcus Crestani) Date: Tue, 06 Apr 2010 09:10:44 +0200 Subject: [OpenAFS] Documentation for MacOSX Preference Pane in 1.4.12 Message-ID: I have trouble getting the new maintenance release 1.4.12 working properly on MacOSX 10.6.3. We use Kerberos 5 to authenticate and our user's homes are stored in AFS, so we need to get a Token at login time. We have a working setup with OpenAFS 1.4.11 that obtains a Kerberos Ticket during login and uses the loginwindow's LoginHook to convert the Kerberos Ticket to an AFS Token. After I've installed 1.4.12, this does not seem work any longer. On a first login attempt, I do not get an token at login time. To get one, I have to logout and login again. But then, the Finder process stalls for a couple of minutes with a spinning wheel. Something is terribly wrong here. I have the feeling that the new Preference Pane and our previous solution do not work together. To understand what happens, I could use some insight on the new Preference Pane. Is there some documentation? Especially, it would be useful to have answers to the following questions: - What is the purpose of the "Backgrounder" Launch Agent it.infn.lnf.network.AFSBackgrounder.plist? How is it connected to the Preference Pane? - Where does the Preference Pane store its settings? - What happens in the background when I check/uncheck the several options like "Get Krb5 credential at login", "Use aklog", "get credential at login time", "Backgrounder"? - Where does the stuff under the "Parameter" tab get stored? How does the AFS startup get these values? I'd appreciate any help, either ideas concerning my described problems or answers to my questions that should help me figuring things out. Thanks in advance! -- Marcus From lists@drewstud.com Tue Apr 6 14:11:35 2010 From: lists@drewstud.com (lists@drewstud.com) Date: Tue, 6 Apr 2010 09:11:35 -0400 (EDT) Subject: [OpenAFS] servers not establishing a quorum Message-ID: <1270559495.93977471@192.168.2.230> We had two afs servers and things were running great, we had a nice quorum = and all was happy.=0AWe added an addition afs server over the weekend, and = now none of the machines will establish a quorum. All FileLogs show the 537= 6 error code.=0ATue Apr 6 08:59:59 2010 File server starting=0ATue Apr 6 = 08:59:59 2010 /var/openafs/sysid: doesn't exist=0ATue Apr 6 08:59:59 2010 = Creating new SysID file=0ATue Apr 6 08:59:59 2010 VL_RegisterAddrs rpc fai= led; will retry periodically (code=3D5376, err=3D0)=0ATue Apr 6 09:00:00 2= 010 Set thread id 133 for FSYNC_sync=0ATue Apr 6 09:00:00 2010 FSYNC_sync:= bind failed with (98), removed bogus /var/openafs/fssync.sock=0A=0Audebug = of 7002 of all three servers:=0Ahttp://pastebin.com/SZyM4BC7=0A=0A=0AThey a= ll show the sync host as 0.0.0.0 (which is what it gets set to when a qurou= m cannot be established right?)=0A=0Avos listaddrs shows the two original a= fs servers, but not the current one.=0A=0AI upped the debug level on the vl= server and get:=0ATue Apr 6 09:09:44 2010 beacon: amSyncSite is 0=0ATue Ap= r 6 09:09:44 2010 Received beacon type 0 from host 10.130.8.160=0ATue Apr = 6 09:09:46 2010 Received beacon from unknown host 172.20.1.26=0ATue Apr 6= 09:09:48 2010 recovery running in state 0=0ATue Apr 6 09:09:48 2010 beaco= n: amSyncSite is 0=0ATue Apr 6 09:09:52 2010 recovery running in state 0= =0ATue Apr 6 09:09:52 2010 beacon: amSyncSite is 0=0A=0Arepeatedly. =0AWe = added the server to the CellSrvDB file on all afs servers, and restarted th= em, and we got this. Also the sysid file is not being created on the new se= rver (which iirc is because no quorum can be established). =0AI checked tim= e, and they are all sycned within ~1 second of each other. =0A=0AWhat else = could I be missing or need to check? I am sure it is something very simple.= =0A=0AThank you.=0A=0A=0A From nymano@seznam.cz Tue Apr 6 15:05:51 2010 From: nymano@seznam.cz (=?us-ascii?Q?Alena=20Manova?=) Date: Tue, 06 Apr 2010 16:05:51 +0200 (CEST) Subject: [OpenAFS] =?us-ascii?Q?kmod=20packages=20for=20rh=20kernel=202=2E6=2E18=2D164=2E15=2E1=2Eel5?= In-Reply-To: Message-ID: <969.804.1039-30045-1078124667-1270562751@seznam.cz> Hi, any idea when this is available in the official OpenAFS repository? the latest I can see is kmod-openafs-xen-1.4.11-1.1.2.6.18_164.11.1.el5. thanks, Nick. From adeason@sinenomine.net Tue Apr 6 16:02:43 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Tue, 6 Apr 2010 10:02:43 -0500 Subject: [OpenAFS] Re: servers not establishing a quorum References: <1270559495.93977471@192.168.2.230> Message-ID: <20100406100243.6dd186ad.adeason@sinenomine.net> On Tue, 6 Apr 2010 09:11:35 -0400 (EDT) lists@drewstud.com wrote: > udebug of 7002 of all three servers: > http://pastebin.com/SZyM4BC7 7003 is vlserver, 7002 is ptserver. But I expect the output for either would be similar. > They all show the sync host as 0.0.0.0 (which is what it gets set to > when a quroum cannot be established right?) It says they have not yet established quorum. What tells you that quorum will _not_ be established is that all of the hosts are voting for themselves, so they will never agree on a leader. > vos listaddrs shows the two original afs servers, but not the current > one. vos listaddrs lists fileservers. > What else could I be missing or need to check? I am sure it is > something very simple. 'udebug 7003 -long' on each one. It looks like they may disagree on what the dbservers are, but 'udebug -long' will say what they think they are. -- Andrew Deason adeason@sinenomine.net From shadow@gmail.com Tue Apr 6 16:14:42 2010 From: shadow@gmail.com (Derrick Brashear) Date: Tue, 6 Apr 2010 11:14:42 -0400 Subject: [OpenAFS] kmod packages for rh kernel 2.6.18-164.15.1.el5 In-Reply-To: <969.804.1039-30045-1078124667-1270562751@seznam.cz> References: <969.804.1039-30045-1078124667-1270562751@seznam.cz> Message-ID: On Tue, Apr 6, 2010 at 10:05 AM, Alena Manova wrote: > Hi, > > any idea when this is available in the official OpenAFS repository? the latest I can see is kmod-openafs-xen-1.4.11-1.1.2.6.18_164.11.1.el5. if you upgrade to 1.4.12 that kmod is already provided. i will copy new kmods to 1.4.11 later today and it will probably show up, but you probably are better off with 1.4.12. -- Derrick From lists@drewstud.com Tue Apr 6 18:09:09 2010 From: lists@drewstud.com (lists@drewstud.com) Date: Tue, 6 Apr 2010 13:09:09 -0400 (EDT) Subject: [OpenAFS] Re: servers not establishing a quorum In-Reply-To: <20100406100243.6dd186ad.adeason@sinenomine.net> References: <1270559495.93977471@192.168.2.230> <20100406100243.6dd186ad.adeason@sinenomine.net> Message-ID: <1270573749.811611352@192.168.2.230> Here is what I get from 7003 -long on each server=0Ahttp://pastebin.com/L8B= JtNst=0A=0ATwo of our servers have the same local db version and sync site= db=0AThe other one has v 1.1 for both. They all have Sync host showing as = 0.0.0.0=0AWhat we have tried is removing the new afs server from CellSrvDB,= and stopping the openafs processes on that server (putting it back to what= it was before we tried adding it), and the two original servers were able = to quorum.=0AOnce we added this new server back, no more quorum. =0AWe veri= fied that the hosts files are correct and match, and they do. =0AWe also st= opped the vlserver process on two of the servers, and left it up on one (th= is is with the new server in CellSrvDB) and it never established a quorum, = even though it was the only one alive.=0AWe were however able to get vos li= staddrs to show the new fileserver, which is good, but we are still stuck. = =0AWhat has to be in place for a quorum to take place? I am certain we are = missing something simple here.=0A=0AThanks!=0A=0A-----Original Message-----= =0AFrom: "Andrew Deason" =0ASent: Tuesday, April 6,= 2010 11:02=0ATo: openafs-info@openafs.org=0ASubject: [OpenAFS] Re: servers= not establishing a quorum=0A=0AOn Tue, 6 Apr 2010 09:11:35 -0400 (EDT)=0Al= ists@drewstud.com wrote:=0A=0A> udebug of 7002 of all three servers:=0A> ht= tp://pastebin.com/SZyM4BC7=0A=0A7003 is vlserver, 7002 is ptserver. But I e= xpect the output for either=0Awould be similar.=0A=0A> They all show the sy= nc host as 0.0.0.0 (which is what it gets set to=0A> when a quroum cannot b= e established right?)=0A=0AIt says they have not yet established quorum. Wh= at tells you that quorum=0Awill _not_ be established is that all of the hos= ts are voting for=0Athemselves, so they will never agree on a leader.=0A=0A= > vos listaddrs shows the two original afs servers, but not the current=0A>= one.=0A=0Avos listaddrs lists fileservers.=0A=0A> What else could I be mis= sing or need to check? I am sure it is=0A> something very simple.=0A=0A'ude= bug 7003 -long' on each one.=0A=0AIt looks like they may disagree on what t= he dbservers are, but 'udebug=0A-long' will say what they think they are.= =0A=0A-- =0AAndrew Deason=0Aadeason@sinenomine.net=0A=0A___________________= ____________________________=0AOpenAFS-info mailing list=0AOpenAFS-info@ope= nafs.org=0Ahttps://lists.openafs.org/mailman/listinfo/openafs-info=0A From stephen@physics.unc.edu Tue Apr 6 18:32:27 2010 From: stephen@physics.unc.edu (Stephen Joyce) Date: Tue, 6 Apr 2010 13:32:27 -0400 (EDT) Subject: [OpenAFS] Re: servers not establishing a quorum In-Reply-To: <1270573749.811611352@192.168.2.230> References: <1270559495.93977471@192.168.2.230> <20100406100243.6dd186ad.adeason@sinenomine.net> <1270573749.811611352@192.168.2.230> Message-ID: On Tue, 6 Apr 2010, lists@drewstud.com wrote: > ...snip... > I am certain we are missing something simple here. > > Thanks! Simple? Do you have a firewall on any of the servers? Have you configured it to allow packets to and from the other servers on the relevant ports? (Remember udp). ... Just a shot in the dark. From lists@drewstud.com Tue Apr 6 18:39:28 2010 From: lists@drewstud.com (lists@drewstud.com) Date: Tue, 6 Apr 2010 13:39:28 -0400 (EDT) Subject: [OpenAFS] Re: servers not establishing a quorum In-Reply-To: References: <1270559495.93977471@192.168.2.230> <20100406100243.6dd186ad.adeason@sinenomine.net> <1270573749.811611352@192.168.2.230> Message-ID: <1270575568.078330632@192.168.2.230> There is no firwewall in between or iptables running on these machines. We = can also udebug to each server from the other server with no problems.=0AFo= rgot to mention these are RHEL 5.4 w/openafs 1.4.11=0AWhat is interesting i= s udebug that they all say that each machine is the lowest host.... =0AFrom= VLLog:=0ATue Apr 6 13:20:52 2010 Ubik: vote 'yes' for 10.130.8.160 (NOT i= n quorum)=0ASo they are all voting for themselves....=0A=0A-----Original Me= ssage-----=0AFrom: "Stephen Joyce" =0ASent: Tuesda= y, April 6, 2010 13:32=0ATo: lists@drewstud.com=0ACc: openafs-info@openafs.= org=0ASubject: RE: [OpenAFS] Re: servers not establishing a quorum=0A=0AOn = Tue, 6 Apr 2010, lists@drewstud.com wrote:=0A> ...snip...=0A> I am certain = we are missing something simple here.=0A>=0A> Thanks!=0A=0ASimple? Do you h= ave a firewall on any of the servers? Have you configured =0Ait to allow pa= ckets to and from the other servers on the relevant ports? =0A(Remember udp= ).=0A=0A... Just a shot in the dark.=0A From adeason@sinenomine.net Tue Apr 6 18:41:08 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Tue, 6 Apr 2010 12:41:08 -0500 Subject: [OpenAFS] Re: servers not establishing a quorum References: <1270559495.93977471@192.168.2.230> Message-ID: <20100406124108.0631ce22.adeason@sinenomine.net> On Tue, 6 Apr 2010 09:11:35 -0400 (EDT) lists@drewstud.com wrote: > Tue Apr 6 09:09:46 2010 Received beacon from unknown host 172.20.1.26 What is this address? Your udebug output shows that it expects one of the dbservers to be 172.20.125.226, but this log shows that you're getting pinged from 172.20.1.26. I could ask a few more questions, but if you just show me the new updated CellServDB for your cell and indicate which server is the new one, it would answer them. -- Andrew Deason adeason@sinenomine.net From kula@tproa.net Tue Apr 6 18:46:08 2010 From: kula@tproa.net (Thomas Kula) Date: Tue, 6 Apr 2010 13:46:08 -0400 Subject: [OpenAFS] Re: servers not establishing a quorum In-Reply-To: <20100406124108.0631ce22.adeason@sinenomine.net> References: <1270559495.93977471@192.168.2.230> <20100406124108.0631ce22.adeason@sinenomine.net> Message-ID: <20100406174608.GD17256@mcketrick.tproa.net> On Tue, Apr 06, 2010 at 12:41:08PM -0500, Andrew Deason wrote: > On Tue, 6 Apr 2010 09:11:35 -0400 (EDT) > lists@drewstud.com wrote: > > > Tue Apr 6 09:09:46 2010 Received beacon from unknown host 172.20.1.26 > > What is this address? Your udebug output shows that it expects one of > the dbservers to be 172.20.125.226, but this log shows that you're > getting pinged from 172.20.1.26. > > I could ask a few more questions, but if you just show me the new > updated CellServDB for your cell and indicate which server is the new > one, it would answer them. > And, importantly, since you are dealing with dbservers, it should be the server side CellServDB, (I tend to find it in /etc/openafs/server around here, but your path may vary). Also, you are trying to add a dbserver, right? Not just a simple fileserver? -- Thomas L. Kula | kula@tproa.net | http://kula.tproa.net/ From lists@drewstud.com Tue Apr 6 18:56:50 2010 From: lists@drewstud.com (lists@drewstud.com) Date: Tue, 6 Apr 2010 13:56:50 -0400 (EDT) Subject: [OpenAFS] Re: servers not establishing a quorum In-Reply-To: <20100406124108.0631ce22.adeason@sinenomine.net> References: <1270559495.93977471@192.168.2.230> <20100406124108.0631ce22.adeason@sinenomine.net> Message-ID: <1270576610.396627792@192.168.2.230> awesome.=0AThis may help as well:=0Awe have afs "pairs" at each location. W= e are syncing them with heartbeat/drbd.=0A172.20.125.226 is the floating VI= P for the afs server at one locaiton.=0A172.20.1.26 is the local ip of one = of the "pairs" of the servers (currently the active node). We have the db, = sysid, configs etc... identical on each pair, and before adding this extra = server, failing over each pair worked great. =0AWe have tried to get it to = only "show" the one floating vip via NetInfo, however it seemed that the fi= leserver loved to use the ip for the hostname no matter what, and to be hon= set, since it worked when we failed over to the other server, we did not th= ink it was a problem.=0AFileLog=0AFileServer afs1.afs.dfw1a has address 172= .20.1.26=0AVLLog=0ATue Apr 6 13:23:37 2010 ubik: primary address 172.20.1.= 26 does not exist=0ATue Apr 6 13:23:37 2010 Using 172.20.125.226 as my pri= mary address=0AContents of NetInfo:=0A172.20.125.226=0A=0ACellServDB:=0A>wm= .mlsrvr.com #Cell name=0A172.20.125.226 #afs.dfw1a.rsapps.net=0A192.168= .125.102 #afs.iad1a.rsapps.net=0A10.130.8.160 #store.afs.ord1a.rsapps= .net=0A=0Athe 10.138.8.160 is the server we are trying to add=0A=0A-----Ori= ginal Message-----=0AFrom: "Andrew Deason" =0ASent:= Tuesday, April 6, 2010 13:41=0ATo: openafs-info@openafs.org=0ASubject: [Op= enAFS] Re: servers not establishing a quorum=0A=0AOn Tue, 6 Apr 2010 09:11:= 35 -0400 (EDT)=0Alists@drewstud.com wrote:=0A=0A> Tue Apr 6 09:09:46 2010 = Received beacon from unknown host 172.20.1.26=0A=0AWhat is this address? Yo= ur udebug output shows that it expects one of=0Athe dbservers to be 172.20.= 125.226, but this log shows that you're=0Agetting pinged from 172.20.1.26.= =0A=0AI could ask a few more questions, but if you just show me the new=0Au= pdated CellServDB for your cell and indicate which server is the new=0Aone,= it would answer them.=0A=0A-- =0AAndrew Deason=0Aadeason@sinenomine.net=0A= =0A_______________________________________________=0AOpenAFS-info mailing l= ist=0AOpenAFS-info@openafs.org=0Ahttps://lists.openafs.org/mailman/listinfo= /openafs-info=0A From lists@drewstud.com Tue Apr 6 18:58:04 2010 From: lists@drewstud.com (lists@drewstud.com) Date: Tue, 6 Apr 2010 13:58:04 -0400 (EDT) Subject: [OpenAFS] Re: servers not establishing a quorum In-Reply-To: <20100406174608.GD17256@mcketrick.tproa.net> References: <1270559495.93977471@192.168.2.230> <20100406124108.0631ce22.adeason@sinenomine.net> <20100406174608.GD17256@mcketrick.tproa.net> Message-ID: <1270576684.121710186@192.168.2.230> Yes, we are adding both a Fileserver and a DBserver. We have our afs server= setup not to be running the client for a variety of reasons, so the only o= ne to edit on our afs servers is the server side CellServDB =0A=0A-----Orig= inal Message-----=0AFrom: "Thomas Kula" =0ASent: Tuesday, A= pril 6, 2010 13:46=0ATo: openafs-info@openafs.org=0ASubject: Re: [OpenAFS] = Re: servers not establishing a quorum=0A=0AOn Tue, Apr 06, 2010 at 12:41:08= PM -0500, Andrew Deason wrote:=0A> On Tue, 6 Apr 2010 09:11:35 -0400 (EDT)= =0A> lists@drewstud.com wrote:=0A> =0A> > Tue Apr 6 09:09:46 2010 Received= beacon from unknown host 172.20.1.26=0A> =0A> What is this address? Your u= debug output shows that it expects one of=0A> the dbservers to be 172.20.12= 5.226, but this log shows that you're=0A> getting pinged from 172.20.1.26.= =0A> =0A> I could ask a few more questions, but if you just show me the new= =0A> updated CellServDB for your cell and indicate which server is the new= =0A> one, it would answer them.=0A> =0A=0AAnd, importantly, since you are d= ealing with dbservers, it should=0Abe the server side CellServDB, (I tend t= o find it in /etc/openafs/server=0Aaround here, but your path may vary). = =0A=0AAlso, you are trying to add a dbserver, right? Not just a simple file= server?=0A=0A=0A=0A-- =0AThomas L. Kula | kula@tproa.net | http://kula.tpro= a.net/=0A_______________________________________________=0AOpenAFS-info mai= ling list=0AOpenAFS-info@openafs.org=0Ahttps://lists.openafs.org/mailman/li= stinfo/openafs-info=0A From adeason@sinenomine.net Tue Apr 6 19:37:49 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Tue, 6 Apr 2010 13:37:49 -0500 Subject: [OpenAFS] Re: servers not establishing a quorum References: <1270559495.93977471@192.168.2.230> <20100406124108.0631ce22.adeason@sinenomine.net> <1270576610.396627792@192.168.2.230> Message-ID: <20100406133749.7172ede8.adeason@sinenomine.net> On Tue, 6 Apr 2010 13:56:50 -0400 (EDT) lists@drewstud.com wrote: > awesome. > This may help as well: > we have afs "pairs" at each location. We are syncing them with > heartbeat/drbd. Trying to do that with dbservers seems overkill, but okay. So you have a hot-spare thata starts up bosserver when the other node goes down, I assume? > We have tried to get it to only "show" the one floating vip via > NetInfo I haven't been thinking about the cluster-HA AFS thing recently, but I'm not sure how necessary that is. Fileservers will register what addresses they have on startup, so if the local IP is registered in the VLDB on one fileserver, and it goes down and the other server comes up, the old local IP should go away. If/when clients re-read VLDB information, they won't get the IP for the downed fileserver. > VLLog > Tue Apr 6 13:23:37 2010 ubik: primary address 172.20.1.26 does not exist > Tue Apr 6 13:23:37 2010 Using 172.20.125.226 as my primary address > Contents of NetInfo: > 172.20.125.226 That will work for fileservers, but I think for dbservers that's going to cause problems like the one you're seeing. When 10.138.8.160 gets a ping from 172.20.1.26, it doesn't know which site in the quorum it corresponds to, since you told 172.20.1.26 not to advertise the 172.20.1.26 address. Preferably for dbservers you would not specify anything in that file. Alternatively, the easiest way for you to solve this would probably be to just route outgoing packets such that they originate from 172.20.125.226 instead of 172.20.1.26 (enabled with some heartbeat script). Would that be possible? -- Andrew Deason adeason@sinenomine.net From lists@drewstud.com Tue Apr 6 20:02:24 2010 From: lists@drewstud.com (lists@drewstud.com) Date: Tue, 6 Apr 2010 15:02:24 -0400 (EDT) Subject: [OpenAFS] Re: servers not establishing a quorum In-Reply-To: <20100406133749.7172ede8.adeason@sinenomine.net> References: <1270559495.93977471@192.168.2.230> <20100406124108.0631ce22.adeason@sinenomine.net> <1270576610.396627792@192.168.2.230> <20100406133749.7172ede8.adeason@sinenomine.net> Message-ID: <1270580544.16875658@192.168.2.230> first off thank you again! I definitely appreciate everyone taking time to = answer.=0AI removed the NetInfo file from the new openafs server we are try= ing to add, and BAM quorum, the new afs server became the quorum, and you a= re definitely correct about it having to do with what is and is not getting= registered (had to be since removing that file worked :) ) Each of our afs= servers so far is a fileserver and dbserver. =0A=0AAs far as sourcing ever= ything on each server so that it comes from the vip via heartbeat, that is = absolutely possible and we will probably go that route, since our servers a= re both fileserver and dbservers and we will need some kind of vip to fail = over. Good idea.=0A=0AThanks again for the help! I also finally understand = how a quorum is elected much better after digging through the mailing list = (found http://www.openafs.org/pipermail/openafs-devel/2001-January/005470.h= tml).=0A=0A=0A-----Original Message-----=0AFrom: "Andrew Deason" =0ASent: Tuesday, April 6, 2010 14:37=0ATo: openafs-info@open= afs.org=0ASubject: [OpenAFS] Re: servers not establishing a quorum=0A=0AOn = Tue, 6 Apr 2010 13:56:50 -0400 (EDT)=0Alists@drewstud.com wrote:=0A=0A> awe= some.=0A> This may help as well:=0A=0A> we have afs "pairs" at each locatio= n. We are syncing them with=0A> heartbeat/drbd.=0A=0ATrying to do that with= dbservers seems overkill, but okay. So you have a=0Ahot-spare thata starts= up bosserver when the other node goes down, I=0Aassume?=0A=0A> We have tri= ed to get it to only "show" the one floating vip via=0A> NetInfo=0A=0AI hav= en't been thinking about the cluster-HA AFS thing recently, but I'm=0Anot s= ure how necessary that is. Fileservers will register what addresses=0Athey = have on startup, so if the local IP is registered in the VLDB on=0Aone file= server, and it goes down and the other server comes up, the old=0Alocal IP = should go away. If/when clients re-read VLDB information, they=0Awon't get = the IP for the downed fileserver.=0A=0A> VLLog=0A> Tue Apr 6 13:23:37 2010= ubik: primary address 172.20.1.26 does not exist=0A> Tue Apr 6 13:23:37 2= 010 Using 172.20.125.226 as my primary address=0A> Contents of NetInfo:=0A>= 172.20.125.226=0A=0AThat will work for fileservers, but I think for dbserv= ers that's going=0Ato cause problems like the one you're seeing. When 10.13= 8.8.160 gets a=0Aping from 172.20.1.26, it doesn't know which site in the q= uorum it=0Acorresponds to, since you told 172.20.1.26 not to advertise the= =0A172.20.1.26 address. Preferably for dbservers you would not specify=0Aan= ything in that file.=0A=0AAlternatively, the easiest way for you to solve t= his would probably be=0Ato just route outgoing packets such that they origi= nate from=0A172.20.125.226 instead of 172.20.1.26 (enabled with some heartb= eat=0Ascript). Would that be possible?=0A=0A-- =0AAndrew Deason=0Aadeason@s= inenomine.net=0A=0A_______________________________________________=0AOpenAF= S-info mailing list=0AOpenAFS-info@openafs.org=0Ahttps://lists.openafs.org/= mailman/listinfo/openafs-info=0A From adeason@sinenomine.net Tue Apr 6 20:26:08 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Tue, 6 Apr 2010 14:26:08 -0500 Subject: [OpenAFS] Re: servers not establishing a quorum References: <1270559495.93977471@192.168.2.230> <20100406124108.0631ce22.adeason@sinenomine.net> <1270576610.396627792@192.168.2.230> <20100406133749.7172ede8.adeason@sinenomine.net> <1270580544.16875658@192.168.2.230> Message-ID: <20100406142608.8d507f77.adeason@sinenomine.net> On Tue, 6 Apr 2010 15:02:24 -0400 (EDT) lists@drewstud.com wrote: > I removed the NetInfo file from the new openafs server we are trying > to add, and BAM quorum, the new afs server became the quorum, and you > are definitely correct about it having to do with what is and is not > getting registered (had to be since removing that file worked :) ) Okay, but that may or may not be what you want in the longer term. If you don't have a NetInfo on the fileserver and it advertises all of it's IPs, a client may choose to contact the fileserver on its local IP. When it goes down and you failover, that client may try again to contact the fileserver on that local IP, and it will hang until it times out on the network. That should only happen once (at which point I believe the client refreshes its information on where that fileserver is), but that could still be annoying. But maybe it's not so bad, I don't remember what people normally do. > As far as sourcing everything on each server so that it comes from the > vip via heartbeat, that is absolutely possible and we will probably go > that route Okay, that's good. I don't think there are any problems with doing that, but it's a little annoying that it needs to be done. -- Andrew Deason adeason@sinenomine.net From pontius@btv.ibm.com Wed Apr 7 19:24:05 2010 From: pontius@btv.ibm.com (Dale Pontius) Date: Wed, 07 Apr 2010 14:24:05 -0400 Subject: [OpenAFS] Linux packages for 1.5? In-Reply-To: <5D4F5B07-1054-4428-A77C-7BBD26A82196@inf.ed.ac.uk> References: <4BAD4D29.6040409@rampaginggeek.com> <5D4F5B07-1054-4428-A77C-7BBD26A82196@inf.ed.ac.uk> Message-ID: <4BBCCDC5.9090805@btv.ibm.com> At what point should the 1.5.xx series be considered "usable" on Linux? I'm thinking usable as 1.4.xx is, not trying disconnected mode, at the moment. I've tried Linux clients from 1.5.71-73 with varying amounts of success, but in no case has it been sufficient. A quick look at my domain, and you'll see that I'm likely connecting to a stunning (or annoying) variety of servers, which might explain my results. In every case, I've had "holes" in my data as viewed in /afs. Though those holes have gotten smaller with each release, some still appear to be there with 1.5.73. Is there something I can run that will furnish debug information to be of some help? A quick glance through "pts help" or "fs help" doesn't really suggest anything to me. I'm presuming I want to identify missing data, and run something against the mount point or against the server. With 1.5.72 I found that the mount points themselves were missing for some data. I guess I also need to know how to map a mount point to a server. By the way, this stuff is both same-cell and cross-cell. For the testing I've done so far, any cross-cell data is "system:anyuser rl" - I haven't gotten to getting extra tokens. Thanks, Dale Pontius On 03/26/10 20:16, Simon Wilkinson wrote: > > On 27 Mar 2010, at 00:11, Jason Edgecombe wrote: > >> Are there any RPM or debian packages for 1.5? > > When I get the time, I've been producing RPMs for 1.5 using the > 'standard' tool chain that we use for the 1.4.x RPMs. > > If people would like to see these on a more regular basis, let me know > > Cheers, > > Simon. > > > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info -- Dale Pontius Senior Engineer IBM Corporation Phone: (802) 769-6850 Tie-Line: 446-6850 email: pontius@us.ibm.com This e-mail and its attachments, if any, may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message from your system without copying it and notify sender of the misdirection by reply e-mail. From Ken@Elkabany.com Wed Apr 7 19:24:33 2010 From: Ken@Elkabany.com (Ken Elkabany) Date: Wed, 7 Apr 2010 11:24:33 -0700 Subject: [OpenAFS] Can client's CellServDB file rely on DNS? Message-ID: --000e0cd1170a87663b0483a9acfd Content-Type: text/plain; charset=ISO-8859-1 Hello, We have had to replace our master openafs fileserver several times. Each time we have had to go through each client and update the CellServDB file to reflect the IP address of the new replacement server. Since we always map a domain name to the master openafs fileserver, is it possible to specify in the CellServDB file to always use domain name x as opposed to an IP? This feature would allow the system to reconfigure itself automatically once the DNS information is updated. By any chance is this feature already present and I've simply missed it? Thanks, Ken --000e0cd1170a87663b0483a9acfd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,

We have had to replace our master openafs fileser= ver several times. Each time we have had to go through each client and upda= te the CellServDB file to reflect the IP=A0address of the new replacement s= erver. Since we always map a domain name to the master openafs fileserver, = is it possible to specify in the CellServDB file to always use domain name = x as opposed to an IP? This feature would allow the system to reconfigure i= tself automatically once the DNS information is updated. By any chance is t= his feature already present and I've simply missed it?

Thanks,

Ken
--000e0cd1170a87663b0483a9acfd-- From rra@stanford.edu Wed Apr 7 19:28:29 2010 From: rra@stanford.edu (Russ Allbery) Date: Wed, 07 Apr 2010 11:28:29 -0700 Subject: [OpenAFS] Linux packages for 1.5? In-Reply-To: <4BBCCDC5.9090805@btv.ibm.com> (Dale Pontius's message of "Wed, 07 Apr 2010 14:24:05 -0400") References: <4BAD4D29.6040409@rampaginggeek.com> <5D4F5B07-1054-4428-A77C-7BBD26A82196@inf.ed.ac.uk> <4BBCCDC5.9090805@btv.ibm.com> Message-ID: <87ljczt8vm.fsf@windlord.stanford.edu> Dale Pontius writes: > At what point should the 1.5.xx series be considered "usable" on Linux? > I'm thinking usable as 1.4.xx is, not trying disconnected mode, at the > moment. I finally got a working build on Debian with 1.5.73.3 plus two additional patches (one of which has been merged and one of which is still in review), so that's a good sign. :) I agree with your general impression that up until now we've not really been there on Linux, but we seem to be stabilizing. I would give it a while longer, though, before considering it as stable as 1.4.x. At least a couple more releases, I suspect. > I've tried Linux clients from 1.5.71-73 with varying amounts of success, > but in no case has it been sufficient. A quick look at my domain, and > you'll see that I'm likely connecting to a stunning (or annoying) > variety of servers, which might explain my results. In every case, I've > had "holes" in my data as viewed in /afs. Though those holes have > gotten smaller with each release, some still appear to be there with > 1.5.73. Is there something I can run that will furnish debug > information to be of some help? The first thing I would try, based on my experience from yesterday, is to stop your AFS client and completely purge your cache directory. Then start it again and see if the holes have gone away. When switching from 1.4 to 1.5, I got some weird cache artifacts. I thought that was because I also had a kernel panic with the new version that could have left the cache in an inconsistent state, but I'm wondering if there may be some more basic upgrade problem. Other people have been switching back and forth without encountering this problem, so this may be a red herring, but it's worth a try. -- Russ Allbery (rra@stanford.edu) From rra@stanford.edu Wed Apr 7 19:29:55 2010 From: rra@stanford.edu (Russ Allbery) Date: Wed, 07 Apr 2010 11:29:55 -0700 Subject: [OpenAFS] Can client's CellServDB file rely on DNS? In-Reply-To: (Ken Elkabany's message of "Wed, 7 Apr 2010 11:24:33 -0700") References: Message-ID: <87hbnnt8t8.fsf@windlord.stanford.edu> Ken Elkabany writes: > We have had to replace our master openafs fileserver several times. Each > time we have had to go through each client and update the CellServDB > file to reflect the IP address of the new replacement server. Since we > always map a domain name to the master openafs fileserver, is it > possible to specify in the CellServDB file to always use domain name x > as opposed to an IP? This feature would allow the system to reconfigure > itself automatically once the DNS information is updated. No. The file semantics don't support that. However, you can enable AFSDB records (add the -afsdb flag to afsd), and then use a zero-length CellServDB file, and all VLDB location information will be resolved via AFSDB records. -- Russ Allbery (rra@stanford.edu) From sxw@inf.ed.ac.uk Wed Apr 7 19:38:59 2010 From: sxw@inf.ed.ac.uk (Simon Wilkinson) Date: Wed, 7 Apr 2010 19:38:59 +0100 Subject: [OpenAFS] Linux packages for 1.5? In-Reply-To: <87ljczt8vm.fsf@windlord.stanford.edu> References: <4BAD4D29.6040409@rampaginggeek.com> <5D4F5B07-1054-4428-A77C-7BBD26A82196@inf.ed.ac.uk> <4BBCCDC5.9090805@btv.ibm.com> <87ljczt8vm.fsf@windlord.stanford.edu> Message-ID: <6DDDE213-0AC2-4BC2-8F88-DA24FA654364@inf.ed.ac.uk> On 7 Apr 2010, at 19:28, Russ Allbery wrote: > I agree with your general impression > that up until now we've not really been there on Linux, but we seem > to be > stabilizing. Those of us actively developing on Linux have been running the 1.5 series for ages. The fact that other people are seeing problems would seem to indicate that testing across a wider variety of systems is required. Unfortunately, we don't have the time, or the systems, to do this by ourselves. If folk are interested in getting a stable 1.5 (and 1.6) for Linux any time this millenia, then we need more people testing the builds. This particularly applies to those running old, or non-standard kernels and running on odd platforms and architectures. One of the bugs I fixed for Russ surfaced exactly because he was running a kernel with slightly out of the ordinary memory management. If RPM packages would help with this please let me know. So far all I have heard is silence. Simon. From shadow@gmail.com Wed Apr 7 19:39:04 2010 From: shadow@gmail.com (Derrick Brashear) Date: Wed, 7 Apr 2010 14:39:04 -0400 Subject: [OpenAFS] Can client's CellServDB file rely on DNS? In-Reply-To: <87hbnnt8t8.fsf@windlord.stanford.edu> References: <87hbnnt8t8.fsf@windlord.stanford.edu> Message-ID: On Wed, Apr 7, 2010 at 2:29 PM, Russ Allbery wrote: > Ken Elkabany writes: > >> We have had to replace our master openafs fileserver several times. Each >> time we have had to go through each client and update the CellServDB >> file to reflect the IP address of the new replacement server. Since we >> always map a domain name to the master openafs fileserver, is it >> possible to specify in the CellServDB file to always use domain name x >> as opposed to an IP? This feature would allow the system to reconfigure >> itself automatically once the DNS information is updated. > > No. =A0The file semantics don't support that. > > However, you can enable AFSDB records (add the -afsdb flag to afsd), and > then use a zero-length CellServDB file, and all VLDB location information > will be resolved via AFSDB records. Or name just cells you want with this behavior as e.g. >cell.name #Whatever instead of >cell.name #Whatever IP #host --=20 Derrick From pontius@btv.ibm.com Wed Apr 7 19:40:21 2010 From: pontius@btv.ibm.com (Dale Pontius) Date: Wed, 07 Apr 2010 14:40:21 -0400 Subject: [OpenAFS] Linux packages for 1.5? In-Reply-To: <87ljczt8vm.fsf@windlord.stanford.edu> References: <4BAD4D29.6040409@rampaginggeek.com> <5D4F5B07-1054-4428-A77C-7BBD26A82196@inf.ed.ac.uk> <4BBCCDC5.9090805@btv.ibm.com> <87ljczt8vm.fsf@windlord.stanford.edu> Message-ID: <4BBCD195.9000902@btv.ibm.com> On 04/07/10 14:28, Russ Allbery wrote: > Dale Pontius writes: > > >> At what point should the 1.5.xx series be considered "usable" on Linux? >> I'm thinking usable as 1.4.xx is, not trying disconnected mode, at the >> moment. >> > I finally got a working build on Debian with 1.5.73.3 plus two additional > patches (one of which has been merged and one of which is still in > review), so that's a good sign. :) I agree with your general impression > that up until now we've not really been there on Linux, but we seem to be > stabilizing. > > I would give it a while longer, though, before considering it as stable as > 1.4.x. At least a couple more releases, I suspect. > > >> I've tried Linux clients from 1.5.71-73 with varying amounts of success, >> but in no case has it been sufficient. A quick look at my domain, and >> you'll see that I'm likely connecting to a stunning (or annoying) >> variety of servers, which might explain my results. In every case, I've >> had "holes" in my data as viewed in /afs. Though those holes have >> gotten smaller with each release, some still appear to be there with >> 1.5.73. Is there something I can run that will furnish debug >> information to be of some help? >> > The first thing I would try, based on my experience from yesterday, is to > stop your AFS client and completely purge your cache directory. Then > start it again and see if the holes have gone away. > A year or two back I was having some odd cache issues with the stable client. I hacked the init script (This is Gentoo, by the way.) to clear the cache each time right before starting the client. That solved my problems back then, and at some point the init script got overwritten by an update. But by then my cache problems were gone, so I didn't worry about it. It's certainly easy to put back in. > When switching from 1.4 to 1.5, I got some weird cache artifacts. I > thought that was because I also had a kernel panic with the new version > that could have left the cache in an inconsistent state, but I'm wondering > if there may be some more basic upgrade problem. > > Other people have been switching back and forth without encountering this > problem, so this may be a red herring, but it's worth a try. > I'll certainly try clearing the cache. But I'm also guessing that I'm also talking to a greater-than-average variety of servers, and wondering if there could be a vintage problem here. Is there a way to query a mount point to find the server version providing that data? (Or perhaps there's other relevant information to query.) Thanks, -- Dale Pontius Senior Engineer IBM Corporation Phone: (802) 769-6850 Tie-Line: 446-6850 email: pontius@us.ibm.com This e-mail and its attachments, if any, may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message from your system without copying it and notify sender of the misdirection by reply e-mail. From sxw@inf.ed.ac.uk Wed Apr 7 19:49:33 2010 From: sxw@inf.ed.ac.uk (Simon Wilkinson) Date: Wed, 7 Apr 2010 19:49:33 +0100 Subject: [OpenAFS] Linux packages for 1.5? In-Reply-To: <4BBCD195.9000902@btv.ibm.com> References: <4BAD4D29.6040409@rampaginggeek.com> <5D4F5B07-1054-4428-A77C-7BBD26A82196@inf.ed.ac.uk> <4BBCCDC5.9090805@btv.ibm.com> <87ljczt8vm.fsf@windlord.stanford.edu> <4BBCD195.9000902@btv.ibm.com> Message-ID: <2FC93788-8A6C-45FB-BC25-B6525F578FEF@inf.ed.ac.uk> >> > A year or two back I was having some odd cache issues with the stable > client. I hacked the init script (This is Gentoo, by the way.) to > clear > the cache each time right before starting the client. And, of course, you reported these problems, and we fixed them in a later release? > I'll certainly try clearing the cache. But I'm also guessing that I'm > also talking to a greater-than-average variety of servers, and > wondering > if there could be a vintage problem here. Is there a way to query a > mount point to find the server version providing that data? (Or > perhaps > there's other relevant information to query.) fs whereis . will tell you. Cheers, Simon. From rra@stanford.edu Wed Apr 7 19:56:02 2010 From: rra@stanford.edu (Russ Allbery) Date: Wed, 07 Apr 2010 11:56:02 -0700 Subject: [OpenAFS] Can client's CellServDB file rely on DNS? In-Reply-To: (Derrick Brashear's message of "Wed, 7 Apr 2010 14:39:04 -0400") References: <87hbnnt8t8.fsf@windlord.stanford.edu> Message-ID: <87bpdvt7lp.fsf@windlord.stanford.edu> Derrick Brashear writes: > Or name just cells you want with this behavior as e.g. > >cell.name #Whatever > instead of > >cell.name #Whatever > IP #host I didn't know you could do that. Added to the man page in: http://gerrit.openafs.org/1710 -- Russ Allbery (rra@stanford.edu) From rra@stanford.edu Wed Apr 7 19:59:52 2010 From: rra@stanford.edu (Russ Allbery) Date: Wed, 07 Apr 2010 11:59:52 -0700 Subject: [OpenAFS] Linux packages for 1.5? In-Reply-To: <6DDDE213-0AC2-4BC2-8F88-DA24FA654364@inf.ed.ac.uk> (Simon Wilkinson's message of "Wed, 7 Apr 2010 19:38:59 +0100") References: <4BAD4D29.6040409@rampaginggeek.com> <5D4F5B07-1054-4428-A77C-7BBD26A82196@inf.ed.ac.uk> <4BBCCDC5.9090805@btv.ibm.com> <87ljczt8vm.fsf@windlord.stanford.edu> <6DDDE213-0AC2-4BC2-8F88-DA24FA654364@inf.ed.ac.uk> Message-ID: <877hojt7fb.fsf@windlord.stanford.edu> Simon Wilkinson writes: > Those of us actively developing on Linux have been running the 1.5 > series for ages. The fact that other people are seeing problems would > seem to indicate that testing across a wider variety of systems is > required. Unfortunately, we don't have the time, or the systems, to do > this by ourselves. If folk are interested in getting a stable 1.5 (and > 1.6) for Linux any time this millenia, then we need more people testing > the builds. Debian packages will be available from experimental as soon as the fixes for the things I ran into yesterday are finalized, which will make it easier for some folks to test hopefully. At that point, I'll start running the new client on all of my systems, but they're all recent kernels and roughly the same basic set of packages, and my usage pattern is not heavy under normal circumstances. So I definitely echo Simon here: please test more and report any problems you encounter. -- Russ Allbery (rra@stanford.edu) From pontius@btv.ibm.com Wed Apr 7 20:06:59 2010 From: pontius@btv.ibm.com (Dale Pontius) Date: Wed, 07 Apr 2010 15:06:59 -0400 Subject: [OpenAFS] Linux packages for 1.5? In-Reply-To: <6DDDE213-0AC2-4BC2-8F88-DA24FA654364@inf.ed.ac.uk> References: <4BAD4D29.6040409@rampaginggeek.com> <5D4F5B07-1054-4428-A77C-7BBD26A82196@inf.ed.ac.uk> <4BBCCDC5.9090805@btv.ibm.com> <87ljczt8vm.fsf@windlord.stanford.edu> <6DDDE213-0AC2-4BC2-8F88-DA24FA654364@inf.ed.ac.uk> Message-ID: <4BBCD7D3.7010506@btv.ibm.com> On 04/07/10 14:38, Simon Wilkinson wrote: > > On 7 Apr 2010, at 19:28, Russ Allbery wrote: > >> I agree with your general impression >> that up until now we've not really been there on Linux, but we seem >> to be >> stabilizing. > > Those of us actively developing on Linux have been running the 1.5 > series for ages. The fact that other people are seeing problems would > seem to indicate that testing across a wider variety of systems is > required. Unfortunately, we don't have the time, or the systems, to do > this by ourselves. If folk are interested in getting a stable 1.5 (and > 1.6) for Linux any time this millenia, then we need more people > testing the builds. I'll try putting more effort into testing 1.5.x releases. I suspect my employer has a wider-than-average variety of hardware and servers available. > > This particularly applies to those running old, or non-standard > kernels and running on odd platforms and architectures. One of the > bugs I fixed for Russ surfaced exactly because he was running a kernel > with slightly out of the ordinary memory management. > > If RPM packages would help with this please let me know. So far all I > have heard is silence. I generally run Gentoo, and it's very simple to move to a new release. All I need is the source tarball and a few ebuild tweaks on my side. On a T61p I can switch afs versions in 15 minutes or so, so it's more a matter of not absolutely needing that machine during the testing interval. Thanks, -- Dale Pontius Senior Engineer IBM Corporation Phone: (802) 769-6850 Tie-Line: 446-6850 email: pontius@us.ibm.com This e-mail and its attachments, if any, may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message from your system without copying it and notify sender of the misdirection by reply e-mail. From pontius@btv.ibm.com Wed Apr 7 20:14:31 2010 From: pontius@btv.ibm.com (Dale Pontius) Date: Wed, 07 Apr 2010 15:14:31 -0400 Subject: [OpenAFS] Linux packages for 1.5? In-Reply-To: <2FC93788-8A6C-45FB-BC25-B6525F578FEF@inf.ed.ac.uk> References: <4BAD4D29.6040409@rampaginggeek.com> <5D4F5B07-1054-4428-A77C-7BBD26A82196@inf.ed.ac.uk> <4BBCCDC5.9090805@btv.ibm.com> <87ljczt8vm.fsf@windlord.stanford.edu> <4BBCD195.9000902@btv.ibm.com> <2FC93788-8A6C-45FB-BC25-B6525F578FEF@inf.ed.ac.uk> Message-ID: <4BBCD997.2010905@btv.ibm.com> On 04/07/10 14:49, Simon Wilkinson wrote: >>> >> A year or two back I was having some odd cache issues with the stable >> client. I hacked the init script (This is Gentoo, by the way.) to clear >> the cache each time right before starting the client. > > And, of course, you reported these problems, and we fixed them in a > later release? I believe I reported them to my distro, which is probably the annoying thing for you to hear, because I suspect such things frequently don't make it upstream. > >> I'll certainly try clearing the cache. But I'm also guessing that I'm >> also talking to a greater-than-average variety of servers, and wondering >> if there could be a vintage problem here. Is there a way to query a >> mount point to find the server version providing that data? (Or perhaps >> there's other relevant information to query.) > > fs whereis . will tell you. Thanks, that does give the server name. Now is there a command that will give meaningful and useful (to you) information about that server? I doubt I have any sort of shell access to any of them. Thanks, -- Dale Pontius Senior Engineer IBM Corporation Phone: (802) 769-6850 Tie-Line: 446-6850 email: pontius@us.ibm.com This e-mail and its attachments, if any, may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message from your system without copying it and notify sender of the misdirection by reply e-mail. From rra@stanford.edu Wed Apr 7 20:24:05 2010 From: rra@stanford.edu (Russ Allbery) Date: Wed, 07 Apr 2010 12:24:05 -0700 Subject: [OpenAFS] Linux packages for 1.5? In-Reply-To: <4BBCD997.2010905@btv.ibm.com> (Dale Pontius's message of "Wed, 07 Apr 2010 15:14:31 -0400") References: <4BAD4D29.6040409@rampaginggeek.com> <5D4F5B07-1054-4428-A77C-7BBD26A82196@inf.ed.ac.uk> <4BBCCDC5.9090805@btv.ibm.com> <87ljczt8vm.fsf@windlord.stanford.edu> <4BBCD195.9000902@btv.ibm.com> <2FC93788-8A6C-45FB-BC25-B6525F578FEF@inf.ed.ac.uk> <4BBCD997.2010905@btv.ibm.com> Message-ID: <87vdc3rrqi.fsf@windlord.stanford.edu> Dale Pontius writes: > On 04/07/10 14:49, Simon Wilkinson wrote: >> fs whereis . will tell you. > Thanks, that does give the server name. Now is there a command that > will give meaningful and useful (to you) information about that server? > I doubt I have any sort of shell access to any of them. rxdebug 7000 -version will display the version of AFS the file server is running. -- Russ Allbery (rra@stanford.edu) From adeason@sinenomine.net Wed Apr 7 20:24:50 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Wed, 7 Apr 2010 14:24:50 -0500 Subject: [OpenAFS] Re: Linux packages for 1.5? References: <4BAD4D29.6040409@rampaginggeek.com> <5D4F5B07-1054-4428-A77C-7BBD26A82196@inf.ed.ac.uk> <4BBCCDC5.9090805@btv.ibm.com> <87ljczt8vm.fsf@windlord.stanford.edu> <4BBCD195.9000902@btv.ibm.com> <2FC93788-8A6C-45FB-BC25-B6525F578FEF@inf.ed.ac.uk> <4BBCD997.2010905@btv.ibm.com> Message-ID: <20100407142450.eb5f3778.adeason@sinenomine.net> On Wed, 07 Apr 2010 15:14:31 -0400 Dale Pontius wrote: > > fs whereis . will tell you. > > Thanks, that does give the server name. Now is there a command that > will give meaningful and useful (to you) information about that > server? I doubt I have any sort of shell access to any of them. rxdebug -version will give you a clue as to what code they are running. But everything you've said so far sounds more like the client, to me. -- Andrew Deason adeason@sinenomine.net From brandon.m.simmons@gmail.com Thu Apr 8 03:10:53 2010 From: brandon.m.simmons@gmail.com (Brandon Simmons) Date: Wed, 7 Apr 2010 22:10:53 -0400 Subject: [OpenAFS] Shared r/w access to numerous sqlite databases: an appropriate application for AFS? Message-ID: I have a web application in which I would like many client web-servers to be able to read and write to many separate and modestly-sized sqlite databases, exported by a master server. Each database corresponds to an account, so we might have several concurrent users accessing an individual DB every few seconds. I have been testing with NFS and haven't had any problems but I'm concerned with issues of file-locking and caching problems, which the whole internet seems to be warning about. Would AFS be appropriate for this? Thanks for any advice, Brandon From utoddl@email.unc.edu Thu Apr 8 12:22:09 2010 From: utoddl@email.unc.edu (Todd Lewis) Date: Thu, 08 Apr 2010 07:22:09 -0400 Subject: [OpenAFS] Shared r/w access to numerous sqlite databases: an appropriate application for AFS? In-Reply-To: References: Message-ID: <4BBDBC61.9000609@email.unc.edu> On 04/07/2010 10:10 PM, Brandon Simmons sent: > I have a web application in which I would like many client web-servers > to be able to read and write to many separate and modestly-sized > sqlite databases, exported by a master server. Each database > corresponds to an account, so we might have several concurrent users > accessing an individual DB every few seconds. > > I have been testing with NFS and haven't had any problems but I'm > concerned with issues of file-locking and caching problems, which the > whole internet seems to be warning about. Would AFS be appropriate for > this? In a word, no. If your multiple clients were on the same host, then that host could enforce the locking sqlite attempts, but from multiple hosts you lose. I happen to be facing exactly that same problem at the moment, so I'm hopeful (doubtful, but hopeful) someone will step up and prove me wrong. > Thanks for any advice, > Brandon Same here, only not the Brandon part. -- +--------------------------------------------------------------+ / Todd_Lewis@unc.edu 919-445-9302 http://www.unc.edu/~utoddl / / "He had delusions of adequacy." - Walter Kerr / +--------------------------------------------------------------+ From sxw@inf.ed.ac.uk Thu Apr 8 12:29:41 2010 From: sxw@inf.ed.ac.uk (Simon Wilkinson) Date: Thu, 8 Apr 2010 12:29:41 +0100 Subject: [OpenAFS] Shared r/w access to numerous sqlite databases: an appropriate application for AFS? In-Reply-To: <4BBDBC61.9000609@email.unc.edu> References: <4BBDBC61.9000609@email.unc.edu> Message-ID: On 8 Apr 2010, at 12:22, Todd Lewis wrote: > In a word, no. If your multiple clients were on the same host, then > that > host could enforce the locking sqlite attempts, but from multiple > hosts > you lose. This is actually only true on Linux. On other operating systems, OpenAFS doesn't enforce byte range locks at all, so you lose even if all of the lock requests are from the same host. Someone (Matt, IIRC) was working on server support for byte range locking, but I don't think we've seen any code yet. Cheers, Simon. From pontius@btv.ibm.com Thu Apr 8 15:39:26 2010 From: pontius@btv.ibm.com (Dale Pontius) Date: Thu, 08 Apr 2010 10:39:26 -0400 Subject: [OpenAFS] Re: Linux packages for 1.5? In-Reply-To: <20100407142450.eb5f3778.adeason@sinenomine.net> References: <4BAD4D29.6040409@rampaginggeek.com> <5D4F5B07-1054-4428-A77C-7BBD26A82196@inf.ed.ac.uk> <4BBCCDC5.9090805@btv.ibm.com> <87ljczt8vm.fsf@windlord.stanford.edu> <4BBCD195.9000902@btv.ibm.com> <2FC93788-8A6C-45FB-BC25-B6525F578FEF@inf.ed.ac.uk> <4BBCD997.2010905@btv.ibm.com> <20100407142450.eb5f3778.adeason@sinenomine.net> Message-ID: <4BBDEA9E.5090009@btv.ibm.com> On 04/07/10 15:24, Andrew Deason wrote: > On Wed, 07 Apr 2010 15:14:31 -0400 > Dale Pontius wrote: > > >>> fs whereis . will tell you. >>> >> Thanks, that does give the server name. Now is there a command that >> will give meaningful and useful (to you) information about that >> server? I doubt I have any sort of shell access to any of them. >> > rxdebug -version > > will give you a clue as to what code they are running. But everything > you've said so far sounds more like the client, to me I'm rerunning my big jobstream with using the 1.5.73 now, except that I have tweaked the init script to clear the cache before loading the kernel module. So far things are looking better. The first checking tool, which failed last time, has already passed. There are quite a few more job steps to go, so it might not get done before my ride home is ready to leave. But for a few more jollies, some of the distinct server types I have available are: AFS version: Base configuration afs3.6 2.64;Iavinesh-ID71117-afs3.6-AIX-large AFS version: Base configuration afs3.6 2.67 AFS version: Base configuration afs3.6 2.64;Navinesh-ID71117-afs3.6-AIX-large This list is most likely not exhaustive - it just comes from 16 mount points I could think of off the top of my head and tuck into a quick script. OK - I had problems, again. Clearly better than last time, but not clean. In this case, I'm parked in a directory that looks really weird. Most of the subdirectories are shown, but have no contents. There is a symlink that says it points nowhere, (Symlink target is blank) yet it has contents. UIDs and sizes appear to be sheer gibberish. The server type is: AFS version: Base configuration afs3.6 2.64;Iavinesh-ID71117-afs3.6-AIX-largeP ---------------------------------------- I didn't finish this note before I had to leave yesterday, so it stayed in the drafts folder overnight. The laptop was powered off overnight, and started up fresh this morning. Further observations... If I query the server type from my 32-bit machine running 1.4.12, server types are as in the list above. If I run that same script from my 64-bit laptop running 1.5.73, I get the same server types, except the "-large" and the end becomes "-largeP". As mentioned, yesterday I had missing data on some mount points. However I couldn't seem to correlate it to server type. This morning I decided to first retry the jobstream experiment from yesterday, and today everything runs clean. So at this point I'm not sure how to proceed, since everything appears to be fully functional. There are some additional tools I can fire up, which will most likely touch other volumes. I suppose I can also continue running with 1.5.73, and keep looking for errors. Yesterday there were problems, today there are none, so far. Intermittent problems are the MOST fun. Thanks, Dale Pontius Senior Engineer IBM Corporation Phone: (802) 769-6850 Tie-Line: 446-6850 email: pontius@us.ibm.com This e-mail and its attachments, if any, may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message from your system without copying it and notify sender of the misdirection by reply e-mail. From phalenor@gmail.com Thu Apr 8 17:51:04 2010 From: phalenor@gmail.com (Andy Cobaugh) Date: Thu, 8 Apr 2010 12:51:04 -0400 (EDT) Subject: [OpenAFS] Linux packages for 1.5? In-Reply-To: <6DDDE213-0AC2-4BC2-8F88-DA24FA654364@inf.ed.ac.uk> References: <4BAD4D29.6040409@rampaginggeek.com> <5D4F5B07-1054-4428-A77C-7BBD26A82196@inf.ed.ac.uk> <4BBCCDC5.9090805@btv.ibm.com> <87ljczt8vm.fsf@windlord.stanford.edu> <6DDDE213-0AC2-4BC2-8F88-DA24FA654364@inf.ed.ac.uk> Message-ID: On 2010-04-07 at 19:38, Simon Wilkinson ( sxw@inf.ed.ac.uk ) said: > > Those of us actively developing on Linux have been running the 1.5 series for > ages. The fact that other people are seeing problems would seem to indicate > that testing across a wider variety of systems is required. Unfortunately, we > don't have the time, or the systems, to do this by ourselves. If folk are > interested in getting a stable 1.5 (and 1.6) for Linux any time this > millenia, then we need more people testing the builds. > > This particularly applies to those running old, or non-standard kernels and > running on odd platforms and architectures. One of the bugs I fixed for Russ > surfaced exactly because he was running a kernel with slightly out of the > ordinary memory management. > > If RPM packages would help with this please let me know. So far all I have > heard is silence. Yes, please - if not for every 1.5.x release, at least for the ones you want tested. I'm probably in a position here where I could start pushing 1.5 onto certain desktops/workstations around here, and having ready-made RPMs for 1.5 will make that task that much easier. --andy From matt@linuxbox.com Thu Apr 8 19:18:13 2010 From: matt@linuxbox.com (Matt W. Benjamin) Date: Thu, 8 Apr 2010 14:18:13 -0400 (EDT) Subject: [OpenAFS] Shared r/w access to numerous sqlite databases: an appropriate application for AFS? In-Reply-To: <1931138644.1895.1270750370350.JavaMail.root@thunderbeast.private.linuxbox.com> Message-ID: <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> Hi, Simon is correct. A byte-range locking implementation for OpenAFS is being funded by Your File System, Inc., under its DOE SBIR Phase II grant. As stated elsewhere by Jeff, there are (or will be) structures for making completed available to the community during the course of the work. However, my understanding that shared r/w access to sqlite through AFS probably does work, provided you ensure sqlite uses the correct locking style (cf. sqlite's os_unix.c): #define SQLITE_WHOLE_FILE_LOCKING 0x0001 /* Use whole-file locking */ This feature is apparently due to Adam Megacz, who posted briefly about it in 2006. See http://marc.info/?l=sqlite-users&m=116742195016159&w=2 . Regards, Matt ----- "Simon Wilkinson" wrote: > On 8 Apr 2010, at 12:22, Todd Lewis wrote: > > > Someone (Matt, IIRC) was working on server support for byte range > locking, but I don't think we've seen any code yet. > > Cheers, > > Simon. -- Matt Benjamin The Linux Box 206 South Fifth Ave. Suite 150 Ann Arbor, MI 48104 http://linuxbox.com tel. 734-761-4689 fax. 734-769-8938 cel. 734-216-5309 From brandon.m.simmons@gmail.com Thu Apr 8 21:06:18 2010 From: brandon.m.simmons@gmail.com (Brandon Simmons) Date: Thu, 8 Apr 2010 16:06:18 -0400 Subject: [OpenAFS] Shared r/w access to numerous sqlite databases: an appropriate application for AFS? In-Reply-To: <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> References: <1931138644.1895.1270750370350.JavaMail.root@thunderbeast.private.linuxbox.com> <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> Message-ID: On Thu, Apr 8, 2010 at 2:18 PM, Matt W. Benjamin wrote: > Hi, > > Simon is correct. =A0A byte-range locking implementation for OpenAFS is b= eing funded by Your File System, Inc., under its DOE SBIR Phase II grant. = =A0As stated elsewhere by Jeff, there are (or will be) structures for makin= g completed available to the community during the course of the work. > > However, my understanding that shared r/w access to sqlite through AFS pr= obably does work, provided you ensure sqlite uses the correct locking style= (cf. sqlite's os_unix.c): > > #define SQLITE_WHOLE_FILE_LOCKING =A00x0001 =A0 /* Use whole-file locking= */ > > This feature is apparently due to Adam Megacz, who posted briefly about i= t in 2006. =A0See http://marc.info/?l=3Dsqlite-users&m=3D116742195016159&w= =3D2 . > > Regards, > > Matt > Thanks for the response. It seems like whole-file locking in sqlite would be a good choice for me in any case, and I can't imagine needing that kind of writing concurrency. Doing a little more research, this message describes a few more issues with sqlite over NFS which I suppose might apply to AFS: http://old.nabble.com/SQLite-on-NFS-cache-coherency-td15655701.html In a situation where the whole-file locking scheme is used, would AFS be an acceptable choice? Would it be better than NFS? For instance I envision a handful of clients on different machines each writing to a single sqlite DB every few seconds; would this defeat AFS's caching scheme? Thanks for the thoughtful responses. > ----- "Simon Wilkinson" wrote: > >> On 8 Apr 2010, at 12:22, Todd Lewis wrote: >> > >> >> Someone (Matt, IIRC) was working on server support for byte range >> locking, but I don't think we've seen any code yet. >> >> Cheers, >> >> Simon. > > -- > > Matt Benjamin > > The Linux Box > 206 South Fifth Ave. Suite 150 > Ann Arbor, MI =A048104 > > http://linuxbox.com > > tel. 734-761-4689 > fax. 734-769-8938 > cel. 734-216-5309 > From kula@tproa.net Thu Apr 8 21:38:16 2010 From: kula@tproa.net (Thomas Kula) Date: Thu, 8 Apr 2010 16:38:16 -0400 Subject: [OpenAFS] Shared r/w access to numerous sqlite databases: an appropriate application for AFS? In-Reply-To: References: <1931138644.1895.1270750370350.JavaMail.root@thunderbeast.private.linuxbox.com> <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> Message-ID: <20100408203816.GJ17256@mcketrick.tproa.net> On Thu, Apr 08, 2010 at 04:06:18PM -0400, Brandon Simmons wrote: > > Thanks for the response. It seems like whole-file locking in sqlite > would be a good choice for me in any case, and I can't imagine needing > that kind of writing concurrency. > > Doing a little more research, this message describes a few more issues > with sqlite over NFS which I suppose might apply to AFS: > > http://old.nabble.com/SQLite-on-NFS-cache-coherency-td15655701.html > > In a situation where the whole-file locking scheme is used, would AFS > be an acceptable choice? Would it be better than NFS? > > For instance I envision a handful of clients on different machines > each writing to a single sqlite DB every few seconds; would this > defeat AFS's caching scheme? > Basically, every time that sqlite db file is changed the fileserver will have to notify all of the clients that have callbacks on that file, and then all the clients will have to go fetch that file again (or the chunk that changed, maybe, I can never remember that detail). It does kinda defeat caching, whether or not you still get good enough performance for it to still be useful is unknown. This kind of thing does make me twitchy, since it is starting to sound close to something that happens around here: every so often someone (usually a student) re-invents this notion of finding a lab full of unused machines, logging on to all of them and turning AFS into a rather horrid and ineffective message passing interface. Now, they usually do this at a higher rate than you are anticipating (dozens or hundreds of file creations/modifications/deletions per second --- the really fun ones renew their credentials every time as well, to the point where we've got a local unit of measurement named after a user who did a rather impressive level of this...), and at that level, with all the callbacks being broken on a large number of vnodes from a large number of clients at a high rate usually makes that particular fileserver unhappy. So, the question of concurrency and if sqlite will do the right thing aside, you may want to try a good 200% expected load from some number of clients on a volume on a fileserver you don't particularly care about first and make sure you aren't going to make things unhappy for yourself. You may also want to make sure that other common AFS operations don't cause problems. The only one that springs to mind off hand is the brief period when a volume is backed up that the volume is locked so the backup clone an be created. There may be other examples that other folks can think of. Of course, your application should be making sure it handles these kinds of things already anyways, because even local disk likes to be goofy on occasion. I love sqlite, but I don't use sqlite databases that are located in AFS outside of a single user (me) from a single machine (my workstation) and a single process that happen to be looking at a db file that just happens to be in AFS because, well, then I'll know where that file is and know it's getting backed up. Your milage may vary, offer void except when it isn't, etc. etc. -- Thomas L. Kula | kula@tproa.net | http://kula.tproa.net/ From Todd_Lewis@unc.edu Thu Apr 8 21:43:55 2010 From: Todd_Lewis@unc.edu (Todd Lewis) Date: Thu, 08 Apr 2010 16:43:55 -0400 Subject: [OpenAFS] Shared r/w access to numerous sqlite databases: an appropriate application for AFS? In-Reply-To: References: <1931138644.1895.1270750370350.JavaMail.root@thunderbeast.private.linuxbox.com> <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> Message-ID: <4BBE400B.1020004@email.unc.edu> On 04/08/2010 04:06 PM, Brandon Simmons wrote: > For instance I envision a handful of clients on different machines > each writing to a single sqlite DB every few seconds; would this > defeat AFS's caching scheme? > > Thanks for the thoughtful responses. Every few seconds your cached data is going to be invalidated, which will make sure you server stays thoroughly utilized. Sqlite shines when you don't need a data base daemon running on some central server and access requirements fit file ACLs. You don't have that. You need to distribute at a higher level. Bite the bullet and set up a real db you can connect to and write from multiple clients, and let it do what it's designed to do: arbitrate writes to maintain data integrity. AFS doesn't solve this problem (nor does NFS). Sorry. -- Todd_Lewis@unc.edu From adeason@sinenomine.net Thu Apr 8 22:03:59 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Thu, 8 Apr 2010 16:03:59 -0500 Subject: [OpenAFS] Re: Shared r/w access to numerous sqlite databases: an appropriate application for AFS? References: <1931138644.1895.1270750370350.JavaMail.root@thunderbeast.private.linuxbox.com> <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> <4BBE400B.1020004@email.unc.edu> Message-ID: <20100408160359.ad073d63.adeason@sinenomine.net> On Thu, 08 Apr 2010 16:43:55 -0400 Todd Lewis wrote: > > > On 04/08/2010 04:06 PM, Brandon Simmons wrote: > > For instance I envision a handful of clients on different machines > > each writing to a single sqlite DB every few seconds; would this > > defeat AFS's caching scheme? As others have said, it'll be slow. But it should work; more likely to work than NFS, anyway. Just don't turn off sqlite's fsync()ing behavior (don't change the 'PRAGMA synchronous' setting from the default FULL). In particular with the slowness, if one of those clients goes down that was accessing the database, the next write could take many many seconds to complete. > arbitrate writes to maintain data integrity. AFS doesn't solve this > problem (nor does NFS). Sorry. I believe this would be a lot more efficient with XCB, if the written sections are untouched by the other clients. It's not impossible for AFS to do better. -- Andrew Deason adeason@sinenomine.net From dirk.heinrichs@online.de Thu Apr 8 22:12:12 2010 From: dirk.heinrichs@online.de (Dirk Heinrichs) Date: Thu, 08 Apr 2010 23:12:12 +0200 Subject: [OpenAFS] Shared r/w access to numerous sqlite databases: an appropriate application for AFS? References: <4BBDBC61.9000609@email.unc.edu> Message-ID: <201004082312.13198.dirk.heinrichs@online.de> Am Donnerstag 08 April 2010 13:22:09 schrieb Todd Lewis: > I happen to be facing exactly that same problem at the moment, so I'm > hopeful (doubtful, but hopeful) someone will step up and prove me wrong. Well, I won't. But why don't you both simply install a real Db server, like PostgreSQL, for example? Bye... Dirk From bampfamd@berkeley.edu Thu Apr 8 23:19:54 2010 From: bampfamd@berkeley.edu (bampfamd@berkeley.edu) Date: Thu, 8 Apr 2010 15:19:54 -0700 Subject: [OpenAFS] openAFS 1.4.12 Kernel Panic on restart? (mac) Message-ID: <532c8ee43e0c7a407fd39c5097b004f5.squirrel@calmail.berkeley.edu> So i installed OpenAFS 1.4.12 on a Leopard Mac OS X computer earlier and tried running it (i had a slow afs loading issue earlier...but this version fixed that). Even though this version fixed that slow loading issue, I get the Kernel Panic message (the "You need to power down your computer...") every time I try to power down the computer/restart it. I assume that the kernel panic happens when the system is trying to unmount the AFS server...but as of right now, it happens every single time I turn off my computer. If the kernel panic log is needed I will post one up. But does anyone have any idea as of right now? From shadow@gmail.com Fri Apr 9 04:51:59 2010 From: shadow@gmail.com (Derrick Brashear) Date: Thu, 8 Apr 2010 23:51:59 -0400 Subject: [OpenAFS] openAFS 1.4.12 Kernel Panic on restart? (mac) In-Reply-To: <532c8ee43e0c7a407fd39c5097b004f5.squirrel@calmail.berkeley.edu> References: <532c8ee43e0c7a407fd39c5097b004f5.squirrel@calmail.berkeley.edu> Message-ID: On Thu, Apr 8, 2010 at 6:19 PM, wrote: > So i installed OpenAFS 1.4.12 on a Leopard Mac OS X computer earlier and > tried running it (i had a slow afs loading issue earlier...but this > version fixed that). Even though this version fixed that slow loading > issue, I get the Kernel Panic message (the "You need to power down your > computer...") every time I try to power down the computer/restart it. I > assume that the kernel panic happens when the system is trying to unmount > the AFS server...but as of right now, it happens every single time I turn > off my computer. > > If the kernel panic log is needed I will post one up. But does anyone have > any idea as of right now? a decoded panic log would be ideal, if you could. the decode-panic sript should be able to help with that. From boyland@cs.uwm.edu Fri Apr 9 17:08:47 2010 From: boyland@cs.uwm.edu (John Tang Boyland) Date: Fri, 09 Apr 2010 11:08:47 -0500 Subject: [OpenAFS] deadlock in OpenAFS 1.4.11 (Solaris 5.10) Message-ID: <29935.1270829327@pabst.cs.uwm.edu> We get an occasional deadlock happening on Solaris 5.10 using OpenAFS 1.4.11. After the problem starts, any attempt to use AFS on the machine freezes: For example: % truss -f touch /afs/not-here 15694: execve("/usr/bin/touch", 0x08047E20, 0x08047E2C) argc = 2 15694: resolvepath("/usr/lib/ld.so.1", "/lib/ld.so.1", 1023) = 12 15694: resolvepath("/usr/bin/touch", "/usr/bin/touch", 1023) = 14 15694: sysconfig(_CONFIG_PAGESIZE) = 4096 15694: xstat(2, "/usr/bin/touch", 0x08047BF8) = 0 15694: open("/var/ld/ld.config", O_RDONLY) = 3 15694: fxstat(2, 3, 0x08047B38) = 0 15694: mmap(0x00000000, 128104, PROT_READ, MAP_SHARED, 3, 0) = 0xFEFA1000 15694: close(3) = 0 15694: mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEF90000 15694: xstat(2, "/lib/libc.so.1", 0x08047440) = 0 15694: resolvepath("/lib/libc.so.1", "/lib/libc.so.1", 1023) = 14 15694: open("/lib/libc.so.1", O_RDONLY) = 3 15694: mmap(0x00010000, 32768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_ALIGN, 3, 0) = 0xFEF80000 15694: mmap(0x00010000, 880640, PROT_NONE, MAP_PRIVATE|MAP_NORESERVE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFEEA0000 15694: mmap(0xFEEA0000, 775469, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_TEXT, 3, 0) = 0xFEEA0000 15694: mmap(0xFEF6E000, 26855, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_INITDATA, 3, 778240) = 0xFEF6E000 15694: mmap(0xFEF75000, 5016, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANON, -1, 0) = 0xFEF75000 15694: munmap(0xFEF5E000, 65536) = 0 15694: memcntl(0xFEEA0000, 123376, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0 15694: close(3) = 0 15694: munmap(0xFEF80000, 32768) = 0 15694: mmap(0x00010000, 24576, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFEF80000 15694: getcontext(0x080479B0) 15694: getrlimit(RLIMIT_STACK, 0x080479A8) = 0 15694: getpid() = 15694 [15692] 15694: lwp_private(0, 1, 0xFEF82000) = 0x000001C3 15694: setustack(0xFEF82060) 15694: sysi86(SI86FPSTART, 0xFEF75A58, 0x0000133F, 0x00001F80) = 0x00000001 15694: brk(0x08062758) = 0 15694: brk(0x08064758) = 0 15694: xstat(2, "/usr/lib/locale/en_US.UTF-8/en_US.UTF-8.so.3", 0x08046D08) = 015694: resolvepath("/usr/lib/locale/en_US.UTF-8/en_US.UTF-8.so.3", "/usr/lib/locale/en_US.UTF-8/en_US.UTF-8.so.3", 1023) = 44 15694: open("/usr/lib/locale/en_US.UTF-8/en_US.UTF-8.so.3", O_RDONLY) = 3 15694: mmap(0x00010000, 32768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_ALIGN, 3, 0) = 0xFEE90000 15694: mmap(0x00010000, 2297856, PROT_NONE, MAP_PRIVATE|MAP_NORESERVE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFEC00000 15694: mmap(0xFEC00000, 2225278, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_TEXT, 3, 0) = 0xFEC00000 15694: mmap(0xFEE2F000, 4234, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_INITDATA, 3, 2224128) = 0xFEE2F000 15694: munmap(0xFEE20000, 61440) = 0 15694: memcntl(0xFEC00000, 7188, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0 15694: close(3) = 0 15694: xstat(2, "/usr/lib/locale/en_US.UTF-8/methods_en_US.UTF-8.so.3", 0x08046C60) = 0 15694: resolvepath("/usr/lib/locale/en_US.UTF-8/methods_en_US.UTF-8.so.3", "/usr/lib/locale/common/methods_unicode.so.3", 1023) = 43 15694: open("/usr/lib/locale/en_US.UTF-8/methods_en_US.UTF-8.so.3", O_RDONLY) = 3 15694: mmap(0xFEE90000, 32768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0xFEE90000 15694: mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEE80000 15694: mmap(0x00010000, 122880, PROT_NONE, MAP_PRIVATE|MAP_NORESERVE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFEE60000 15694: mmap(0xFEE60000, 55437, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_TEXT, 3, 0) = 0xFEE60000 15694: mmap(0xFEE7D000, 2524, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_INITDATA, 3, 53248) = 0xFEE7D000 15694: munmap(0xFEE6E000, 61440) = 0 15694: memcntl(0xFEE60000, 2532, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0 15694: close(3) = 0 15694: xstat(2, "/usr/lib/locale/en_US.UTF-8/libc.so.1", 0x08046C60) Err#2 ENOENT 15694: munmap(0xFEE90000, 32768) = 0 15694: sysconfig(_CONFIG_PAGESIZE) = 4096 FREEZE On a machine which has not had the problem (yet...) the output continues ... 24608: sysconfig(_CONFIG_PAGESIZE) = 4096 24608: stat64("/afs/not-here", 0x08047C90) Err#2 ENOENT 24608: creat64("/afs/not-here", 0666) Err#30 EROFS 24608: open("/usr/lib/locale/en_US.UTF-8/LC_MESSAGES/SUNW_OST_OSCMD.mo", O_RDONLY) Err#2 ENOENT 24608: fstat64(2, 0x08046EA0) = 0 24608: write(2, " t o u c h", 5) = 5 24608: write(2, " : ", 2) = 2 24608: write(2, " / a f s / n o t - h e r".., 13) = 13 24608: write(2, " c a n n o t c r e a".., 15) = 15 24608: _exit(1) In other words, the stat64 call accesses AFS and (on the machine with the problem), the thread gets stuck in the AFS tarbaby. I suspected it was due to logging, so I changed the configuration to mount a dedicated partition for /usr/vice/cache, and rebooted. The ' machine was fine for a month or two, but problem has re-occurred. The machine is used frequently (it's our main computer server for undergraduate classes) but "fortunately" AFS is not very popular here so most courses don't use it (partly because of nasty things like this happening now and then) and so the machine is still being used for non-AFS courses. Hence I hadn't tried to install a newer version of OpenAFS. If this is a known bug with OpenAFS, I will indeed ask them to take the machine offline long enough to fix this. (Political capital and all; I hope people understand.) I haven't tried to reproduce this bug (and wouldn't want to on the computer server!): it only seems to happen on these main compute servers -- never on my little research machines... :-( Any help would be appreciated. John From shadow@gmail.com Fri Apr 9 17:26:26 2010 From: shadow@gmail.com (Derrick Brashear) Date: Fri, 9 Apr 2010 12:26:26 -0400 Subject: [OpenAFS] deadlock in OpenAFS 1.4.11 (Solaris 5.10) In-Reply-To: <29935.1270829327@pabst.cs.uwm.edu> References: <29935.1270829327@pabst.cs.uwm.edu> Message-ID: cmdebug or it didn't happen. On Fri, Apr 9, 2010 at 12:08 PM, John Tang Boyland wrote: > We get an occasional deadlock happening on Solaris 5.10 using > OpenAFS 1.4.11. =A0After the problem starts, any attempt to use AFS > on the machine freezes: =A0For example: > > % truss -f touch /afs/not-here > 15694: =A0execve("/usr/bin/touch", 0x08047E20, 0x08047E2C) =A0argc =3D 2 > 15694: =A0resolvepath("/usr/lib/ld.so.1", "/lib/ld.so.1", 1023) =3D 12 > 15694: =A0resolvepath("/usr/bin/touch", "/usr/bin/touch", 1023) =3D 14 > 15694: =A0sysconfig(_CONFIG_PAGESIZE) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =3D 4096 > 15694: =A0xstat(2, "/usr/bin/touch", 0x08047BF8) =A0 =A0 =A0 =A0 =A0=3D 0 > 15694: =A0open("/var/ld/ld.config", O_RDONLY) =A0 =A0 =A0 =A0 =A0 =A0 =3D= 3 > 15694: =A0fxstat(2, 3, 0x08047B38) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0=3D 0 > 15694: =A0mmap(0x00000000, 128104, PROT_READ, MAP_SHARED, 3, 0) =3D 0xFEF= A1000 > 15694: =A0close(3) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D 0 > 15694: =A0mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIV= ATE|MAP_ANON, -1, 0) =3D 0xFEF90000 > 15694: =A0xstat(2, "/lib/libc.so.1", 0x08047440) =A0 =A0 =A0 =A0 =A0=3D 0 > 15694: =A0resolvepath("/lib/libc.so.1", "/lib/libc.so.1", 1023) =3D 14 > 15694: =A0open("/lib/libc.so.1", O_RDONLY) =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0=3D 3 > 15694: =A0mmap(0x00010000, 32768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_AL= IGN, 3, 0) =3D 0xFEF80000 > 15694: =A0mmap(0x00010000, 880640, PROT_NONE, MAP_PRIVATE|MAP_NORESERVE|M= AP_ANON|MAP_ALIGN, -1, 0) =3D 0xFEEA0000 > 15694: =A0mmap(0xFEEA0000, 775469, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_F= IXED|MAP_TEXT, 3, 0) =3D 0xFEEA0000 > 15694: =A0mmap(0xFEF6E000, 26855, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_F= IXED|MAP_INITDATA, 3, 778240) =3D 0xFEF6E000 > 15694: =A0mmap(0xFEF75000, 5016, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FI= XED|MAP_ANON, -1, 0) =3D 0xFEF75000 > 15694: =A0munmap(0xFEF5E000, 65536) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =3D 0 > 15694: =A0memcntl(0xFEEA0000, 123376, MC_ADVISE, MADV_WILLNEED, 0, 0) =3D= 0 > 15694: =A0close(3) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D 0 > 15694: =A0munmap(0xFEF80000, 32768) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =3D 0 > 15694: =A0mmap(0x00010000, 24576, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRI= VATE|MAP_ANON|MAP_ALIGN, -1, 0) =3D 0xFEF80000 > 15694: =A0getcontext(0x080479B0) > 15694: =A0getrlimit(RLIMIT_STACK, 0x080479A8) =A0 =A0 =A0 =A0 =A0 =A0 =3D= 0 > 15694: =A0getpid() =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D 15694 [15692] > 15694: =A0lwp_private(0, 1, 0xFEF82000) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =3D 0x000001C3 > 15694: =A0setustack(0xFEF82060) > 15694: =A0sysi86(SI86FPSTART, 0xFEF75A58, 0x0000133F, 0x00001F80) =3D 0x0= 0000001 > 15694: =A0brk(0x08062758) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =3D 0 > 15694: =A0brk(0x08064758) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =3D 0 > 15694: =A0xstat(2, "/usr/lib/locale/en_US.UTF-8/en_US.UTF-8.so.3", 0x0804= 6D08) =3D 015694: =A0resolvepath("/usr/lib/locale/en_US.UTF-8/en_US.UTF-8.s= o.3", "/usr/lib/locale/en_US.UTF-8/en_US.UTF-8.so.3", 1023) =3D 44 > 15694: =A0open("/usr/lib/locale/en_US.UTF-8/en_US.UTF-8.so.3", O_RDONLY) = =3D 3 > 15694: =A0mmap(0x00010000, 32768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_AL= IGN, 3, 0) =3D 0xFEE90000 > 15694: =A0mmap(0x00010000, 2297856, PROT_NONE, MAP_PRIVATE|MAP_NORESERVE|= MAP_ANON|MAP_ALIGN, -1, 0) =3D 0xFEC00000 > 15694: =A0mmap(0xFEC00000, 2225278, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_= FIXED|MAP_TEXT, 3, 0) =3D 0xFEC00000 > 15694: =A0mmap(0xFEE2F000, 4234, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIV= ATE|MAP_FIXED|MAP_INITDATA, 3, 2224128) =3D 0xFEE2F000 > 15694: =A0munmap(0xFEE20000, 61440) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =3D 0 > 15694: =A0memcntl(0xFEC00000, 7188, MC_ADVISE, MADV_WILLNEED, 0, 0) =3D 0 > 15694: =A0close(3) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D 0 > 15694: =A0xstat(2, "/usr/lib/locale/en_US.UTF-8/methods_en_US.UTF-8.so.3"= , 0x08046C60) =3D 0 > 15694: =A0resolvepath("/usr/lib/locale/en_US.UTF-8/methods_en_US.UTF-8.so= .3", "/usr/lib/locale/common/methods_unicode.so.3", 1023) =3D 43 > 15694: =A0open("/usr/lib/locale/en_US.UTF-8/methods_en_US.UTF-8.so.3", O_= RDONLY) =3D 3 > 15694: =A0mmap(0xFEE90000, 32768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FI= XED, 3, 0) =3D 0xFEE90000 > 15694: =A0mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIV= ATE|MAP_ANON, -1, 0) =3D 0xFEE80000 > 15694: =A0mmap(0x00010000, 122880, PROT_NONE, MAP_PRIVATE|MAP_NORESERVE|M= AP_ANON|MAP_ALIGN, -1, 0) =3D 0xFEE60000 > 15694: =A0mmap(0xFEE60000, 55437, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FI= XED|MAP_TEXT, 3, 0) =3D 0xFEE60000 > 15694: =A0mmap(0xFEE7D000, 2524, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIV= ATE|MAP_FIXED|MAP_INITDATA, 3, 53248) =3D 0xFEE7D000 > 15694: =A0munmap(0xFEE6E000, 61440) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =3D 0 > 15694: =A0memcntl(0xFEE60000, 2532, MC_ADVISE, MADV_WILLNEED, 0, 0) =3D 0 > 15694: =A0close(3) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D 0 > 15694: =A0xstat(2, "/usr/lib/locale/en_US.UTF-8/libc.so.1", 0x08046C60) E= rr#2 ENOENT > 15694: =A0munmap(0xFEE90000, 32768) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =3D 0 > 15694: =A0sysconfig(_CONFIG_PAGESIZE) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =3D 4096 > > FREEZE > > On a machine which has not had the problem (yet...) the output continues > ... > 24608: =A0sysconfig(_CONFIG_PAGESIZE) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =3D 4096 > 24608: =A0stat64("/afs/not-here", 0x08047C90) =A0 =A0 =A0 =A0 =A0 =A0 Err= #2 ENOENT > 24608: =A0creat64("/afs/not-here", 0666) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0Err#30 EROFS > 24608: =A0open("/usr/lib/locale/en_US.UTF-8/LC_MESSAGES/SUNW_OST_OSCMD.mo= ", O_RDONLY) Err#2 ENOENT > 24608: =A0fstat64(2, 0x08046EA0) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0=3D 0 > 24608: =A0write(2, " t o u c h", 5) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =3D 5 > 24608: =A0write(2, " : =A0", 2) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =3D 2 > 24608: =A0write(2, " / a f s / n o t - h e r".., 13) =A0 =A0 =A0=3D 13 > 24608: =A0write(2, " =A0 c a n n o t =A0 c r e a".., 15) =A0 =A0 =A0=3D 1= 5 > 24608: =A0_exit(1) > > In other words, the stat64 call accesses AFS and (on the machine > with the problem), the thread gets stuck in the AFS tarbaby. > > I suspected it was due to logging, so I changed the configuration to > mount a dedicated partition for /usr/vice/cache, and rebooted. =A0The ' > machine was fine for a month or two, but problem has re-occurred. > > The machine is used frequently (it's our main computer server for > undergraduate classes) but "fortunately" AFS is not very popular here > so most courses don't use it (partly because of nasty things like > this happening now and then) and so the machine is still being used > for non-AFS courses. =A0Hence I hadn't tried to install a newer version > of OpenAFS. =A0If this is a known bug with OpenAFS, I will indeed > ask them to take the machine offline long enough to fix this. > (Political capital and all; I hope people understand.) > > I haven't tried to reproduce this bug (and wouldn't want to > on the computer server!): it only seems to happen on these > main compute servers -- never on my little research machines... :-( > > Any help would be appreciated. > > John > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info > --=20 Derrick From deengert@anl.gov Fri Apr 9 17:33:48 2010 From: deengert@anl.gov (Douglas E. Engert) Date: Fri, 09 Apr 2010 11:33:48 -0500 Subject: [OpenAFS] deadlock in OpenAFS 1.4.11 (Solaris 5.10) In-Reply-To: <29935.1270829327@pabst.cs.uwm.edu> References: <29935.1270829327@pabst.cs.uwm.edu> Message-ID: <4BBF56EC.7090900@anl.gov> What happens if you have exported LANG=C into your environment. Based on you trace the freeze comes before AFS does anything. Or is just the truss has not written all its output. John Tang Boyland wrote: > We get an occasional deadlock happening on Solaris 5.10 using > OpenAFS 1.4.11. After the problem starts, any attempt to use AFS > on the machine freezes: For example: > > % truss -f touch /afs/not-here > 15694: execve("/usr/bin/touch", 0x08047E20, 0x08047E2C) argc = 2 > 15694: resolvepath("/usr/lib/ld.so.1", "/lib/ld.so.1", 1023) = 12 > 15694: resolvepath("/usr/bin/touch", "/usr/bin/touch", 1023) = 14 > 15694: sysconfig(_CONFIG_PAGESIZE) = 4096 > 15694: xstat(2, "/usr/bin/touch", 0x08047BF8) = 0 > 15694: open("/var/ld/ld.config", O_RDONLY) = 3 > 15694: fxstat(2, 3, 0x08047B38) = 0 > 15694: mmap(0x00000000, 128104, PROT_READ, MAP_SHARED, 3, 0) = 0xFEFA1000 > 15694: close(3) = 0 > 15694: mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEF90000 > 15694: xstat(2, "/lib/libc.so.1", 0x08047440) = 0 > 15694: resolvepath("/lib/libc.so.1", "/lib/libc.so.1", 1023) = 14 > 15694: open("/lib/libc.so.1", O_RDONLY) = 3 > 15694: mmap(0x00010000, 32768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_ALIGN, 3, 0) = 0xFEF80000 > 15694: mmap(0x00010000, 880640, PROT_NONE, MAP_PRIVATE|MAP_NORESERVE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFEEA0000 > 15694: mmap(0xFEEA0000, 775469, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_TEXT, 3, 0) = 0xFEEA0000 > 15694: mmap(0xFEF6E000, 26855, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_INITDATA, 3, 778240) = 0xFEF6E000 > 15694: mmap(0xFEF75000, 5016, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANON, -1, 0) = 0xFEF75000 > 15694: munmap(0xFEF5E000, 65536) = 0 > 15694: memcntl(0xFEEA0000, 123376, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0 > 15694: close(3) = 0 > 15694: munmap(0xFEF80000, 32768) = 0 > 15694: mmap(0x00010000, 24576, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFEF80000 > 15694: getcontext(0x080479B0) > 15694: getrlimit(RLIMIT_STACK, 0x080479A8) = 0 > 15694: getpid() = 15694 [15692] > 15694: lwp_private(0, 1, 0xFEF82000) = 0x000001C3 > 15694: setustack(0xFEF82060) > 15694: sysi86(SI86FPSTART, 0xFEF75A58, 0x0000133F, 0x00001F80) = 0x00000001 > 15694: brk(0x08062758) = 0 > 15694: brk(0x08064758) = 0 > 15694: xstat(2, "/usr/lib/locale/en_US.UTF-8/en_US.UTF-8.so.3", 0x08046D08) = 015694: resolvepath("/usr/lib/locale/en_US.UTF-8/en_US.UTF-8.so.3", "/usr/lib/locale/en_US.UTF-8/en_US.UTF-8.so.3", 1023) = 44 > 15694: open("/usr/lib/locale/en_US.UTF-8/en_US.UTF-8.so.3", O_RDONLY) = 3 > 15694: mmap(0x00010000, 32768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_ALIGN, 3, 0) = 0xFEE90000 > 15694: mmap(0x00010000, 2297856, PROT_NONE, MAP_PRIVATE|MAP_NORESERVE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFEC00000 > 15694: mmap(0xFEC00000, 2225278, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_TEXT, 3, 0) = 0xFEC00000 > 15694: mmap(0xFEE2F000, 4234, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_INITDATA, 3, 2224128) = 0xFEE2F000 > 15694: munmap(0xFEE20000, 61440) = 0 > 15694: memcntl(0xFEC00000, 7188, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0 > 15694: close(3) = 0 > 15694: xstat(2, "/usr/lib/locale/en_US.UTF-8/methods_en_US.UTF-8.so.3", 0x08046C60) = 0 > 15694: resolvepath("/usr/lib/locale/en_US.UTF-8/methods_en_US.UTF-8.so.3", "/usr/lib/locale/common/methods_unicode.so.3", 1023) = 43 > 15694: open("/usr/lib/locale/en_US.UTF-8/methods_en_US.UTF-8.so.3", O_RDONLY) = 3 > 15694: mmap(0xFEE90000, 32768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0xFEE90000 > 15694: mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEE80000 > 15694: mmap(0x00010000, 122880, PROT_NONE, MAP_PRIVATE|MAP_NORESERVE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFEE60000 > 15694: mmap(0xFEE60000, 55437, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_TEXT, 3, 0) = 0xFEE60000 > 15694: mmap(0xFEE7D000, 2524, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_INITDATA, 3, 53248) = 0xFEE7D000 > 15694: munmap(0xFEE6E000, 61440) = 0 > 15694: memcntl(0xFEE60000, 2532, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0 > 15694: close(3) = 0 > 15694: xstat(2, "/usr/lib/locale/en_US.UTF-8/libc.so.1", 0x08046C60) Err#2 ENOENT > 15694: munmap(0xFEE90000, 32768) = 0 > 15694: sysconfig(_CONFIG_PAGESIZE) = 4096 > > FREEZE > > On a machine which has not had the problem (yet...) the output continues > ... > 24608: sysconfig(_CONFIG_PAGESIZE) = 4096 > 24608: stat64("/afs/not-here", 0x08047C90) Err#2 ENOENT > 24608: creat64("/afs/not-here", 0666) Err#30 EROFS > 24608: open("/usr/lib/locale/en_US.UTF-8/LC_MESSAGES/SUNW_OST_OSCMD.mo", O_RDONLY) Err#2 ENOENT > 24608: fstat64(2, 0x08046EA0) = 0 > 24608: write(2, " t o u c h", 5) = 5 > 24608: write(2, " : ", 2) = 2 > 24608: write(2, " / a f s / n o t - h e r".., 13) = 13 > 24608: write(2, " c a n n o t c r e a".., 15) = 15 > 24608: _exit(1) > > In other words, the stat64 call accesses AFS and (on the machine > with the problem), the thread gets stuck in the AFS tarbaby. > > I suspected it was due to logging, so I changed the configuration to > mount a dedicated partition for /usr/vice/cache, and rebooted. The ' > machine was fine for a month or two, but problem has re-occurred. > > The machine is used frequently (it's our main computer server for > undergraduate classes) but "fortunately" AFS is not very popular here > so most courses don't use it (partly because of nasty things like > this happening now and then) and so the machine is still being used > for non-AFS courses. Hence I hadn't tried to install a newer version > of OpenAFS. If this is a known bug with OpenAFS, I will indeed > ask them to take the machine offline long enough to fix this. > (Political capital and all; I hope people understand.) > > I haven't tried to reproduce this bug (and wouldn't want to > on the computer server!): it only seems to happen on these > main compute servers -- never on my little research machines... :-( > > Any help would be appreciated. > > John > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info > > -- Douglas E. Engert Argonne National Laboratory 9700 South Cass Avenue Argonne, Illinois 60439 (630) 252-5444 From boyland@cs.uwm.edu Fri Apr 9 18:36:05 2010 From: boyland@cs.uwm.edu (John Tang Boyland) Date: Fri, 09 Apr 2010 12:36:05 -0500 Subject: [OpenAFS] deadlock in OpenAFS 1.4.11 (Solaris 5.10) In-Reply-To: Your message of "Fri, 09 Apr 2010 12:26:26 EDT." Message-ID: <595.1270834565@pabst.cs.uwm.edu> ] cmdebug or it didn't happen. ] ] On Fri, Apr 9, 2010 at 12:08 PM, John Tang Boyland ] wrote: ] > We get an occasional deadlock happening on Solaris 5.10 using ] > OpenAFS 1.4.11.  After the problem starts, any attempt to use AFS ] > on the machine freezes:  For example: I foolishly thought that with every AFS access deadlocking, cmdebug wouldn't work. But it does.... ** Cache entry @ 0xa26da3f0 for 1.536875155.530.1418 [cs.uwm.edu] locks: (reader_waiting, write_locked(pid:17732 at:250), 2 waiters) 26532 bytes DV 197 refcnt 3 callback 00000000 expires 1270781645 1 opens 0 writers normal file states (0x0) ** Cache entry @ 0xa27651d0 for 1.536875155.608.1458 [cs.uwm.edu] locks: (upgrade_waiting, write_locked(pid:17679 at:66), 12 waiters) 19094744 bytes DV 109 refcnt 13 callback 00000000 expires 1270782798 0 opens 0 writers normal file states (0x0) ** Cache entry @ 0xa2710018 for 1.536875155.610.1499 [cs.uwm.edu] locks: (none_waiting, write_locked(pid:17889 at:250)) 23240 bytes DV 1 refcnt 1 callback 00000000 expires 1270782798 1 opens 0 writers normal file states (0x0) ** Cache entry @ 0xa26bf000 for 1.536873892.1.1 [cs.uwm.edu] locks: (writer_waiting, 7 read_locks(pid:18421), 41 waiters) 2048 bytes DV 8 refcnt 49 callback 00000000 expires 1270774475 0 opens 0 writers volume root states (0x4), read-only ** Cache entry @ 0xa27c99a0 for 1.536874783.4234.9047 [cs.uwm.edu] locks: (none_waiting, write_locked(pid:17834 at:250)) 1641 bytes DV 1 refcnt 1 callback 00000000 expires 1270782797 1 opens 0 writers normal file states (0x0) John From boyland@cs.uwm.edu Fri Apr 9 18:39:43 2010 From: boyland@cs.uwm.edu (John Tang Boyland) Date: Fri, 09 Apr 2010 12:39:43 -0500 Subject: [OpenAFS] deadlock in OpenAFS 1.4.11 (Solaris 5.10) In-Reply-To: Your message of "Fri, 09 Apr 2010 11:33:48 CDT." Message-ID: <634.1270834783@pabst.cs.uwm.edu> ] What happens if you have exported LANG=C into your environment. ... 19813: lwp_private(0, 1, 0xFEF82000) = 0x000001C3 19813: setustack(0xFEF82060) 19813: sysi86(SI86FPSTART, 0xFEF75A58, 0x0000133F, 0x00001F80) = 0x00000001 19813: brk(0x08062758) = 0 19813: brk(0x08064758) = 0 FREEZE On the machine WITHOUT the problem, it continues: 27096: stat64("/afs/not-here", 0x08047CA0) Err#2 ENOENT 27096: creat64("/afs/not-here", 0666) Err#30 EROFS 27096: fstat64(2, 0x08046EB0) = 0 27096: write(2, " t o u c h", 5) = 5 ... ] Based on you trace the freeze comes before AFS does anything. Or ] is just the truss has not written all its output. The freeze comes EXACTLY when AFS is asked to do somrething. truss writes output once the call to stat64 returns, which it never does. John Boyland From shadow@gmail.com Fri Apr 9 19:21:31 2010 From: shadow@gmail.com (Derrick Brashear) Date: Fri, 9 Apr 2010 14:21:31 -0400 Subject: [OpenAFS] deadlock in OpenAFS 1.4.11 (Solaris 5.10) In-Reply-To: <595.1270834565@pabst.cs.uwm.edu> References: <595.1270834565@pabst.cs.uwm.edu> Message-ID: On Fri, Apr 9, 2010 at 1:36 PM, John Tang Boyland wrote: > ] cmdebug or it didn't happen. > ] > ] On Fri, Apr 9, 2010 at 12:08 PM, John Tang Boyland > ] wrote: > ] > We get an occasional deadlock happening on Solaris 5.10 using > ] > OpenAFS 1.4.11. =A0After the problem starts, any attempt to use AFS > ] > on the machine freezes: =A0For example: > > I foolishly thought that with every AFS access deadlocking, cmdebug > wouldn't work. =A0But it does.... That's the best time to try it. > > ** Cache entry @ 0xa26da3f0 for 1.536875155.530.1418 [cs.uwm.edu] > =A0 =A0locks: (reader_waiting, write_locked(pid:17732 at:250), 2 waiters) > =A0 =A0 =A0 =A0 =A0 26532 bytes =A0DV =A0 =A0 =A0 =A0 =A0197 =A0refcnt = =A0 =A0 3 > =A0 =A0callback 00000000 =A0 expires 1270781645 > =A0 =A01 opens =A0 =A0 0 writers > =A0 =A0normal file > =A0 =A0states (0x0) ok, that's the rdwr vnode op, so that makes some sense. > ** Cache entry @ 0xa27651d0 for 1.536875155.608.1458 [cs.uwm.edu] > =A0 =A0locks: (upgrade_waiting, write_locked(pid:17679 at:66), 12 waiters= ) > =A0 =A0 =A0 =A019094744 bytes =A0DV =A0 =A0 =A0 =A0 =A0109 =A0refcnt =A0 = =A013 > =A0 =A0callback 00000000 =A0 expires 1270782798 > =A0 =A00 opens =A0 =A0 0 writers > =A0 =A0normal file > =A0 =A0states (0x0) and 66 is GetDCache > ** Cache entry @ 0xa2710018 for 1.536875155.610.1499 [cs.uwm.edu] > =A0 =A0locks: (none_waiting, write_locked(pid:17889 at:250)) > =A0 =A0 =A0 =A0 =A0 23240 bytes =A0DV =A0 =A0 =A0 =A0 =A0 =A01 =A0refcnt = =A0 =A0 1 > =A0 =A0callback 00000000 =A0 expires 1270782798 > =A0 =A01 opens =A0 =A0 0 writers > =A0 =A0normal file > =A0 =A0states (0x0) > ** Cache entry @ 0xa26bf000 for 1.536873892.1.1 [cs.uwm.edu] > =A0 =A0locks: (writer_waiting, 7 read_locks(pid:18421), 41 waiters) > =A0 =A0 =A0 =A0 =A0 =A02048 bytes =A0DV =A0 =A0 =A0 =A0 =A0 =A08 =A0refcn= t =A0 =A049 > =A0 =A0callback 00000000 =A0 expires 1270774475 > =A0 =A00 opens =A0 =A0 0 writers > =A0 =A0volume root > =A0 =A0states (0x4), read-only > ** Cache entry @ 0xa27c99a0 for 1.536874783.4234.9047 [cs.uwm.edu] > =A0 =A0locks: (none_waiting, write_locked(pid:17834 at:250)) > =A0 =A0 =A0 =A0 =A0 =A01641 bytes =A0DV =A0 =A0 =A0 =A0 =A0 =A01 =A0refcn= t =A0 =A0 1 > =A0 =A0callback 00000000 =A0 expires 1270782797 > =A0 =A01 opens =A0 =A0 0 writers > =A0 =A0normal file > =A0 =A0states (0x0) Can you get the fids of the files in question? --=20 Derrick From shadow@gmail.com Fri Apr 9 19:27:24 2010 From: shadow@gmail.com (Derrick Brashear) Date: Fri, 9 Apr 2010 14:27:24 -0400 Subject: [OpenAFS] deadlock in OpenAFS 1.4.11 (Solaris 5.10) In-Reply-To: References: <595.1270834565@pabst.cs.uwm.edu> Message-ID: On Fri, Apr 9, 2010 at 2:21 PM, Derrick Brashear wrote: > On Fri, Apr 9, 2010 at 1:36 PM, John Tang Boyland > wrote: >> ] cmdebug or it didn't happen. >> ] >> ] On Fri, Apr 9, 2010 at 12:08 PM, John Tang Boyland >> ] wrote: >> ] > We get an occasional deadlock happening on Solaris 5.10 using >> ] > OpenAFS 1.4.11. =A0After the problem starts, any attempt to use AFS >> ] > on the machine freezes: =A0For example: >> >> I foolishly thought that with every AFS access deadlocking, cmdebug >> wouldn't work. =A0But it does.... > > That's the best time to try it. Almost certainly a dcache lock (which cmdebug doesn't show, alas) involved here and causing this. I suppose the other thing which may help: can you collect fstrace for this? From adeason@sinenomine.net Fri Apr 9 19:38:23 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Fri, 9 Apr 2010 13:38:23 -0500 Subject: [OpenAFS] Re: deadlock in OpenAFS 1.4.11 (Solaris 5.10) References: <595.1270834565@pabst.cs.uwm.edu> Message-ID: <20100409133823.36f41ce3.adeason@sinenomine.net> On Fri, 9 Apr 2010 14:27:24 -0400 Derrick Brashear wrote: > Almost certainly a dcache lock (which cmdebug doesn't show, alas) > involved here and causing this. > > I suppose the other thing which may help: can you collect fstrace for > this? What about the kernel stack trace for the proc(s) from mdb? Or do you know where we're hanging? -- Andrew Deason adeason@sinenomine.net From shadow@gmail.com Fri Apr 9 19:48:34 2010 From: shadow@gmail.com (Derrick Brashear) Date: Fri, 9 Apr 2010 14:48:34 -0400 Subject: [OpenAFS] Re: deadlock in OpenAFS 1.4.11 (Solaris 5.10) In-Reply-To: <20100409133823.36f41ce3.adeason@sinenomine.net> References: <595.1270834565@pabst.cs.uwm.edu> <20100409133823.36f41ce3.adeason@sinenomine.net> Message-ID: On Fri, Apr 9, 2010 at 2:38 PM, Andrew Deason wrote: > On Fri, 9 Apr 2010 14:27:24 -0400 > Derrick Brashear wrote: > >> Almost certainly a dcache lock (which cmdebug doesn't show, alas) >> involved here and causing this. >> >> I suppose the other thing which may help: can you collect fstrace for >> this? > > What about the kernel stack trace for the proc(s) from mdb? Or do you > know where we're hanging? nope. i figured fstrace would make it easier to guess that but jumping directly to a stack trace is probabyl a fine course of action. -- Derrick From adeason@sinenomine.net Fri Apr 9 20:45:32 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Fri, 9 Apr 2010 14:45:32 -0500 Subject: [OpenAFS] Re: deadlock in OpenAFS 1.4.11 (Solaris 5.10) References: <595.1270834565@pabst.cs.uwm.edu> <20100409133823.36f41ce3.adeason@sinenomine.net> Message-ID: <20100409144532.40a800cf.adeason@sinenomine.net> On Fri, 9 Apr 2010 14:48:34 -0400 Derrick Brashear wrote: > > What about the kernel stack trace for the proc(s) from mdb? Or do you > > know where we're hanging? > > nope. i figured fstrace would make it easier to guess that but jumping > directly to a stack trace is probabyl a fine course of action. John, if you want to do this, do the following for each PID listed in that cmdebug output: ("$pid", "ffffffffaddress1", and "ffffffffaddress2" etc are placeholders) # mdb -k > 0t$pid::pid2proc | ::threadlist ADDR PROC LWP CMD/LWPID ffffffffaddress1 ffffffffaddress2 0 XXX/YYY > ffffffffaddress2::findstack So, as an example, looking at process 674: > 0t674::pid2proc | ::threadlist ADDR PROC LWP CMD/LWPID ffffffff83e74908 ffffffff832de020 0 /239 > ffffffff832de020::findstack [stack trace] (make sure you don't see anything sensitive in there, though I don't think there would be) fstrace may give more information on how we came to that point, but this should tell us why someone is hanging with the lock we're waiting for... -- Andrew Deason adeason@sinenomine.net From boyland@cs.uwm.edu Fri Apr 9 22:57:37 2010 From: boyland@cs.uwm.edu (John Tang Boyland) Date: Fri, 09 Apr 2010 16:57:37 -0500 Subject: [OpenAFS] deadlock in OpenAFS 1.4.11 (Solaris 5.10) In-Reply-To: Your message of "Fri, 09 Apr 2010 14:21:31 EDT." Message-ID: <1640.1270850257@pabst.cs.uwm.edu> Derrick Brashear writes: ] [...] ] John Boyland writes: ] <...> ] > ** Cache entry @ 0xa26da3f0 for 1.536875155.530.1418 [cs.uwm.edu] ] >    locks: (reader_waiting, write_locked(pid:17732 at:250), 2 waiters) ] >           26532 bytes  DV          197  refcnt     3 ] >    callback 00000000   expires 1270781645 ] >    1 opens     0 writers ] >    normal file ] >    states (0x0) ] ] ok, that's the rdwr vnode op, so that makes some sense. ] ] > ** Cache entry @ 0xa27651d0 for 1.536875155.608.1458 [cs.uwm.edu] ] >    locks: (upgrade_waiting, write_locked(pid:17679 at:66), 12 waiters) ] >        19094744 bytes  DV          109  refcnt    13 ] >    callback 00000000   expires 1270782798 ] >    0 opens     0 writers ] >    normal file ] >    states (0x0) ] ] and 66 is GetDCache ] > The person who generated this process says they were running aprocess ] > that was writing debugging output redirected into a file and there was a ] > loop so the file got very large. ] ] hm. did it really hang, or just get very slow? I was told that at first things got slow, but then it stopped altogether. They then moved to a different machine and read the file from there. Meanwhile, on the bad machine, ANY afs file action hangs. ] > ** Cache entry @ 0xa2710018 for 1.536875155.610.1499 [cs.uwm.edu] ] >    locks: (none_waiting, write_locked(pid:17889 at:250)) ] >           23240 bytes  DV            1  refcnt     1 ] >    callback 00000000   expires 1270782798 ] >    1 opens     0 writers ] >    normal file ] >    states (0x0) ] > ** Cache entry @ 0xa26bf000 for 1.536873892.1.1 [cs.uwm.edu] ] >    locks: (writer_waiting, 7 read_locks(pid:18421), 41 waiters) ] >            2048 bytes  DV            8  refcnt    49 ] >    callback 00000000   expires 1270774475 ] >    0 opens     0 writers ] >    volume root ] >    states (0x4), read-only This last one (with 41 waiters) is /afs: good% /usr/afsws/bin/fs getfid /afs File /afs (536873892.1.1) contained in volume 536873892 (on the bad machine, I can't touch /usr/afsws of course since it is a link into /afs) cmdebug now shows 71 waiters -- of course it increases whenever someone touches afs and joins the tarbaby. ] Almost certainly a dcache lock (which cmdebug doesn't show, alas) ] involved here and causing this. ] ] I suppose the other thing which may help: can you collect fstrace for this? bad# ./fstrace setset cm -active [ during this time I touch /afs/not-here and freeze ] bad# ./fstrace dump cm AFS Trace Dump - Date: Fri Apr 9 16:50:14 2010 Found 1 logs. Contents of log cmfx: AFS Trace Dump - Completed bad# ./fstrace setset cm -inactive John Boyland From shadow@gmail.com Sat Apr 10 05:51:29 2010 From: shadow@gmail.com (Derrick Brashear) Date: Sat, 10 Apr 2010 00:51:29 -0400 Subject: [OpenAFS] Reminder! Early Registration Discount for the OpenAFS & Kerberos Best Practices Workshop 2010 ends April 14! Message-ID: Registration for the OpenAFS & Kerberos Best Practices Workshop is available on the website, http://workshop.openafs.org/. Register by April 14, 2010 to get the best prices. AFS and Kerberos tutorials are $100 each, the Workshop itself is $150, or register for all three for only $300. After April 14, prices will go up, so register now and save. A tentative schedule is available. Further details, including social events, is still forthcoming. Hotel and travel information is also available. We'll be looking forward to meeting you at Illinois next month! Derrick, for the Workshop Organizers http://workshop.openafs.org/ From boyland@cs.uwm.edu Sat Apr 10 18:54:30 2010 From: boyland@cs.uwm.edu (John Tang Boyland) Date: Sat, 10 Apr 2010 12:54:30 -0500 Subject: [OpenAFS] Re: deadlock in OpenAFS 1.4.11 (Solaris 5.10) In-Reply-To: Your message of "Sat, 10 Apr 2010 12:01:03 EDT." Message-ID: <2575.1270922070@pabst.cs.uwm.edu> [BTW: I get openafs-info messages digested.] Andrew Deason wrote: ] On Fri, 9 Apr 2010 14:48:34 -0400 ] Derrick Brashear wrote: ] ] > > What about the kernel stack trace for the proc(s) from mdb? Or do you ] > > know where we're hanging? ] > ] > nope. i figured fstrace would make it easier to guess that but jumping ] > directly to a stack trace is probabyl a fine course of action. ] ] John, if you want to do this, do the following for each PID listed in ] that cmdebug output: ] ] ("$pid", "ffffffffaddress1", and "ffffffffaddress2" etc are placeholders) ] ] # mdb -k ] > 0t$pid::pid2proc | ::threadlist ] ADDR PROC LWP CMD/LWPID ] ffffffffaddress1 ffffffffaddress2 0 XXX/YYY ] > ffffffffaddress2::findstack ] ] So, as an example, looking at process 674: ] ] > 0t674::pid2proc | ::threadlist ] ADDR PROC LWP CMD/LWPID ] ffffffff83e74908 ffffffff832de020 0 /239 ] > ffffffff832de020::findstack ] [stack trace] Thanks for the detailed instructions. I never even knew mdb existed. BTW: process 17679 is the one writing the LONG file that seemed to initiate the deadlock. I notice it is inside "FetchWholeEnchilada". process 18421 is the one listed for the cmdebug entry for /afs: the root directory of the whole AFS system and the cm entry with the most waiters. > 0t17732::pid2proc | ::threadlist ADDR PROC LWP CMD/LWPID fffffe84baca3a98 fffffe8925fa2500 0 /239 > fffffe8925fa2500::findstack stack pointer for thread fffffe8925fa2500: fffffe8002fce5a0 [ fffffe8002fce5a0 _resume_from_idle+0xf8() ] fffffe8002fce5d0 swtch+0x110() fffffe8002fce5f0 cv_wait+0x68() fffffe8002fce640 afs_osi_Sleep+0x99() fffffe8002fce6c0 Afs_Lock_Obtain+0x1cb() fffffe8002fce780 afs_putpage+0x14a() fffffe8002fce7f0 osi_VM_GetDownD+0xe8() fffffe8002fce9c0 afs_GetDownD+0x7ed() fffffe8002fceb90 afs_GetDCache+0x713() fffffe8002fcecc0 afs_nfsrdwr+0xd19() fffffe8002fced30 afs_vmread+0x89() fffffe8002fced80 fop_read+0x31() fffffe8002fceeb0 read+0x188() fffffe8002fceec0 read32+0xe() fffffe8002fcef10 sys_syscall32+0x101() > 0t17679::pid2proc | ::threadlist ADDR PROC LWP CMD/LWPID fffffe84c16f55a8 fffffe84bae85500 0 /239 > fffffe84bae85500::findstack stack pointer for thread fffffe84bae85500: fffffe8003244640 [ fffffe8003244640 _resume_from_idle+0xf8() ] fffffe8003244670 swtch+0x110() fffffe8003244690 cv_wait+0x68() fffffe80032446e0 afs_osi_Sleep+0x99() fffffe8003244760 Afs_Lock_Obtain+0x1cb() fffffe8003244820 afs_putpage+0x14a() fffffe8003244890 osi_VM_GetDownD+0xe8() fffffe8003244a60 afs_GetDownD+0x7ed() fffffe8003244c30 afs_GetDCache+0x713() fffffe8003244cb0 FetchWholeEnchilada+0xf4() fffffe8003244d80 afs_remove+0x7eb() fffffe8003244de0 gafs_remove+0x4f() fffffe8003244e10 fop_remove+0x25() fffffe8003244ea0 vn_removeat+0x228() fffffe8003244eb0 vn_remove+0x12() fffffe8003244ec0 unlink+0xd() fffffe8003244f10 sys_syscall32+0x101() > 0t17889::pid2proc | ::threadlist ADDR PROC LWP CMD/LWPID fffffe84b1c218d0 fffffe8926218840 0 /239 > fffffe8926218840::findstack stack pointer for thread fffffe8926218840: fffffe8001cff5a0 [ fffffe8001cff5a0 _resume_from_idle+0xf8() ] fffffe8001cff5d0 swtch+0x110() fffffe8001cff5f0 cv_wait+0x68() fffffe8001cff640 afs_osi_Sleep+0x99() fffffe8001cff6c0 Afs_Lock_Obtain+0x1cb() fffffe8001cff780 afs_putpage+0x14a() fffffe8001cff7f0 osi_VM_GetDownD+0xe8() fffffe8001cff9c0 afs_GetDownD+0x7ed() fffffe8001cffb90 afs_GetDCache+0x713() fffffe8001cffcc0 afs_nfsrdwr+0xd19() fffffe8001cffd30 afs_vmread+0x89() fffffe8001cffd80 fop_read+0x31() fffffe8001cffeb0 read+0x188() fffffe8001cffec0 read32+0xe() fffffe8001cfff10 sys_syscall32+0x101() > 0t18421::pid2proc | ::threadlist ADDR PROC LWP CMD/LWPID fffffe84b6b60de0 fffffe8905b2d280 0 /239 > fffffe8905b2d280::findstack stack pointer for thread fffffe8905b2d280: fffffe8000365300 [ fffffe8000365300 _resume_from_idle+0xf8() ] fffffe8000365330 swtch+0x110() fffffe8000365350 cv_wait+0x68() fffffe80003653a0 afs_osi_Sleep+0x99() fffffe8000365420 Afs_Lock_Obtain+0x1cb() fffffe80003654e0 afs_putpage+0x14a() fffffe8000365550 osi_VM_GetDownD+0xe8() fffffe8000365720 afs_GetDownD+0x7ed() fffffe80003658f0 afs_GetDCache+0x6f8() fffffe8000365a20 afs_lookup+0x700() fffffe8000365aa0 gafs_lookup+0x70() fffffe8000365af0 fop_lookup+0x35() fffffe8000365cc0 lookuppnvp+0x1bf() fffffe8000365d30 lookuppnat+0xf9() fffffe8000365df0 lookupnameat+0x86() fffffe8000365e50 cstatat_getvp+0x115() fffffe8000365eb0 cstatat64_32+0x4c() fffffe8000365ec0 stat64_32+0x22() fffffe8000365f10 sys_syscall32+0x101() > 0t17834::pid2proc | ::threadlist ADDR PROC LWP CMD/LWPID fffffe84c2cbc008 fffffe8516ab2720 0 ?????????K?/239 > fffffe8516ab2720::findstack stack pointer for thread fffffe8516ab2720: fffffe8002fda5a0 [ fffffe8002fda5a0 _resume_from_idle+0xf8() ] fffffe8002fda5d0 swtch+0x110() fffffe8002fda5f0 cv_wait+0x68() fffffe8002fda640 afs_osi_Sleep+0x99() fffffe8002fda6c0 Afs_Lock_Obtain+0x1cb() fffffe8002fda780 afs_putpage+0x14a() fffffe8002fda7f0 osi_VM_GetDownD+0xe8() fffffe8002fda9c0 afs_GetDownD+0x7ed() fffffe8002fdab90 afs_GetDCache+0x713() fffffe8002fdacc0 afs_nfsrdwr+0xd19() fffffe8002fdad30 afs_vmread+0x89() fffffe8002fdad80 fop_read+0x31() fffffe8002fdaeb0 read+0x188() fffffe8002fdaec0 read32+0xe() fffffe8002fdaf10 sys_syscall32+0x101() > From adam@megacz.com Mon Apr 12 04:13:41 2010 From: adam@megacz.com (Adam Megacz) Date: Mon, 12 Apr 2010 03:13:41 +0000 Subject: [OpenAFS] sqlite on AFS will not work, even with whole-file locking References: <1931138644.1895.1270750370350.JavaMail.root@thunderbeast.private.linuxbox.com> <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> Message-ID: Brandon Simmons writes: > Thanks for the response. It seems like whole-file locking in sqlite > would be a good choice for me in any case, > In a situation where the whole-file locking scheme is used, would AFS > be an acceptable choice? Would it be better than NFS? I had the same idea, and tried it. It does not work. Your databases will get corrupted. I never figured out why, although I did confirm that sqlite was in fact requesting only whole-file locks. It would be nice if it worked, though. There are a lot of applications out there where writes to the database are extremely rare, so invalidating all the clients' caches is not a problem. - a From adeason@sinenomine.net Mon Apr 12 05:14:18 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Sun, 11 Apr 2010 23:14:18 -0500 Subject: [OpenAFS] Re: deadlock in OpenAFS 1.4.11 (Solaris 5.10) References: <2575.1270922070@pabst.cs.uwm.edu> Message-ID: <20100411231418.acf4f0cf.adeason@sinenomine.net> On Sat, 10 Apr 2010 12:54:30 -0500 John Tang Boyland wrote: > [mdb] Thanks for those. I'm not sure myself what's going on, but perhaps some discussion will help... You appear to be running out of cache files, though, by the way. If you increase the size of your cache (or maybe even just the number of files), it may make this less likely to occur. > BTW: > process 17679 is the one writing the LONG file that seemed to > initiate the deadlock. I notice it is inside "FetchWholeEnchilada". It appears to have unlinked the file while it was open; does that sound correct? > fffffe8003244cb0 FetchWholeEnchilada+0xf4() > fffffe8003244d80 afs_remove+0x7eb() Can someone explain this, by the way? If I'm reading this correctly, we fetch/cache the entire file contents of a file if it's unlinked from under a process... Why? > fffffe8002fda5d0 swtch+0x110() > fffffe8002fda5f0 cv_wait+0x68() > fffffe8002fda640 afs_osi_Sleep+0x99() > fffffe8002fda6c0 Afs_Lock_Obtain+0x1cb() > fffffe8002fda780 afs_putpage+0x14a() > fffffe8002fda7f0 osi_VM_GetDownD+0xe8() > fffffe8002fda9c0 afs_GetDownD+0x7ed() > fffffe8002fdab90 afs_GetDCache+0x713() So, all of these are waiting to free up a dcache entry. I'm not in this code very much, but here's a guess... someone tell me if this makes any sense. What looks like may be possible is that some process locks vcache V1, and tries to get a dcache entry for it; it tries to create a new dcache entry and tries to free up a dcache entry (D1) because we're out. D1 has mapped pages (or whatever IFAnyPages means), and we need to invalidate the pages, so we need to lock D1's vcache. If D1's vcache is the same as vcache V1, we have deadlock. This makes sense to me to see while FetchWholeEnchilada is running, since fetching the later chunks may be trying to free up the earlier chunks fetched in the same file... If that is plausible, I think potential solutions include dropping the V1 lock before GetDownD (I assume this isn't possible, or a lot of things assume this doesn't happen and is a lot of work to make right, etc)... or, passing the avc into GetDownD, and have GetDownD skip dcaches that need page invalidation that have the same vcache as the one passed in. That way we sleep and retry (although still while holding the V1 lock...) -- Andrew Deason adeason@sinenomine.net From shadow@gmail.com Mon Apr 12 05:34:23 2010 From: shadow@gmail.com (Derrick Brashear) Date: Mon, 12 Apr 2010 00:34:23 -0400 Subject: [OpenAFS] sqlite on AFS will not work, even with whole-file locking In-Reply-To: References: <1931138644.1895.1270750370350.JavaMail.root@thunderbeast.private.linuxbox.com> <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> Message-ID: On Sun, Apr 11, 2010 at 11:13 PM, Adam Megacz wrote: > > Brandon Simmons writes: >> Thanks for the response. It seems like whole-file locking in sqlite >> would be a good choice for me in any case, > >> In a situation where the whole-file locking scheme is used, would AFS >> be an acceptable choice? Would it be better than NFS? > > I had the same idea, and tried it. =A0It does not work. =A0Your databases > will get corrupted. =A0I never figured out why, although I did confirm > that sqlite was in fact requesting only whole-file locks. > > It would be nice if it worked, though. =A0There are a lot of applications > out there where writes to the database are extremely rare, so > invalidating all the clients' caches is not a problem. do you happen to know what the corruption looked like (blocks of zeroes, just not readable, something else) --=20 Derrick From atro.tossavainen+openafs@helsinki.fi Mon Apr 12 13:29:11 2010 From: atro.tossavainen+openafs@helsinki.fi (Atro Tossavainen) Date: Mon, 12 Apr 2010 15:29:11 +0300 (EEST) Subject: [OpenAFS] Ubik problem Message-ID: <201004121229.o3CCTBgc010382@ruuvi.it.helsinki.fi> I recently changed one of our cell's db servers from IBM AFS on Solaris 8 / SPARC to OpenAFS on Solaris 10 / x64. The other one remains on IBM AFS on Solaris 8 for what will hopefully be a very short time until I migrate it over to S10x64 as well. I've seen some strange database problems recently, and no wonder: the OpenAFS server seems to be thinking its IP address is what it would be if you reversed the octets. The public db servers for biocenter.helsinki.fi are 128.214.58.174 and 128.214.88.114. The former seems to have some strange ideas about 174.58.214.128 being somehow involved. Please see udebug -long output from both: sun4x_58 # /usr/afs/bin/udebug 128.214.88.114 7002 -long Host's addresses are: 128.214.88.114 10.0.0.3 172.16.0.1 172.17.0.1 172.18.0.1 Host's 128.214.88.114 time is Mon Apr 12 15:17:30 2010 Local time is Mon Apr 12 15:17:34 2010 (time differential 4 secs) Last yes vote for 128.214.88.114 was 1 secs ago (not sync site); Last vote started 1 secs ago (at Mon Apr 12 15:17:33 2010) Local db version is 1270721316.13 I am not sync site Lowest host 128.214.88.114 was set 1 secs ago Sync host 0.0.0.0 was set 1271074650 secs ago Sync site's db version is 1270721316.13 0 locked pages, 0 of them for write Server( 128.214.58.174 ): (db 0.0) last vote rcvd 1 secs ago (at Mon Apr 12 15:17:33 2010), last beacon sent 1 secs ago (at Mon Apr 12 15:17:33 2010), last vote was no dbcurrent=0, up=1 beaconSince=1 sunx86_510 # /usr/afs/bin/udebug 128.214.58.174 7002 -long Host's addresses are: 128.214.58.174 Host's 128.214.58.174 time is Mon Apr 12 15:17:27 2010 Local time is Mon Apr 12 15:17:28 2010 (time differential 1 secs) Last yes vote for 174.58.214.128 was 2 secs ago (sync site); Last vote started 2 secs ago (at Mon Apr 12 15:17:26 2010) Local db version is 1270721316.13 I am sync site until 58 secs from now (at Mon Apr 12 15:18:26 2010) (2 servers) Recovery state 1f Sync site's db version is 1270721316.13 0 locked pages, 0 of them for write Server (128.214.88.114 10.0.0.3 172.16.0.1 172.17.0.1 172.18.0.1): (db 1270721316.13) last vote rcvd 2 secs ago (at Mon Apr 12 15:17:26 2010), last beacon sent 2 secs ago (at Mon Apr 12 15:17:26 2010), last vote was no dbcurrent=1, up=1 beaconSince=1 -- Atro Tossavainen (Mr.) / The Institute of Biotechnology at Systems Analyst, Techno-Amish & / the University of Helsinki, Finland, +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own. < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS From jaltman@secure-endpoints.com Mon Apr 12 13:36:44 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Mon, 12 Apr 2010 08:36:44 -0400 Subject: [OpenAFS] Ubik problem In-Reply-To: <201004121229.o3CCTBgc010382@ruuvi.it.helsinki.fi> References: <201004121229.o3CCTBgc010382@ruuvi.it.helsinki.fi> Message-ID: <4BC313DC.3000401@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms040206060403060600000404 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/12/2010 8:29 AM, Atro Tossavainen wrote: > I recently changed one of our cell's db servers from IBM AFS on > Solaris 8 / SPARC to OpenAFS on Solaris 10 / x64. The other one > remains on IBM AFS on Solaris 8 for what will hopefully be a very > short time until I migrate it over to S10x64 as well. >=20 > I've seen some strange database problems recently, and no wonder: the > OpenAFS server seems to be thinking its IP address is what it would be > if you reversed the octets. >=20 > The public db servers for biocenter.helsinki.fi are 128.214.58.174 > and 128.214.88.114. The former seems to have some strange ideas about > 174.58.214.128 being somehow involved. What version of OpenAFS? What does the address report if you use the udebug from the sparc system to query the x86 system? I believe this is just a reporting problem with udebug client that was fixed on master. --------------ms040206060403060600000404 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MTIxMjM2NDRaMCMGCSqGSIb3DQEJBDEWBBQwyiWI JqJRQ78EgbYYJvntRGsVjzBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAG3zMQKVV9unkn6JXkJg+hNo8n1zAy77Cp9J z6dQpDcd7HW+LumLfps/zKj6L9egbpRXn8CpB3zkqDPFl4rX9+pjsGopWvKeE+jIDYgpWDqh PjQS90lzWTCQEuQ2p4dFEhxMp6C0KsTkFUnezL7eJCAoKlsy3j6GVJSlsl6oAYk+wLMAUJAW 91/2QVhNxwjDsNGQi7+TV94YnMwkHMZi1CDAVF0t+97q19B71LqERP7GvWX6Pfl6Ae8QOCEJ +U+fjy8uOJWuxzv4zBEYYj44/C2raquX/Z4ZfextI8NP1v9EbQJqSd3DDUz4GRm7+kdfl8vt aMpkMpLzHV1VXq9O8nsAAAAAAAA= --------------ms040206060403060600000404-- From atro.tossavainen+openafs@helsinki.fi Mon Apr 12 13:54:44 2010 From: atro.tossavainen+openafs@helsinki.fi (Atro Tossavainen) Date: Mon, 12 Apr 2010 15:54:44 +0300 (EEST) Subject: [OpenAFS] Ubik problem In-Reply-To: <4BC313DC.3000401@secure-endpoints.com> Message-ID: <201004121254.o3CCsikk011778@ruuvi.it.helsinki.fi> Jeffrey, thanks for the superfast response. > What version of OpenAFS? What does the address report if you use > the udebug from the sparc system to query the x86 system? I believe > this is just a reporting problem with udebug client that was fixed > on master. OpenAFS 1.4.12. The a.b.c.d becoming d.c.b.a seems to be just cosmetic, but there are some other issues. Out of 128.214.58.174 and 128.214.88.114, the lowest numbered host certainly isn't 128.214.88.114, and I'm slightly worried that the report says the database version is 0.0 on the other host. sun4x_58 # /usr/afs/bin/udebug 128.214.58.174 7002 -long Host's addresses are: 128.214.58.174 Host's 128.214.58.174 time is Mon Apr 12 15:50:20 2010 Local time is Mon Apr 12 15:50:24 2010 (time differential 4 secs) Last yes vote for 128.214.58.174 was 9 secs ago (sync site); <----- indeed Last vote started 9 secs ago (at Mon Apr 12 15:50:15 2010) Local db version is 1270721316.13 I am sync site until 51 secs from now (at Mon Apr 12 15:51:15 2010) (2 servers) Recovery state 1f Sync site's db version is 1270721316.13 0 locked pages, 0 of them for write Server( 128.214.88.114 10.0.0.3 172.16.0.1 172.17.0.1 172.18.0.1 ): (db 1270721316.13) last vote rcvd 9 secs ago (at Mon Apr 12 15:50:15 2010), last beacon sent 9 secs ago (at Mon Apr 12 15:50:15 2010), last vote was no dbcurrent=1, up=1 beaconSince=1 And indeed: sunx86_510 # /usr/afs/bin/udebug 128.214.88.114 7002 -long Host's addresses are: 128.214.88.114 10.0.0.3 172.16.0.1 172.17.0.1 172.18.0.1 Host's 128.214.88.114 time is Mon Apr 12 15:51:10 2010 Local time is Mon Apr 12 15:51:10 2010 (time differential 0 secs) Last yes vote for 114.88.214.128 was 11 secs ago (not sync site); <--- Last vote started 11 secs ago (at Mon Apr 12 15:50:59 2010) Local db version is 1270721316.13 I am not sync site Lowest host 128.214.88.114 was set 11 secs ago <---- this can't be right Sync host 0.0.0.0 was set 1271076670 secs ago Sync site's db version is 1270721316.13 0 locked pages, 0 of them for write Server (128.214.58.174): (db 0.0) <---- and this must be wrong too last vote rcvd 11 secs ago (at Mon Apr 12 15:50:59 2010), last beacon sent 11 secs ago (at Mon Apr 12 15:50:59 2010), last vote was no dbcurrent=0, up=1 beaconSince=1 -- Atro Tossavainen (Mr.) / The Institute of Biotechnology at Systems Analyst, Techno-Amish & / the University of Helsinki, Finland, +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own. < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS From jaltman@secure-endpoints.com Mon Apr 12 14:21:30 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Mon, 12 Apr 2010 09:21:30 -0400 Subject: [OpenAFS] Ubik problem In-Reply-To: <201004121254.o3CCsikk011778@ruuvi.it.helsinki.fi> References: <201004121254.o3CCsikk011778@ruuvi.it.helsinki.fi> Message-ID: <4BC31E5A.3030009@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms060702040808020809040203 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/12/2010 8:54 AM, Atro Tossavainen wrote: > Jeffrey, thanks for the superfast response. >=20 >> What version of OpenAFS? What does the address report if you use >> the udebug from the sparc system to query the x86 system? I believe >> this is just a reporting problem with udebug client that was fixed >> on master. >=20 > OpenAFS 1.4.12. >=20 > The a.b.c.d becoming d.c.b.a seems to be just cosmetic, but there are > some other issues. Out of 128.214.58.174 and 128.214.88.114, the > lowest numbered host certainly isn't 128.214.88.114, actually it is because that server is reporting multiple addresses: Server( 128.214.88.114 10.0.0.3 172.16.0.1 172.17.0.1 172.18.0.1 ) several of which are lower than 128.214.58.174. What are these other interface addresses are do you expect them to be used for ubik synchronization? > and I'm slightly > worried that the report says the database version is 0.0 on the other > host. The db version is only reported by the server that is currently the sync site. This is not a concern. --------------ms060702040808020809040203 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MTIxMzIxMzBaMCMGCSqGSIb3DQEJBDEWBBTDmvGc 5RuR6g1oK5G1C+fG1bloWjBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAE1qP7cwog5NMRQjdGlbcRjXNxacoDRqlh+l 074Lyh0YtH54pVMspq3qQCkiLAhtBxKmn6UWOL/8W6ZOtnA7r7n2xYpY8LkER7Wp6J5bz8Gm WmR3K10uASiW3SUcNNcAsI0RBEtUcXa2IJfI8mdA/kK3RUmhbwnrtmzbaQfrnwesJP4YXl5H sUjlv389h1ueAw3yOncqKaLbZUQu4mB/PRys1pDT3hhoX4O3nbPbkLhADh1FleuGpSBXaNP2 tPQlH578AsEPv/4bpqPX37uBdBzWbvzzaGKyRqaLcQdvcXTL9BvcrD61tcoooIrYyz9q1php RJiGjqfFh7L1Vhk/mnwAAAAAAAA= --------------ms060702040808020809040203-- From adeason@sinenomine.net Mon Apr 12 15:03:54 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Mon, 12 Apr 2010 09:03:54 -0500 Subject: [OpenAFS] Re: Ubik problem References: <201004121254.o3CCsikk011778@ruuvi.it.helsinki.fi> <4BC31E5A.3030009@secure-endpoints.com> Message-ID: <20100412090354.c7f567e4.adeason@sinenomine.net> On Mon, 12 Apr 2010 09:21:30 -0400 Jeffrey Altman wrote: > On 4/12/2010 8:54 AM, Atro Tossavainen wrote: > > Jeffrey, thanks for the superfast response. > > > >> What version of OpenAFS? What does the address report if you use > >> the udebug from the sparc system to query the x86 system? I believe > >> this is just a reporting problem with udebug client that was fixed > >> on master. Yeah, 63fe055ecd13c93a3a6070a15a745ace2e420817, not on 1.4 yet. It's just cosmetic. > > The a.b.c.d becoming d.c.b.a seems to be just cosmetic, but there are > > some other issues. Out of 128.214.58.174 and 128.214.88.114, the > > lowest numbered host certainly isn't 128.214.88.114, > > actually it is because that server is reporting multiple addresses: > > Server( 128.214.88.114 10.0.0.3 172.16.0.1 172.17.0.1 172.18.0.1 ) > > several of which are lower than 128.214.58.174. What are these other > interface addresses are do you expect them to be used for ubik > synchronization? If you want the other db server to be the lowest host, you can restrict the addresses advertised with NetInfo/NetRestrict. But if that doesn't matter to you, there doesn't seem to be a problem. Are you seeing other issues with the database itself? -- Andrew Deason adeason@sinenomine.net From boyland@cs.uwm.edu Mon Apr 12 15:07:58 2010 From: boyland@cs.uwm.edu (John Tang Boyland) Date: Mon, 12 Apr 2010 09:07:58 -0500 Subject: [OpenAFS] Re: deadlock in OpenAFS 1.4.11 (Solaris 5.10) In-Reply-To: Your message of "Mon, 12 Apr 2010 09:22:00 EDT." Message-ID: <4382.1271081278@pabst.cs.uwm.edu> Andrew Deason writes ] John Tang Boyland wrote: ] ] > [mdb] ] ] Thanks for those. I'm not sure myself what's going on, but perhaps some ] discussion will help... ] ] You appear to be running out of cache files, though, by the way. If you ] increase the size of your cache (or maybe even just the number of ] files), it may make this less likely to occur. OK. I'll do that the next time we reboot. The cacheinfo is rather small (25000K). (In fact, I guess that's why other people haven't noticed the problem. Running with a 25MB disk cache is pretty ridiculous.) ] > BTW: ] > process 17679 is the one writing the LONG file that seemed to ] > initiate the deadlock. I notice it is inside "FetchWholeEnchilada". ] ] It appears to have unlinked the file while it was open; does that sound ] correct? Possibly: process 17679 is listed as "make test". I'm guessing the user was noticing things were going slow and control-C'ed the make process, and "make" decided to delete the output file. But I don't know for sure. ] > fffffe8003244cb0 FetchWholeEnchilada+0xf4() ] > fffffe8003244d80 afs_remove+0x7eb() ] ] Can someone explain this, by the way? If I'm reading this correctly, we ] fetch/cache the entire file contents of a file if it's unlinked from ] under a process... Why? ] ] > fffffe8002fda5d0 swtch+0x110() ] > fffffe8002fda5f0 cv_wait+0x68() ] > fffffe8002fda640 afs_osi_Sleep+0x99() ] > fffffe8002fda6c0 Afs_Lock_Obtain+0x1cb() ] > fffffe8002fda780 afs_putpage+0x14a() ] > fffffe8002fda7f0 osi_VM_GetDownD+0xe8() ] > fffffe8002fda9c0 afs_GetDownD+0x7ed() ] > fffffe8002fdab90 afs_GetDCache+0x713() ] ] So, all of these are waiting to free up a dcache entry. I'm not in this ] code very much, but here's a guess... someone tell me if this makes any ] sense. ] ] What looks like may be possible is that some process locks vcache V1, ] and tries to get a dcache entry for it; it tries to create a new dcache ] entry and tries to free up a dcache entry (D1) because we're out. D1 has ] mapped pages (or whatever IFAnyPages means), and we need to invalidate ] the pages, so we need to lock D1's vcache. If D1's vcache is the same as ] vcache V1, we have deadlock. This makes sense to me to see while ] FetchWholeEnchilada is running, since fetching the later chunks may be ] trying to free up the earlier chunks fetched in the same file... ] ] If that is plausible, I think potential solutions include dropping the ] V1 lock before GetDownD (I assume this isn't possible, or a lot of ] things assume this doesn't happen and is a lot of work to make right, ] etc)... or, passing the avc into GetDownD, and have GetDownD skip ] dcaches that need page invalidation that have the same vcache as the one ] passed in. That way we sleep and retry (although still while holding the ] V1 lock...) ] ] -- ] Andrew Deason ] adeason@sinenomine.net BTW: Is there any more useful information I could get from the machine or can we reboot it? Please reply by email to boyland@cs.uwm.edu. From shadow@gmail.com Mon Apr 12 15:14:40 2010 From: shadow@gmail.com (Derrick Brashear) Date: Mon, 12 Apr 2010 10:14:40 -0400 Subject: [OpenAFS] Re: deadlock in OpenAFS 1.4.11 (Solaris 5.10) In-Reply-To: <4382.1271081278@pabst.cs.uwm.edu> References: <4382.1271081278@pabst.cs.uwm.edu> Message-ID: you might as well reboot it. i suspect (and wondered before) if the real issue was not deadlock but that the machine simply went into a loop, and with a cache that small it's likely it did. not the best behavior, of course but not the most urgent thing to pursue at the moment. On Mon, Apr 12, 2010 at 10:07 AM, John Tang Boyland wrote: > Andrew Deason writes > ] John Tang Boyland wrote: > ] > ] > [mdb] > ] > ] Thanks for those. I'm not sure myself what's going on, but perhaps some > ] discussion will help... > ] > ] You appear to be running out of cache files, though, by the way. If you > ] increase the size of your cache (or maybe even just the number of > ] files), it may make this less likely to occur. > > OK. =A0I'll do that the next time we reboot. =A0The cacheinfo is > rather small (25000K). > > (In fact, I guess that's why other people haven't noticed the problem. > Running with a 25MB disk cache is pretty ridiculous.) > > ] > BTW: > ] > process 17679 is the one writing the LONG file that seemed to > ] > initiate the deadlock. =A0I notice it is inside "FetchWholeEnchilada"= . > ] > ] It appears to have unlinked the file while it was open; does that sound > ] correct? > > Possibly: process 17679 is listed as "make test". > I'm guessing the user was noticing > things were going slow and control-C'ed the make process, and "make" > decided to delete the output file. > But I don't know for sure. > > ] > =A0 fffffe8003244cb0 FetchWholeEnchilada+0xf4() > ] > =A0 fffffe8003244d80 afs_remove+0x7eb() > ] > ] Can someone explain this, by the way? If I'm reading this correctly, we > ] fetch/cache the entire file contents of a file if it's unlinked from > ] under a process... Why? > ] > ] > =A0 fffffe8002fda5d0 swtch+0x110() > ] > =A0 fffffe8002fda5f0 cv_wait+0x68() > ] > =A0 fffffe8002fda640 afs_osi_Sleep+0x99() > ] > =A0 fffffe8002fda6c0 Afs_Lock_Obtain+0x1cb() > ] > =A0 fffffe8002fda780 afs_putpage+0x14a() > ] > =A0 fffffe8002fda7f0 osi_VM_GetDownD+0xe8() > ] > =A0 fffffe8002fda9c0 afs_GetDownD+0x7ed() > ] > =A0 fffffe8002fdab90 afs_GetDCache+0x713() > ] > ] So, all of these are waiting to free up a dcache entry. I'm not in this > ] code very much, but here's a guess... someone tell me if this makes any > ] sense. > ] > ] What looks like may be possible is that some process locks vcache V1, > ] and tries to get a dcache entry for it; it tries to create a new dcache > ] entry and tries to free up a dcache entry (D1) because we're out. D1 ha= s > ] mapped pages (or whatever IFAnyPages means), and we need to invalidate > ] the pages, so we need to lock D1's vcache. If D1's vcache is the same a= s > ] vcache V1, we have deadlock. This makes sense to me to see while > ] FetchWholeEnchilada is running, since fetching the later chunks may be > ] trying to free up the earlier chunks fetched in the same file... > ] > ] If that is plausible, I think potential solutions include dropping the > ] V1 lock before GetDownD (I assume this isn't possible, or a lot of > ] things assume this doesn't happen and is a lot of work to make right, > ] etc)... or, passing the avc into GetDownD, and have GetDownD skip > ] dcaches that need page invalidation that have the same vcache as the on= e > ] passed in. That way we sleep and retry (although still while holding th= e > ] V1 lock...) > ] > ] -- > ] Andrew Deason > ] adeason@sinenomine.net > > BTW: Is there any more useful information I could get from the machine > or can we reboot it? =A0Please reply by email to boyland@cs.uwm.edu. > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info > --=20 Derrick From atro.tossavainen+openafs@helsinki.fi Mon Apr 12 22:25:51 2010 From: atro.tossavainen+openafs@helsinki.fi (Atro Tossavainen) Date: Tue, 13 Apr 2010 00:25:51 +0300 (EEST) Subject: [OpenAFS] Ubik problem In-Reply-To: <4BC31E5A.3030009@secure-endpoints.com> Message-ID: <201004122125.o3CLPprA004189@ruuvi.it.helsinki.fi> Jeffrey, > actually it is because that server is reporting multiple addresses: > > Server( 128.214.88.114 10.0.0.3 172.16.0.1 172.17.0.1 172.18.0.1 ) > > several of which are lower than 128.214.58.174. What are these other > interface addresses are do you expect them to be used for ubik > synchronization? Private addresses for purposes other than AFS. I believe I am using NetRestrict to avoid the servers from picking up these: sun4x_58 # cat /usr/afs/local/NetRestrict M 10.255.255.255 M 172.255.255.255 M 192.168.255.255 I don't expect to see the RFC1918 addresses anywhere in connection with AFS. The NetRestrict file is unaltered as of Feb 13, 2009 and has been essentially identical for years. (I remember needing to raise a bug with IBM over wildcard support. PMR-73077... late 2004/early 2005. Not that it says anything to anybody outside IBM, probably. Merely using "255" wasn't enough, it needed adding "M" in front for wildcards to work and I think this was and is undocumented.) I have not had any database issues for as long as the other sun4x_58 host was the other database server. Andrew, > Are you seeing other issues with the database itself? Today, I could not open my screensaver, and I of course know my password. When I used kas to see if I had some problem with my account, "examine atossava" reported that the account did not exist. This was the case for a few other accounts as well - they didn't exist. Querying one database server at a time produced different results; correct on afsdb1 and kaserver producing gobbledygook on afsdb2, if I remember correctly. I needed to change the password for a user and bumped into an AFS error message that I have not seen before. I don't think I wrote it down anywhere, but basically I couldn't do anything with the account because of a key version mismatch. I rebooted the sun4x_58 server and it seemed to take a long time to reach quorum. After that, everything has been all right. I'm worried that I don't, despite having enabled logging, have much to report in the AuthLog. -- Atro Tossavainen (Mr.) / The Institute of Biotechnology at Systems Analyst, Techno-Amish & / the University of Helsinki, Finland, +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own. < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS From sxw@inf.ed.ac.uk Mon Apr 12 22:50:59 2010 From: sxw@inf.ed.ac.uk (Simon Wilkinson) Date: Mon, 12 Apr 2010 22:50:59 +0100 Subject: [OpenAFS] Ubik problem In-Reply-To: <201004122125.o3CLPprA004189@ruuvi.it.helsinki.fi> References: <201004122125.o3CLPprA004189@ruuvi.it.helsinki.fi> Message-ID: <57FB6B5C-AF7D-402D-8AA0-8642FCD06733@inf.ed.ac.uk> > Private addresses for purposes other than AFS. >=20 > I believe I am using NetRestrict to avoid the servers from picking up > these: We had this problem with our DB servers here. It would appear that you = also need to specify -rxbind, to stop the servers from sending packets = from interfaces that are in NetRestrict. Cheers, Simon. From adeason@sinenomine.net Mon Apr 12 22:58:45 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Mon, 12 Apr 2010 16:58:45 -0500 Subject: [OpenAFS] Re: Ubik problem References: <201004122125.o3CLPprA004189@ruuvi.it.helsinki.fi> <57FB6B5C-AF7D-402D-8AA0-8642FCD06733@inf.ed.ac.uk> Message-ID: <20100412165845.c5f44f42.adeason@sinenomine.net> On Mon, 12 Apr 2010 22:50:59 +0100 Simon Wilkinson wrote: > > Private addresses for purposes other than AFS. > > > > I believe I am using NetRestrict to avoid the servers from picking up > > these: > > We had this problem with our DB servers here. It would appear that you > also need to specify -rxbind, to stop the servers from sending packets > from interfaces that are in NetRestrict. Atro's problem appears to be that they are advertising the extra addresses, though, not that they're sending packets out over them. I've got a bad feeling that NetRestrict handling isn't doing endianness properly or something, but it's hard to imagine that going unnoticed... I'm checking, anyway. -- Andrew Deason adeason@sinenomine.net From jaltman@secure-endpoints.com Mon Apr 12 23:05:58 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Mon, 12 Apr 2010 18:05:58 -0400 Subject: [OpenAFS] Ubik problem In-Reply-To: <201004122125.o3CLPprA004189@ruuvi.it.helsinki.fi> References: <201004122125.o3CLPprA004189@ruuvi.it.helsinki.fi> Message-ID: <4BC39946.8020409@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms030007010102020605000500 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/12/2010 5:25 PM, Atro Tossavainen wrote: > Jeffrey, >=20 >> actually it is because that server is reporting multiple addresses: >> >> Server( 128.214.88.114 10.0.0.3 172.16.0.1 172.17.0.1 172.18.0.1 ) >> >> several of which are lower than 128.214.58.174. What are these other= >> interface addresses are do you expect them to be used for ubik >> synchronization? >=20 > Private addresses for purposes other than AFS. >=20 > I believe I am using NetRestrict to avoid the servers from picking up > these: >=20 > sun4x_58 # cat /usr/afs/local/NetRestrict > M 10.255.255.255 > M 172.255.255.255 > M 192.168.255.255 >=20 > I don't expect to see the RFC1918 addresses anywhere in connection > with AFS. The NetRestrict file is unaltered as of Feb 13, 2009 and > has been essentially identical for years. >=20 > (I remember needing to raise a bug with IBM over wildcard support. > PMR-73077... late 2004/early 2005. Not that it says anything to anybod= y > outside IBM, probably. Merely using "255" wasn't enough, it needed > adding "M" in front for wildcards to work and I think this was and is > undocumented.) >=20 > I have not had any database issues for as long as the other sun4x_58 > host was the other database server. The OpenAFS NetRestrict documentation does not mention the use of a preceding 'M'. http://docs.openafs.org/Reference/5/NetRestrict.html I suspect the change IBM implemented was never passed on to OpenAFS and as far as I can tell from the source its presence will invalidate the address and prevent it from being used as a filter. Jeffrey Altman --------------ms030007010102020605000500 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MTIyMjA1NThaMCMGCSqGSIb3DQEJBDEWBBRkNgKA A9GvxPC8bPyM47ksLB27sjBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAIfUvfYsxMk3G4j+w1pebPfdJkC04SxgDAbT 2UU9zZKk69eeeoxXf3t0fhcZMs6hJlqISHV94fnpqMBjjs/UHmsPGLEkDbUZEhjnzG0FIpW3 udGFMhZHo/lru6g9mrA7VfgspWsAHwUI7U55zGrpfI6wkfoliXwfkxa3S3SpOy5YmK5aH2Fb qoePy1A9wwApyB1JLkxeDMu+d0oychcfLOjlaa+cOSZJ5IqbHFUckXiY9b4YOPRX8G3htAus uefajf978EjJ8Y9uqu9B7oRmA8hMzIuxeuf7Zvi9EALbwoN82eOG4UoFAGgb2SvNKQ93q5qX amwt9kdTSgkw1/pH7HEAAAAAAAA= --------------ms030007010102020605000500-- From atro.tossavainen+openafs@helsinki.fi Tue Apr 13 06:43:47 2010 From: atro.tossavainen+openafs@helsinki.fi (Atro Tossavainen) Date: Tue, 13 Apr 2010 08:43:47 +0300 (EEST) Subject: [OpenAFS] Re: Ubik problem In-Reply-To: <20100412165845.c5f44f42.adeason@sinenomine.net> Message-ID: <201004130543.o3D5hlwL015540@ruuvi.it.helsinki.fi> Simon, > We had this problem with our DB servers here. It would appear that you > also need to specify -rxbind, to stop the servers from sending packets > from interfaces that are in NetRestrict. Which command(s) should be started with this flag? (Remember 128.214.88.114 is still on IBM AFS and probably does not support -rxbind if it's something that OpenAFS implemented post IBM.) Andrew, > Atro's problem appears to be that they are advertising the extra > addresses, though, not that they're sending packets out over them. What I don't get is why this would have changed transparently on the sun4x_58 server when I changed the *other* db server from sun4x_58 to sunx86_510 and from IBM AFS to OpenAFS. Jeffrey, > The OpenAFS NetRestrict documentation does not mention the use of a > preceding 'M'. Neither does the IBM documentation, which is what I said, I think. > I suspect the change IBM implemented was never passed on to OpenAFS > and as far as I can tell from the source its presence will invalidate > the address and prevent it from being used as a filter. On the IBM AFS sun4x_58 server where it was explicitly recommended by IBM AFS support in early 2005? :-) I'm not running the OpenAFS db servers. In fact, I seem to be running a mishmash of IBM AFS servers - the various components aren't even all the same version. >From my reading of IBM AFS patch READMEs, it appears that "M" appeared in AFS 3.6 Patch 13 (aka Build Level 2.57) (APAR IY77101). This seems to have been released in December 2005, but IBM support have indicated its use in a support ticket conversation in January 2005 already. It did not work, and in connection with another support ticket in September 2005, IBM made available a patched version of the 3.6 2.56 *fileserver* only where it finally did work. So I don't think I've ever had any database servers that are even supposed to obey "M" in NetRestrict, but at the same time, I haven't had a problem with this so I haven't noticed. What the... -- Atro Tossavainen (Mr.) / The Institute of Biotechnology at Systems Analyst, Techno-Amish & / the University of Helsinki, Finland, +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own. < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS From jaltman@secure-endpoints.com Tue Apr 13 13:31:18 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Tue, 13 Apr 2010 08:31:18 -0400 Subject: [OpenAFS] Re: Ubik problem In-Reply-To: <201004130543.o3D5hlwL015540@ruuvi.it.helsinki.fi> References: <201004130543.o3D5hlwL015540@ruuvi.it.helsinki.fi> Message-ID: <4BC46416.7090203@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms020406050807080209090301 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/13/2010 1:43 AM, Atro Tossavainen wrote: > Jeffrey, >=20 >> The OpenAFS NetRestrict documentation does not mention the use of a >> preceding 'M'. >=20 > Neither does the IBM documentation, which is what I said, I think. The OpenAFS Reference Manual has been thoroughly updated to document how OpenAFS behaves. It is derived from the content of the IBM AFS man pages but is not the same as them. There is no reference to 'M' prefixing because OpenAFS does not support it. >> I suspect the change IBM implemented was never passed on to OpenAFS >> and as far as I can tell from the source its presence will invalidate >> the address and prevent it from being used as a filter. >=20 > On the IBM AFS sun4x_58 server where it was explicitly recommended > by IBM AFS support in early 2005? :-) I'm not running the OpenAFS > db servers. In fact, I seem to be running a mishmash of IBM AFS > servers - the various components aren't even all the same version. >=20 > From my reading of IBM AFS patch READMEs, it appears that "M" appeared > in AFS 3.6 Patch 13 (aka Build Level 2.57) (APAR IY77101). This seems > to have been released in December 2005, but IBM support have indicated > its use in a support ticket conversation in January 2005 already. It > did not work, and in connection with another support ticket in Septembe= r > 2005, IBM made available a patched version of the 3.6 2.56 *fileserver*= > only where it finally did work. So I don't think I've ever had any > database servers that are even supposed to obey "M" in NetRestrict, > but at the same time, I haven't had a problem with this so I haven't > noticed. What the... I can't speak to the IBM patches. I can speak to the OpenAFS sources. You can read them to see how the NetRestrict file is parsed. http://git.openafs.org/?p=3Dopenafs.git;a=3Dblob;f=3Dsrc/util/netutils.c;= h=3D03a90e3b6d89e6f1c781b7324f0f661280ceeaa6;hb=3DHEAD See parseNetRestrictFile(). There is no reference to 'M' anywhere. In OpenAFS, "255" should be a mask by itself. The question OpenAFS is now left with is whether to add support for the IBM behavior change. Jeffrey Altman --------------ms020406050807080209090301 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MTMxMjMxMThaMCMGCSqGSIb3DQEJBDEWBBQy5F+T YdEy0iJvkGvUM9aVHN86wzBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAET38kQyAJ+28qd/EdU1fPHRmwwF1Nsf2gEi t58ysXb3ILgcew/fFEgnSEtukNVEL7/GnWZm9GLJ0r09O45XZWkQM+vXx8bs0R7cTjVSY2d+ I+PHxMOB3A/yDG+691g3cjUjj+4tAOEyF25Btp2e6xzpR6Yf6E9a/pEfbgoYGCeitxlPNvS/ Ce5AkRCeUQ8hcGucantPxulT+fbbV4xmYmJ27zy9WiaFszC7cN3ocyNAOyUxyj+Oh3fHMbdJ iPeJeObSarmv0Pf90Izlzqra4NdWhzYlPkbRly3hd8lsw6wpkdZVWaIi/5lFIltp9h+/mKA2 EXU2ENTs4QWx39ygo7YAAAAAAAA= --------------ms020406050807080209090301-- From jaltman@secure-endpoints.com Tue Apr 13 14:26:24 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Tue, 13 Apr 2010 09:26:24 -0400 Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs Message-ID: <4BC47100.1030802@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms040009090001020707000000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable In 2002, the OpenAFS version of the "vos listaddrs" command was updated to include the Arla -printuuid and -noresolve options which permits the UUID and IP address of registered file servers to be displayed. For example: UUID: 006cab10-0e3e-1b20-a3-aa-2601a8c0aa77 24.193.47.88 192.168.122.1 192.168.1.38 In 2008, the -noresolve option was made generic so that it could apply to all vos commands so that instead of seeing DNS names the actual IP addresses of server could be viewed. This change was made because DNS name resolution often makes it appear that a file server is properly registered when instead it is in fact not. However, IP addresses are not the canonical method of identifying a file server. For that the UUID is required and at the present time there is no mechanism when using vos listvldb or vos examine to identify the UUID of the server on which a volume is located. This lack has come up several times in the #openafs IRC channel when attempting to help users setup new cells or add new file servers. The most recent time on March 30th. Gerrit http://gerrit.openafs.org/#change,1742 is an attempt to add -printuuid as a standard option to all vos commands. The only issue at the moment is what the format of the output should look like. UUIDs and DNS names are long. Extending the existing format to include the UUID inline with each server produces output that will not fit in an 80 column terminal.=20 An example of "vos examine -printuuid" output: root.cell 537870331 RW 42 K On-line ASCLEPIUS.MIT.EDU [0037555a-be36-19a6-a2-4d-5e3c0912aa77] /vicepr RWrite 537870331 ROnly 537870333 Backup 537870332 MaxQuota 500 K Creation Fri Jun 06 12:24:21 2008 Copy Thu Feb 26 11:43:23 2009 Backup Tue Apr 13 02:00:17 2010 Last Update Thu Oct 18 12:44:23 2007 7647 accesses in the past day (i.e., vnode references) RWrite: 537870331 ROnly: 537870333 Backup: 537870332 number of sites -> 4 server ASCLEPIUS.MIT.EDU [0037555a-be36-19a6-a2-4d-5e3c0912aa77] partition /vicepr RW Site server ASCLEPIUS.MIT.EDU [0037555a-be36-19a6-a2-4d-5e3c0912aa77] partition /vicepr RO Site server MNEMOSYNE.MIT.EDU [005d91e8-f824-19a6-aa-5c-613c0912aa77] partition /vicepr RO Site server IXION.MIT.EDU [00086236-fa87-19a6-b4-de-ab015b12aa77] partition /vicepr RO Site An example of "vos listvldb -printuuid" output: root.cell RWrite: 536870915 ROnly: 536870916 number of sites -> 4 server bethlehem.your-file-system.com [0008fa02-d48c-19b9-81-fc-419a1dccaa77] partition /vicepa RW Site server bethlehem.your-file-system.com [0008fa02-d48c-19b9-81-fc-419a1dccaa77] partition /vicepa RO Site server faultline.your-file-system.com [0007580a-7001-1aae-85-8e-2f9a1dccaa77] partition /vicepa RO Site server cpe-24-193-47-88.nyc.res.rr.com [006cab10-0e3e-1b20-a3-aa-2601a8c0aa77] partition /vicepa RO Site One alternative output format that could be used when the -printuuid option is specified is found below. vos examine -printuuid: root.cell 537870331 RW 42 K On-line UUID: 0037555a-be36-19a6-a2-4d-5e3c0912aa77 Server ASCLEPIUS.MIT.EDU Partition /vicepr RWrite 537870331 ROnly 537870333 Backup 537870332 MaxQuota 500 K Creation Fri Jun 06 12:24:21 2008 Copy Thu Feb 26 11:43:23 2009 Backup Tue Apr 13 02:00:17 2010 Last Update Thu Oct 18 12:44:23 2007 7647 accesses in the past day (i.e., vnode references) RWrite: 537870331 ROnly: 537870333 Backup: 537870332 number of sites -> 4 RW Site server ASCLEPIUS.MIT.EDU uuid 0037555a-be36-19a6-a2-4d-5e3c0912aa77 partition /vicepr RO Site server ASCLEPIUS.MIT.EDU uuid 0037555a-be36-19a6-a2-4d-5e3c0912aa77 partition /vicepr RO Site server MNEMOSYNE.MIT.EDU uuid 005d91e8-f824-19a6-aa-5c-613c0912aa77 partition /vicepr RO Site server IXION.MIT.EDU uuid 00086236-fa87-19a6-b4-de-ab015b12aa77 partition /vicepr vos listvldb -printuuid: root.cell RWrite: 536870915 ROnly: 536870916 number of sites -> 4 RW Site server bethlehem.your-file-system.com uuid 0008fa02-d48c-19b9-81-fc-419a1dccaa77 partition /vicepa RO Site server bethlehem.your-file-system.com uuid 0008fa02-d48c-19b9-81-fc-419a1dccaa77 partition /vicepa RO Site server faultline.your-file-system.com uuid 0007580a-7001-1aae-85-8e-2f9a1dccaa77 partition /vicepa RO Site server cpe-24-193-47-88.nyc.res.rr.com uuid 006cab10-0e3e-1b20-a3-aa-2601a8c0aa77 partition /vicepa Please offer your opinions. As people have a variety of scripts that parse the output of vos commands to automate behaviors, we would not be changing the default output. Any format change would only be used when the -printuuid option is specified. Jeffrey Altman --------------ms040009090001020707000000 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MTMxMzI2MjRaMCMGCSqGSIb3DQEJBDEWBBQ1QuqU E3cG5Cfu+InB7LyzOvfvpjBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBACh9A2TcnILwGwFdJ4k5oGFHdE89Ejohbl8N OD3+uE/02/wpqwXedzb9Sz9Q+Yrv4+Ki1XMXiWBxk2oba1iGqAbupmJ/b9uZ2r/gAN4EiAq5 6J9RNpu0gAUf/ZCdD8cqpfxIMSeHyZXHG0dzTJdZlEQs3YzqMxUQyoB6619Ev8IHMZn5bUjc 2ApcbB/CkawIsbeU/prBsj58SfiTAhkAl6Bttwjs5jBQMbzL8sxf/+b7cKAQesK6Q8/K5tPM rXT+1m4vqc/4HRAVCoRzlLCKAvrCoCeskyJk3YKqEQrMeo2lmkIWS/A1Xp++u/ZIGfzv7ZyN iFtD3hH4pHfgn4kvQqMAAAAAAAA= --------------ms040009090001020707000000-- From utoddl@email.unc.edu Tue Apr 13 15:02:35 2010 From: utoddl@email.unc.edu (Todd Lewis) Date: Tue, 13 Apr 2010 10:02:35 -0400 Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: <4BC47100.1030802@secure-endpoints.com> References: <4BC47100.1030802@secure-endpoints.com> Message-ID: <4BC4797B.3070202@email.unc.edu> On 04/13/2010 09:26 AM, Jeffrey Altman sent: > An example of "vos examine -printuuid" output: > [...] > An example of "vos listvldb -printuuid" output: > [...] > One alternative output format that could be used when the -printuuid > option is specified is found below. > > vos examine -printuuid: > [...] > vos listvldb -printuuid: > > Please offer your opinions. Clearly the multi-line form is easier for humans to read, and the related-data-on-one-line form is far simpler for scripts to parse. By far. In both cases. Is there a place on the ballot to vote for... both, with a switch? Otherwise, I don't care. I'm screwed sooner or later either way. -- +--------------------------------------------------------------+ / Todd_Lewis@unc.edu 919-445-9302 http://www.unc.edu/~utoddl / / In democracy it's your vote that counts; / / In feudalism it's your count that votes. / +--------------------------------------------------------------+ From fbo2@gmx.net Tue Apr 13 15:40:25 2010 From: fbo2@gmx.net (Frank Burkhardt) Date: Tue, 13 Apr 2010 16:40:25 +0200 Subject: [OpenAFS] Cache size limit? In-Reply-To: <1e8734811003220738q2c97b6d2o18a4efa6d6214f65@mail.gmail.com> References: <1e8734811003220738q2c97b6d2o18a4efa6d6214f65@mail.gmail.com> Message-ID: <20100413144025.GA16782@postman.alpha> Hi, On Mon, Mar 22, 2010 at 02:38:50PM +0000, Stephen Quinney wrote: > I was wondering if there are set limits on the AFS cache size for a > client? Or are there any limiting factors which mean it is not worth > going beyond a certain point? In this case, this is on a 32bit Linux > machine but I am also interested in getting an answer for the same > question for x64_64 Linux. The machine is being used by multiple users > simultaneously to do big (i.e. large memory & cpu usage, lots of > filesystem access, long running) computation jobs so I am trying to > work out the best way to optimise the AFS access. I've got about 100 linux hosts (x86_64,Debian Lenny,OA 1.4.10) here using a 30GB disk cache. However, I would be interested in some information about cache limits, too. One of my user is very dissapointed about our AFS' performance. So I put an additional 200GB HDD into his computer, set the cache to 175GB ... and it just didn't work. I do not know exactly what the symptoms were but if anyone is interested, I can do it again and post what happens. OK - back to the most interesting question: What are the theoretical and practical limits of the cache size on linux? How do the practical limits vary between machines accessing lots of small files and hosts accessing some large files? Thank you in advance for any information. Regards, Frank From jblaine@kickflop.net Tue Apr 13 16:22:39 2010 From: jblaine@kickflop.net (Jeff Blaine) Date: Tue, 13 Apr 2010 11:22:39 -0400 Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: <4BC47100.1030802@secure-endpoints.com> References: <4BC47100.1030802@secure-endpoints.com> Message-ID: <4BC48C3F.6030802@kickflop.net> IMO, unless a "for parsing" output format is available (never likely), the existing line-per-site format should be kept and not altered just for a new command-line option's output. This isn't a book we're reading for a half hour. It's vos output. Let the lines pass 80 cols. You can have the best of both worlds by noting the position of 's' in server, then padding the end of "server foo" with spaces to wrap the uuid around properly instead of a newline... if one is concerned with the 80col thing that much :) On 4/13/2010 9:26 AM, Jeffrey Altman wrote: > In 2002, the OpenAFS version of the "vos listaddrs" command was updated > to include the Arla -printuuid and -noresolve options which permits the > UUID and IP address of registered file servers to be displayed. For > example: > > UUID: 006cab10-0e3e-1b20-a3-aa-2601a8c0aa77 > 24.193.47.88 > 192.168.122.1 > 192.168.1.38 > > In 2008, the -noresolve option was made generic so that it could apply > to all vos commands so that instead of seeing DNS names the actual IP > addresses of server could be viewed. This change was made because DNS > name resolution often makes it appear that a file server is properly > registered when instead it is in fact not. > > However, IP addresses are not the canonical method of identifying a file > server. For that the UUID is required and at the present time there is > no mechanism when using vos listvldb or vos examine to identify the UUID > of the server on which a volume is located. This lack has come up > several times in the #openafs IRC channel when attempting to help users > setup new cells or add new file servers. The most recent time on March > 30th. > > Gerrit http://gerrit.openafs.org/#change,1742 is an attempt to add > -printuuid as a standard option to all vos commands. The only issue at > the moment is what the format of the output should look like. UUIDs and > DNS names are long. Extending the existing format to include the UUID > inline with each server produces output that will not fit in an 80 > column terminal. > > An example of "vos examine -printuuid" output: > > root.cell 537870331 RW 42 K On-line > ASCLEPIUS.MIT.EDU [0037555a-be36-19a6-a2-4d-5e3c0912aa77] /vicepr > RWrite 537870331 ROnly 537870333 Backup 537870332 > MaxQuota 500 K > Creation Fri Jun 06 12:24:21 2008 > Copy Thu Feb 26 11:43:23 2009 > Backup Tue Apr 13 02:00:17 2010 > Last Update Thu Oct 18 12:44:23 2007 > 7647 accesses in the past day (i.e., vnode references) > > RWrite: 537870331 ROnly: 537870333 Backup: 537870332 > number of sites -> 4 > server ASCLEPIUS.MIT.EDU [0037555a-be36-19a6-a2-4d-5e3c0912aa77] > partition /vicepr RW Site > server ASCLEPIUS.MIT.EDU [0037555a-be36-19a6-a2-4d-5e3c0912aa77] > partition /vicepr RO Site > server MNEMOSYNE.MIT.EDU [005d91e8-f824-19a6-aa-5c-613c0912aa77] > partition /vicepr RO Site > server IXION.MIT.EDU [00086236-fa87-19a6-b4-de-ab015b12aa77] > partition /vicepr RO Site > > An example of "vos listvldb -printuuid" output: > > root.cell > RWrite: 536870915 ROnly: 536870916 > number of sites -> 4 > server bethlehem.your-file-system.com > [0008fa02-d48c-19b9-81-fc-419a1dccaa77] partition /vicepa RW Site > server bethlehem.your-file-system.com > [0008fa02-d48c-19b9-81-fc-419a1dccaa77] partition /vicepa RO Site > server faultline.your-file-system.com > [0007580a-7001-1aae-85-8e-2f9a1dccaa77] partition /vicepa RO Site > server cpe-24-193-47-88.nyc.res.rr.com > [006cab10-0e3e-1b20-a3-aa-2601a8c0aa77] partition /vicepa RO Site > > One alternative output format that could be used when the -printuuid > option is specified is found below. > > vos examine -printuuid: > > root.cell 537870331 RW 42 K On-line > UUID: 0037555a-be36-19a6-a2-4d-5e3c0912aa77 > Server ASCLEPIUS.MIT.EDU > Partition /vicepr > RWrite 537870331 ROnly 537870333 Backup 537870332 > MaxQuota 500 K > Creation Fri Jun 06 12:24:21 2008 > Copy Thu Feb 26 11:43:23 2009 > Backup Tue Apr 13 02:00:17 2010 > Last Update Thu Oct 18 12:44:23 2007 > 7647 accesses in the past day (i.e., vnode references) > > RWrite: 537870331 ROnly: 537870333 Backup: 537870332 > number of sites -> 4 > RW Site > server ASCLEPIUS.MIT.EDU > uuid 0037555a-be36-19a6-a2-4d-5e3c0912aa77 > partition /vicepr > RO Site > server ASCLEPIUS.MIT.EDU > uuid 0037555a-be36-19a6-a2-4d-5e3c0912aa77 > partition /vicepr > RO Site > server MNEMOSYNE.MIT.EDU > uuid 005d91e8-f824-19a6-aa-5c-613c0912aa77 > partition /vicepr > RO Site > server IXION.MIT.EDU > uuid 00086236-fa87-19a6-b4-de-ab015b12aa77 > partition /vicepr > > vos listvldb -printuuid: > > root.cell > RWrite: 536870915 ROnly: 536870916 > number of sites -> 4 > RW Site > server bethlehem.your-file-system.com > uuid 0008fa02-d48c-19b9-81-fc-419a1dccaa77 > partition /vicepa > RO Site > server bethlehem.your-file-system.com > uuid 0008fa02-d48c-19b9-81-fc-419a1dccaa77 > partition /vicepa > RO Site > server faultline.your-file-system.com > uuid 0007580a-7001-1aae-85-8e-2f9a1dccaa77 > partition /vicepa > RO Site > server cpe-24-193-47-88.nyc.res.rr.com > uuid 006cab10-0e3e-1b20-a3-aa-2601a8c0aa77 > partition /vicepa > > Please offer your opinions. As people have a variety of scripts that > parse the output of vos commands to automate behaviors, we would not be > changing the default output. Any format change would only be used when > the -printuuid option is specified. > > Jeffrey Altman > > > > From sxw@inf.ed.ac.uk Tue Apr 13 16:25:17 2010 From: sxw@inf.ed.ac.uk (Simon Wilkinson) Date: Tue, 13 Apr 2010 16:25:17 +0100 Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: <4BC4797B.3070202@email.unc.edu> References: <4BC47100.1030802@secure-endpoints.com> <4BC4797B.3070202@email.unc.edu> Message-ID: On 13 Apr 2010, at 15:02, Todd Lewis wrote: >=20 > Clearly the multi-line form is easier for humans to read, and the > related-data-on-one-line form is far simpler for scripts to parse. By = far. > In both cases. I don't think we should be catering for people parsing command output = (beyond recognising that folk currently do it, and trying not to break = them). Instead, we should focus on making interfaces that provide = properly stuctured output available - things like the AFS-Perl module = are a great example here. In terms of what our commands display, we should prioritise human users. S. From adeason@sinenomine.net Tue Apr 13 16:34:03 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Tue, 13 Apr 2010 10:34:03 -0500 Subject: [OpenAFS] Re: Modifying the output of vos commands to include server UUIDs References: <4BC47100.1030802@secure-endpoints.com> <4BC48C3F.6030802@kickflop.net> Message-ID: <20100413103403.57b92945.adeason@sinenomine.net> On Tue, 13 Apr 2010 11:22:39 -0400 Jeff Blaine wrote: > IMO, unless a "for parsing" output format is available (never > likely), 'vos ex -format', though I don't think it currently affects that part of the output. And it puts things on different lines, which is Todd Lewis' "harder-to-parse" case anyway. -- Andrew Deason adeason@sinenomine.net From adeason@sinenomine.net Tue Apr 13 19:11:29 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Tue, 13 Apr 2010 13:11:29 -0500 Subject: [OpenAFS] Re: Ubik problem References: <20100412165845.c5f44f42.adeason@sinenomine.net> <201004130543.o3D5hlwL015540@ruuvi.it.helsinki.fi> Message-ID: <20100413131129.b790823c.adeason@sinenomine.net> On Tue, 13 Apr 2010 08:43:47 +0300 (EEST) Atro Tossavainen wrote: > Andrew, > > > Atro's problem appears to be that they are advertising the extra > > addresses, though, not that they're sending packets out over them. > > What I don't get is why this would have changed transparently on the > sun4x_58 server when I changed the *other* db server from sun4x_58 to > sunx86_510 and from IBM AFS to OpenAFS. Isn't the sunx86_510 server the one that's reporting extra addresses? >From this: >>> sunx86_510 # /usr/afs/bin/udebug 128.214.88.114 7002 -long >>> Host's addresses are: 128.214.88.114 10.0.0.3 172.16.0.1 172.17.0.1 172.18.0.1 It just looks like OpenAFS will (currently) ignore NetRestrict lines with an 'M' in front as a parse error. So your upgraded sunx86_510 machine does not restrict those addresses, and advertises the private ones. Some of those are lower than the IPs of the sun4x_58 box, so the sunx86_510 box looks like the new "lowest IP" server. -- Andrew Deason adeason@sinenomine.net From wayne_greene@unc.edu Tue Apr 13 20:21:29 2010 From: wayne_greene@unc.edu (Wayne Greene) Date: Tue, 13 Apr 2010 15:21:29 -0400 Subject: [OpenAFS] Windows 7 Sleep behavior-Broken AFS Lock on wakeup Message-ID: <4BC4C439.3060800@unc.edu> Hello, We are using Windows 7 Enterprise, MIT Kerberos for Windows 3.22, and Open AFS 1-5.6.800 and have encountered a problem for our laptop users and the sleep function. When the computers wake, the AFS lock symbol in the system tray shows that it is broken and cannot connect to the AFS service. Net ID manager shows they have AFS tokens and kerberos tickets but AFS shares cannot be accessed until the computer is restarted. I have tried destroying the Network ID credentials, stopping the AFS service then sleeping the computer, regaining credentials and restarting the service and after waking up it still doesn't work. I found a power management option in the Lenovo Power Manager that will keep the network connection for a specific amount of time during sleep, but that has not worked either. These so far are Lenovo computers, my test machine is a ThinkPad R400 but the symptom is the same on a few different models. Is anyone else experiencing this and/or has anyone found a fix if so? Thanks. Wayne Greene Computer Science UNC Chapel Hill From jaltman@secure-endpoints.com Tue Apr 13 20:31:10 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Tue, 13 Apr 2010 15:31:10 -0400 Subject: [OpenAFS] Windows 7 Sleep behavior-Broken AFS Lock on wakeup In-Reply-To: <4BC4C439.3060800@unc.edu> References: <4BC4C439.3060800@unc.edu> Message-ID: <4BC4C67E.5020105@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms040105000900060205030804 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/13/2010 3:21 PM, Wayne Greene wrote: > Hello, >=20 > We are using Windows 7 Enterprise, MIT Kerberos for Windows 3.22, and > Open AFS 1-5.6.800 and have encountered a problem for our laptop users > and the sleep function. When the computers wake, the AFS lock symbol in= > the system tray shows that it is broken and cannot connect to the AFS > service. Net ID manager shows they have AFS tokens and kerberos tickets= > but AFS shares cannot be accessed until the computer is restarted. I > have tried destroying the Network ID credentials, stopping the AFS > service then sleeping the computer, regaining credentials and restartin= g > the service and after waking up it still doesn't work. I found a power > management option in the Lenovo Power Manager that will keep the networ= k > connection for a specific amount of time during sleep, but that has not= > worked either. These so far are Lenovo computers, my test machine is a > ThinkPad R400 but the symptom is the same on a few different models. Is= > anyone else experiencing this and/or has anyone found a fix if so? Than= ks. >=20 > Wayne Greene > Computer Science > UNC Chapel Hill Please file a bug report with Microsoft for this issue. The problem is not with OpenAFS but with the Netbios Name Resolution. If you nbtstat -n you will see that the "AFS" <20> Netbios name has been successfully registered on the Microsoft Loopback adapter (10.254.254.253) and yet when you attempt to access \\AFS, (net view \\afs), Windows reports that the name cannot be resolved. This is a bug in Microsoft Windows 7 and Server 2008 R2. Until Microsoft receives enough reports from paying support customers, it will not be fixed. When you file your report, please indicate that Microsoft when investigating the problem can contact openafs-gatekeepers@openafs.org if they want to discuss the issue privately with the OpenAFS project. Thank you and I am sorry your users are experiencing this problem. Jeffrey Altman --------------ms040105000900060205030804 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MTMxOTMxMTBaMCMGCSqGSIb3DQEJBDEWBBSV9A9J UgwxcMl4x9m9ZkS6V5nQkzBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBABfl7NgEssyfSsuweIk6cJw5aVA/0Ymu9/et EyR5mzJxpMjcits0j9lYtSQGCMgjj3pxFu/yaYfw2eSuDBAMcp7GsVdbt66gEsvF2d+f4Y6C 3uj+S/wtjptlIJqI7bpgZ5mZPg3n+m8sJcCX82y9iGgmdGKcpeZUhbnlRYB6wOy3SdVBIVRW 9xq68FC7T9v5BHQAQXxOkXTMZyRYAKp5htRrotZevJgF3xZ7SrU5uMql86Lo9rphpgwkUVyA WZvt1+dUzqMP5jCoTlTT7MQG8dZchfngTPQILl96rj+3H66OhW5gahG3BHf9PayUAzLEeqeu TTmPU28pUGyyTCr56IcAAAAAAAA= --------------ms040105000900060205030804-- From brandon.m.simmons@gmail.com Tue Apr 13 20:36:45 2010 From: brandon.m.simmons@gmail.com (Brandon Simmons) Date: Tue, 13 Apr 2010 15:36:45 -0400 Subject: [OpenAFS] sqlite on AFS will not work, even with whole-file Message-ID: On Sun, Apr 11, 2010 at 11:13 PM, Adam Megacz wrote: > > Brandon Simmons writes: >> Thanks for the response. It seems like whole-file locking in sqlite >> would be a good choice for me in any case, > >> In a situation where the whole-file locking scheme is used, would AFS >> be an acceptable choice? Would it be better than NFS? > > I had the same idea, and tried it. =A0It does not work. =A0Your databases > will get corrupted. =A0I never figured out why, although I did confirm > that sqlite was in fact requesting only whole-file locks. > > It would be nice if it worked, though. =A0There are a lot of applications > out there where writes to the database are extremely rare, so > invalidating all the clients' caches is not a problem. A couple questions: I assume you were on a linux network? Also, how exactly did you ensure that you were using whole-file locking? I'm still not even clear, after reading the Sqlite docs and the responses here, how to do that. Thanks, Brandon http://coder.bsimmons.name/blog/ From ela@cs.wisc.edu Tue Apr 13 21:59:17 2010 From: ela@cs.wisc.edu (Jacob Ela) Date: Tue, 13 Apr 2010 15:59:17 -0500 Subject: [OpenAFS] OS X, AFS Home Directories and SSH/Unix Permissions Message-ID: <393853E2-C3D1-4F6B-854C-ED0E1D06094D@cs.wisc.edu> Greetings All, I've been looking for some information on this because someone else has = probably run into a similar issue, but I haven't found much that is = recent or pointed towards solving the problem - though I've found some = old email that suggests where this originates from... I've got a Mac Mini lab running OSX 10.6.2 and OpenAFS 1.4.11 (but also = have seen this on a MacBook running 10.6.3 and 1.5.73.3). User's home = directories live in AFS, and users get Kerberos/AFS credentials at = login. =20 I'm seeing on the Macs that all the unix file permissions on files in = AFS are shown as 666, and from the old emails I've found I'm just = guessing that this is to make AFS ACL's play nicely with the Finder (or = rather the other way around). =20 This has the unfortunate side effect that my users can't use SSH on the = Macs, as the reported permissions on their ~/.ssh/config file suggest it = is group and world writable. This causes SSH to error out when a user = attempts to connect to another computer because of insecure config file = permissions. Trying to chmod the file from a Mac doesn't change the = unix permissions as they are reported to the Mac, though Linux hosts can = see these new permissions. =20 Has anyone run into something like this? Is there a way to change the = permissions AFS reports to OSX, or is there a work around I'm failing to = see? Thanks for any help, -- Jacob Ela Computer Systems Lab University of Wisconsin-Madison ela@cs.wisc.edu= From scs@umich.edu Tue Apr 13 22:08:49 2010 From: scs@umich.edu (Steve Simmons) Date: Tue, 13 Apr 2010 17:08:49 -0400 Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: <4BC4797B.3070202@email.unc.edu> References: <4BC47100.1030802@secure-endpoints.com> <4BC4797B.3070202@email.unc.edu> Message-ID: <6A5BB6C1-955E-4740-8CDE-FB9CD7663BD0@umich.edu> On Apr 13, 2010, at 10:02 AM, Todd Lewis wrote: > Clearly the multi-line form is easier for humans to read, and the > related-data-on-one-line form is far simpler for scripts to parse. By = far. > In both cases. >=20 > Is there a place on the ballot to vote for... both, with a switch? I'm a long-time fan of having a switch that causes tools to dump their = data in an easy-to-machine-parse format. That isn't always doable, but = when it is, it's a big win.= From jaltman@secure-endpoints.com Tue Apr 13 22:28:31 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Tue, 13 Apr 2010 17:28:31 -0400 Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: <6A5BB6C1-955E-4740-8CDE-FB9CD7663BD0@umich.edu> References: <4BC47100.1030802@secure-endpoints.com> <4BC4797B.3070202@email.unc.edu> <6A5BB6C1-955E-4740-8CDE-FB9CD7663BD0@umich.edu> Message-ID: <4BC4E1FF.5050305@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms030804030605000409050504 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/13/2010 5:08 PM, Steve Simmons wrote: >=20 > On Apr 13, 2010, at 10:02 AM, Todd Lewis wrote: >=20 >> Clearly the multi-line form is easier for humans to read, and the >> related-data-on-one-line form is far simpler for scripts to parse. By = far. >> In both cases. >> >> Is there a place on the ballot to vote for... both, with a switch? >=20 > I'm a long-time fan of having a switch that causes tools to dump their = data in an easy-to-machine-parse format. That isn't always doable, but wh= en it is, it's a big win. As Andrew pointed out in another reply in this thread, the -format switch is support to provide that but it fails to provide a consistent (value - data) pair per line. Currently that output looks like: name root.cell id 536870915 serv 204.29.154.37 bethlehem.your-file-system.com part /vicepa status OK backupID 0 parentID 536870915 cloneID 536870916 inUse Y needsSalvaged N destroyMe N type RW creationDate 1242930289 Thu May 21 14:24:49 2009 accessDate 0 Wed Dec 31 19:00:00 1969 updateDate 1269892897 Mon Mar 29 16:01:37 2010 backupDate 0 Wed Dec 31 19:00:00 1969 copyDate 1242930289 Thu May 21 14:24:49 2009 flags 0 (Optional) diskused 43 maxquota 5000 minquota 0 (Optional) filecount 38 dayUse 0 weekUse 0 (Optional) spare2 0 (Optional) spare3 0 (Optional) root.cell RWrite: 536870915 ROnly: 536870916 number of sites -> 4 server bethlehem.your-file-system.com partition /vicepa RW Site server bethlehem.your-file-system.com partition /vicepa RO Site server faultline.your-file-system.com partition /vicepa RO Site server cpe-24-193-47-88.nyc.res.rr.com partition /vicepa RO Site RWrite: 536870915 ROnly: 536870916 number of sites -> 4 server bethlehem.your-file-system.com partition /vicepa RW Site server bethlehem.your-file-system.com partition /vicepa RO Site server faultline.your-file-system.com partition /vicepa RO Site server cpe-24-193-47-88.nyc.res.rr.com partition /vicepa RO Site which re-uses a similar logic for the per volume output as the non-format. I do notice a bug in the above output in that it lists the same block twice. Jeffrey Altman --------------ms030804030605000409050504 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MTMyMTI4MzFaMCMGCSqGSIb3DQEJBDEWBBSvAnZx 7W0aGL1jRmCkTKQ2zbh7BzBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAK34GnFi0nLjrfN2CoRY5RJKbUHWxyRg9I4d 8EtSATr2Ckn/nLEqMcZipnunT+MDbRR4oand2keD1ZBXdmeV6Bbgpnf1CpQVfWlV56+zE32h 23waa9sLLPDhSwCMDt0tM6hJsj81QAuR9HnYjOgt6dWeD4HP3R0w4m4/eZrRbovDiwGNeojt 6dJEAs+bptQ0qrIPh0kiHPHtdPCwFB04l2Qf53a6xvXpFDIRuCDfhnHb3NMQmoNMhr/R720G 4zc4W1EEL45Ouau+yUIvK+wfQMlWTaphdrl0MQvhpuUevRPARp8EITjBycPd9FMnYzYSddRb 2AvBvCWchFb25OIO5IAAAAAAAAA= --------------ms030804030605000409050504-- From shadow@gmail.com Wed Apr 14 00:02:54 2010 From: shadow@gmail.com (Derrick Brashear) Date: Tue, 13 Apr 2010 19:02:54 -0400 Subject: [OpenAFS] OS X, AFS Home Directories and SSH/Unix Permissions In-Reply-To: <393853E2-C3D1-4F6B-854C-ED0E1D06094D@cs.wisc.edu> References: <393853E2-C3D1-4F6B-854C-ED0E1D06094D@cs.wisc.edu> Message-ID: On Tue, Apr 13, 2010 at 4:59 PM, Jacob Ela wrote: > Greetings All, > > I've been looking for some information on this because someone else has p= robably run into a similar issue, but I haven't found much that is recent o= r pointed towards solving the problem - though I've found some old email th= at suggests where this originates from... > > I've got a Mac Mini lab running OSX 10.6.2 and OpenAFS 1.4.11 (but also h= ave seen this on a MacBook running 10.6.3 and 1.5.73.3). =A0User's home dir= ectories live in AFS, and users get Kerberos/AFS credentials at login. > > I'm seeing on the Macs that all the unix file permissions on files in AFS= are shown as 666, and from the old emails I've found I'm just guessing tha= t this is to make AFS ACL's play nicely with the Finder (or rather the othe= r way around). > > This has the unfortunate side effect that my users can't use SSH on the M= acs, as the reported permissions on their ~/.ssh/config file suggest it is = group and world writable. =A0This causes SSH to error out when a user attem= pts to connect to another computer because of insecure config file permissi= ons. =A0Trying to chmod the file from a Mac doesn't change the unix permiss= ions as they are reported to the Mac, though Linux hosts can see these new = permissions. > > Has anyone run into something like this? =A0Is there a way to change the = permissions AFS reports to OSX, or is there a work around I'm failing to se= e? Check out the RealModes setting. Edit /var/db/openafs/etc/config/settings.plist, and rerun /var/db/openafs/etc/config/afssettings as root. --=20 Derrick From ela@cs.wisc.edu Wed Apr 14 00:58:20 2010 From: ela@cs.wisc.edu (Jacob Ela) Date: Tue, 13 Apr 2010 18:58:20 -0500 Subject: [OpenAFS] OS X, AFS Home Directories and SSH/Unix Permissions In-Reply-To: References: <393853E2-C3D1-4F6B-854C-ED0E1D06094D@cs.wisc.edu> Message-ID: That's what I missed. Looks like it did the trick - I'll try it on the = lab tomorrow. Thanks! Jacob Ela Computer Systems Lab University of Wisconsin-Madison ela@cs.wisc.edu On Apr 13, 2010, at 6:02 PM, Derrick Brashear wrote: > On Tue, Apr 13, 2010 at 4:59 PM, Jacob Ela wrote: >> Greetings All, >>=20 >> I've been looking for some information on this because someone else = has probably run into a similar issue, but I haven't found much that is = recent or pointed towards solving the problem - though I've found some = old email that suggests where this originates from... >>=20 >> I've got a Mac Mini lab running OSX 10.6.2 and OpenAFS 1.4.11 (but = also have seen this on a MacBook running 10.6.3 and 1.5.73.3). User's = home directories live in AFS, and users get Kerberos/AFS credentials at = login. >>=20 >> I'm seeing on the Macs that all the unix file permissions on files in = AFS are shown as 666, and from the old emails I've found I'm just = guessing that this is to make AFS ACL's play nicely with the Finder (or = rather the other way around). >>=20 >> This has the unfortunate side effect that my users can't use SSH on = the Macs, as the reported permissions on their ~/.ssh/config file = suggest it is group and world writable. This causes SSH to error out = when a user attempts to connect to another computer because of insecure = config file permissions. Trying to chmod the file from a Mac doesn't = change the unix permissions as they are reported to the Mac, though = Linux hosts can see these new permissions. >>=20 >> Has anyone run into something like this? Is there a way to change = the permissions AFS reports to OSX, or is there a work around I'm = failing to see? >=20 > Check out the RealModes setting. Edit > /var/db/openafs/etc/config/settings.plist, and rerun > /var/db/openafs/etc/config/afssettings as root. >=20 >=20 > --=20 > Derrick From jason@rampaginggeek.com Wed Apr 14 01:01:49 2010 From: jason@rampaginggeek.com (Jason Edgecombe) Date: Tue, 13 Apr 2010 20:01:49 -0400 Subject: [OpenAFS] OpenAFS Newsletter, Volume 2, Issue 4, April 2010 Message-ID: <4BC505ED.9040902@rampaginggeek.com> Here is the April 2010 issue of the OpenAFS Newsletter: OpenAFS Newsletter, Volume 2, Issue 4, April 2010 Welcome to the twelveth issue of the OpenAFS newsletter. This newsletter summarizes what is happening in the OpenAFS community. As always, volunteers, patches, bug reports, or any other type of help is greatly appreciated. Feedback on this newsletter is welcome. The goal is to summarize the various development efforts and news of OpenAFS for the community. Please let Jason Edgecombe know what you would like to see out of this newsletter. Any news about AFS-related projects is welcome and may be submitted to Jason for inclusion in the next newsletter. The current and past issues of this newsletter are available at General OpenAFS Progress OpenAFS version 1.5.73 was released on March 24. It was followed by three point releases to fix some issues. The latest version is 1.5.73.3. The gatekeepers are asking for people to really start testing the 1.5.x releases on Unix machines to help iron out bugs before 1.6. To help people with the testing efforts, Russ Allbery has uploaded new Debian packages: I've uploaded Debian packages of 1.5.73.3 plus some additional recent patches to Debian experimental. I should be able to keep the packages up to date with subsequent 1.5.x releases going forward. Due to the new libkopenafs1 package, the upload will have to go through NEW, so it will be a little bit before they show up in Debian. --Russ Allbery The instructions for contributing to OpenAFS have been revised for using Git. These instructions are in the README.git file in each release. The growl agent for Mac OS X is included in 1.5.73, but it's not well integrated yet. Initial feedback is positive and testers are welcome. Please send any feedback ot the port-darmin@openafs.org mailing list. A new version of the AFS PERL API was released. For more information and downloads, go to Events Annual Best Practices Workshop Plans are already underway for the seventh Workshop, to be held May 24-28, 2010, at the University of Illinois at Urbana-Champaign. We hope to see you there. Web site: Register by April 14, 2010 to get the best prices. AFS and Kerberos tutorials are $100 each, the Workshop itself is $150, or register for all three for only $300. After April 14, prices will go up, so register now and save. A tentative schedule is available. Further details, including social events, is still forthcoming. Hotel and travel information is also available. We'll be looking forward to meeting you at Illinois next month! European AFS Conference The date for the 3rd European AFS & Kerberos Conference has been set. The conference will take place in Pilsen, Czech Republic, from September 13 to September 15, 2010. More details are forthcoming and will be posted at . The conference is being hosted by Centre for Information Technology, University of West Bohemia. AFS Protocol Standardization Informal drafts that haven't been uploaded to the IETF web site: Rx Spec: This draft is in the very early stages. Mike Meffie and Tom Keiser are the current owners of this proposal. Nickolai Zeldovich wrote the original draft. Mike and Tom have started updating the draft with Nickolai's permission. A formal specification of Rx is needed for a basis for other IETF proposals. Discussion on these proposals is welcome and should be done on the AFS3-standardization list at PTS Alternate Authentication Status: Active - Third call for review Last Update: November 18, 2009 Expires: May 22, 2010 AFS Callback Extensions Status: Active - Waiting on RPC refresh This proposal will be rewritten with references to the RPC time refresh. Last update: September 23, 2009 Expires: March 23, 2010 DNS SRV Resource Records for AFS Status: Submitted to IETF Still in the RFC Editor queue, waiting for them to have a chance to work on it. --Russ RXGK Status: Active Rxgk is a security layer for AFS which will support strong encryption and authentication through Kerberos v5, GSI and any other GSSAPI security mechanism. Changes which are considered suitable for the 1.5.x series are in git - look for changes with author sxw@your-file-system.com. A development tree, which will be frequently rebased, is at http://github.com/your-file-system/openafs-rxgk Last Update: Jan 9, 2010 AFS3 ACL Rights Status: Second draft Last update: Jan 13, 2010 See the Per-File ACLs section for more info. Rx Security Object Providing Cleartext Peer Identity Assertions Status: Second draft Last Update: February 1, 2010 The Rx clear security class will improve on the rxnull security object by eliminating certain race conditions related to IPv4 address changes. A -02 revision of this internet draft will be forthcoming in the next few days, which will update the introduction and security considerations sections of the memo. Everyone is invited to review this document, and comments should be sent to the afs3-standardization@grand.central.org mailing list. AFSVol Tag-Length-Value Remote Procedure Call Extensions Status: Second Draft Last Update: April 6, 2010 As new forms of metadata are added to AFS volumes, we are running into limitations with the wire volume metadata structures used by the volume server. This internet draft aims to standardize a tag-length-value (TLV) encoding for arbitrary AFS volume metadata. A new version of this draft was released on April 6th, 2010. Everyone is invited to review and comment on this document. Comments should be sent to the afs3-standardization@grand.central.org mailing list. --Tom Projects Demand-Attach FileServer (DAFS) Project Contacts: * Andrew Deason * Tom Keiser * Mike Meffie Gerrit 1406 (per-volume locks) has been merged along with the related changes, and thus we can now salvage at the same time as volume operations as well as other salvages. Gerrit 1092 is unfortunately still not merged; we encourage additional review from anyone who can. Current DAFS development involves adding background I/O threads to the salvager code, and later making demand-salvages spawn as threads instead of processes. Code for that should be available shortly. --Andrew Better Documentation Project Contacts: * Russ Allbery * Jason Edgecombe Davor Ocelic is working on writing man pages for the new demand-attach binaries that aren't yet documented. The man page for state_analyzer has been committed. Pthreaded Ubik Project Contact: * Steven Jenkins * Andrew Deason * Alistair Ferguson Gerrit 1546 (add locks for addresses and cheader) has been submitted for review, and with that, we now believe the vlserver to be thread-safe. Since the vlserver thread-safety issues were the only known pthreaded ubik issues, after 1546 we are aware of no further issues with pthreaded ubik. --Steven We're still discussing what solution to use in gerrit 1546 (add locks for the vldb ubik cache). Additional problems affecting pthreaded ubik were found and fixed in gerrit 1680 (kill afs_inet_ntoa) and 1681 (correct use of flags_cond and version_cond). --Andrew This project will likely be dropped as a separate project in a couple of issues of the newsletter when this project is fully merged into the mainline OpenAFS code. Kerberos v5 and multiple encryption types Project Contacts: * Matt Benjamin * Marcus Watts I was hoping to have some time this week - got distracted by other matters. I do have one change of interest: the "tokens expired" message which formerly looked like this: Feb 22 10:23:08 lancashire kernel: afs: Tokens for user of AFS id 555 for cell cats.umich.edu expired now (where 555 was a fixed constant because the cache manager doesn't know what viceid the user has), now looks like this: Apr 3 04:55:37 lancashire kernel: afs: Tokens for mdw@CATS.UMICH.EDU for cell cats.umich.edu expired now I think that's an improvement. Heimdal has some annoying weirdness with key types and checksums. In 1.3.1 (at least,) the verify checksum logic insists only one checksum algorithm is acceptable per key type. The standards documents do not forbid this interpetation, but don't exactly require it. Sorting out acceptable checksum algorithms between various kerberos distributions continues to be a problem. I'm hoping to do a code drop soon. It will probably be a complete copy of source not just diffs. I was overly aggressive about fixing tabs and now have to "undo" some fixes to patches. Blech. --Marcus Per-File ACLs Project Contacts: * Marc Dionne Current status: * I plan to give a talk on the topic at the upcoming workshop --Marc Mac OS X OpenAFS Preference Pane Project Contact: * Claudio Bisegni The preference pane has been updated to allow the renewal of Kerberos tickets. The GUI and afs backgrounder were updated to accomodate this change. --Claudio *BSD Support Project Contacts: * Matt Benjamin Commit 028240329c09b6a311cb85736f41d75f7ee7a01f deals with some updated VFS calls in FreeBSD. Userspace cache manager Project Contact: * Andrew Deason I've finally managed to find time to work on this again, resulting in gerrit changes 1714-1726 which give a FUSE OpenAFS/libuafs client. Functionality improvements over previous libuafs code include fixed support for AFSDB and fakestat. Support will be forthcoming for some pioctl operations (lsmount, rmmount, getacl, setacl, checkservers) and perl SWIG bindings. I will be presenting at AFSBPW 2010 about libuafs, on its potential uses and how to use it. --Andrew S3 Front-end for AFS Project Contacts: * Fabrizio Manfredi * Claudio Bisegni We have a generic implementation in alpha test, without authentication and specific AFS ACL support. We hope to release a first public beta at the end of the April ( without authentication). --Fabrizio Virtual Machine Images Project Contact: * Fabrizio Manfredi The Virtual Machine Images are updated, now the operating system is Centos 5.4 with openafs 1.4.12, in the new distribution is also present the AFS perl API with example scripts. If you want, you can downgrade to openafs 1.4.11 with a simple snapshot rollback. The images are in vmware format only, you can download from: http://sourceforge.net/projects/s3afs/files/openafs-1.4.12-vm --Fabrizio Google Summer of Code 2010 Google will be doing their Summer of Code again in 2010. We're proud to announce that for the third year, OpenAFS will be participating as a mentoring organization. --Simon Accepted student proposals will be announced on April 26. Projects with no progress or no update Each project without progress this month is listed along with the month of the last update. * Rx OSD integration & Raw Vicep Access in Clients - August 2009 * Active Directory Backend for Ptserver - November 2009 * SetAG - December 2009 * Extended Callback Information - January 2010 * Disconnected AFS support - February 2010 Gerrit Activity To review a change, go to http://gerrit.openafs.org/#change,NUM where NUM is the Change# shown in the lists below. Statistics Number of patches waiting for review: 35 (last month: 50) Patches merged into the master branch: Month Number of Commits 2010-04 53 (Partial month) 2010-03 140 2010-02 156 2010-01 103 2009-12 72 2009-11 85 2009-10 154 2009-09 142 2009-08 78 2009-07 181 Patches merged into the stable branch: Month Number of Commits 2010-04 2 (Partial month) 2010-03 28 2010-02 35 2010-01 11 2009-12 92 2009-11 21 2009-10 7 2009-09 8 2009-08 17 2009-07 5 Patches waiting for review Date Author Change# Description 2010-04-11 Jonathan A. Kollasch (1738) NetBSD 5.0 support. 2010-04-11 Tharidu Fernando (1736) Windows: Secure C String usage in src\WINNT\afsd\fs.c 2010-04-10 Andrew Deason (1614) Add the Jabber MUC to the support page 2010-04-10 Andrew Deason (1723) Split afsd into afsd.c and afsd_kernel.c 2010-04-09 Marc Dionne (1640) Fileserver capabilities support for the UNIX client 2010-04-09 Andrew Deason (1725) Add a FUSE implementation for afsd 2010-04-09 Andrew Deason (1724) Make libuafs usable with afsd.o 2010-04-09 Andrew Deason (1726) Allow afsd.fuse to build on darwin / amd64 linux 2010-04-05 Benjamin Kaduk (1691) Add entries for FBSD 8.1 and 9.0 2010-03-31 Andrew Deason (1546) Add locks around updating the VLDB ubik cache 2010-03-28 Derrick Brashear (1333) byte-range lock warning should include pid 2010-03-26 Rainer Toebbicke (1311) Lockless path through afs_linux_dentry_revalidate 2010-03-23 Derrick Brashear (1625) preliminary support for pinned vcaches 2010-03-19 Michael Meffie (215) rxdebug: show delayed abort packet count for rx peers 2010-03-17 Michael Meffie (1562) ihandle positional read and write 2010-03-17 Simon Wilkinson (1581) Linux Keyrings: don't ignore error code from session keyring creation 2010-03-17 Derrick Brashear (1553) dynamic volume allocation 2010-02-25 Michael Meffie (1092) DAFS: avoid volume lock contention during initialization 2010-02-24 Simon Wilkinson (1392) More warnings cleanup 2010-02-24 Jacob Thebault-Spieker (433) Add throughput framework to cm_RankServer() 2010-02-23 Anders Kaseorg (1373) Adjust afs_lockctl to compensate for byte-range lock fixes 2010-02-15 Michael Meffie (1001) return an error from afs_readdir when out of buffers 2010-02-06 Dan Hyde (1212) VTRANS_LOCK not needed in TryUnlock 2010-02-03 Dan Hyde (1191) runningCalls: VOL_COUNT_LOCK vs VTRANS_LOCK 2010-02-03 Derrick Brashear (1172) linux mmap anti-deadlock shouldn't break StoreAllSegments 2010-02-03 Derrick Brashear (1201) basic kernel event system for afs cm 2010-02-02 Simon Wilkinson (1072) Unix CM: Conflate rxfs_[store,fetch]Variables 2010-01-20 Simon Wilkinson (1074) Unix CM: Include memcache's tiov in rxfs_context 2009-11-29 Andrew Deason (875) Make ubik use unsigned addresses 2009-11-18 Andrew Deason (709) Break origin's callback for RXAFS_Rename target 2009-11-04 Andrew Deason (436) Avoid unnecessarily updating .. in SAFSS_Rename 2009-09-09 Matt Benjamin (435) clear stat flag on renamed directories 2009-08-29 Matt Benjamin (376) K5SSL by Marcus Watts 2009-07-29 Michael Meffie (147) Fix bosserver directory creation 2009-07-24 Hartmut Reuter (70) preparing rxosd integration: change in AFSFetchStatus Patches merged into the master branch Date Author Change# Description 2010-04-10 Matt Smith (1737) Fix problems from afs_osi_gcpags reorganization 2010-04-10 Michael Meffie (1735) afsmonitor: fix segv on exit 2010-04-10 Michael Meffie (1734) afsmonitor: show busy counts 2010-04-10 Marc Dionne (1733) Fix UKERNEL build error - include afs/afs_osi.h 2010-04-09 Matt Smith (1727) Move contents of afs_osi_gcpags to per-OS files 2010-04-09 Andrew Deason (1679) Correct incorrect type-punning fixes 2010-04-09 Michael Meffie (1731) afsmonitor: add fs callback xstats collection 2010-04-09 Michael Meffie (1730) afsmonitor: avoid showing full perf stats garbage 2010-04-09 Derrick Brashear (1729) ukernel osi prototypes header 2010-04-09 Andrew Deason (1722) UKERNEL: allow creation of non-detached threads 2010-04-09 Andrew Deason (1721) Use AFS_CACHE_VNODE_PATH for UKERNEL 2010-04-09 Andrew Deason (1714) Make osi_GetTime work on 64-bit libuafs 2010-04-09 Andrew Deason (1720) afsd: squash inode format warning 2010-04-09 Andrew Deason (1719) UKERNEL: prototype uafs_Shutdown 2010-04-09 Andrew Deason (1718) UKERNEL: Use real vnode type constants 2010-04-09 Andrew Deason (1717) UKERNEL: check for null afs_CurrentDir on shutdown 2010-04-09 Andrew Deason (1716) UKERNEL: add uafs_statvfs 2010-04-09 Andrew Deason (1715) Prevent uafs_readdir/closedir segfault 2010-04-09 Russ Allbery (1713) Update Debian packaging files 2010-04-09 Russ Allbery (1712) Add OpenAFS-debug.*.plist to .gitignore 2010-04-08 Michael Meffie (1601) pts mem -expandgroups option 2010-04-08 Michael Meffie (1600) pts mem -supergroup option 2010-04-07 Russ Allbery (1710) Explain in CellServDB man page that server lines can be omitted 2010-04-07 Simon Wilkinson (1705) Linux: kmap() not page_address() 2010-04-07 Andrew Deason (1709) Fix typo in bos_create manpage 2010-04-07 Rod Widdowson (1708) Make tests/afcp compile cleanly 2010-04-07 Russ Allbery (1706) Reallocate memory in aklog for the AFS ID string 2010-04-07 Russ Allbery (1704) Make src/rx/rx.c not executable 2010-04-07 Russ Allbery (1707) Improve demand-attach fileserver bos documentation 2010-04-06 Jeffrey Altman (1702) Windows: Support new Cygwin docbook stylesheet location 2010-04-06 Jeffrey Altman (1696) Windows: WinTorture Verbose mode display all logged messages 2010-04-06 Jeffrey Altman (1701) Windows: permit documentation to be built without binaries 2010-04-06 Jeffrey Altman (1699) Windows: tag is listitem not llstitem 2010-04-06 Derrick Brashear (1700) make openafs 1.5.73.3 2010-04-06 Derrick Brashear (1698) macos bulkstat avoid reclaiming vnodes 2010-04-06 Derrick Brashear (1690) avoid macos bulkstat vlru when no non-dead vnodes exist 2010-04-06 Derrick Brashear (1693) panic generation update 2010-04-06 Jeffrey Altman (1695) Windows: cm_UpdateVolumeLocation !append exts to num vol names 2010-04-06 Jeffrey Altman (1697) Rx: Remove conn_call_lock contention between rx_NewCall and rx_EndCall 2010-04-05 Aditya Sarawgi (1694) Replace kmodstat by kldstat 2010-04-05 Jeffrey Altman (1685) Fix usage of RX_CALL_TQ_WAIT flag 2010-04-05 Derrick Brashear (1682) rx_ClearTransmitQueue should signal waiters when flushing 2010-04-05 Derrick Brashear (1692) macos panic decoder update 2010-04-02 Derrick Brashear (1687) macos 32 bit platform user address transform 2010-04-02 Derrick Brashear (1688) make 1.5.73.2 2010-04-02 Derrick Brashear (1684) freebsd switch back to condvar-based sleep 2010-04-02 Derrick Brashear (1686) macos installer pane warning fix 2010-04-02 Andrew Deason (1681) tubik: Correct use of flags_cond and version_cond 2010-04-02 Andrew Deason (1680) Kill afs_inet_ntoa 2010-04-02 Derrick Brashear (1683) freebsd glock assertions 2010-04-01 Andrew Deason (1678) fssync-debug: fix strict-aliasing problems 2010-04-01 Simon Wilkinson (1645) Fix formatting issues in src/afs 2010-04-01 Benjamin Kaduk (1677) Set a storeOps storeproc for the memcache case 2010-03-31 Benjamin Kaduk (1676) Fix build for FBSD80 2010-03-31 Benjamin Kaduk (1675) Update to the new thread world order for FBSD 2010-03-31 Benjamin Kaduk (1674) Include limits.h for FBSD 2010-03-31 Derrick Brashear (1670) openafs 1.5.73.1 2010-03-31 Benjamin Kaduk (1672) Make GCPAGs_perproc_func cleaner for FBSD case 2010-03-31 Jonathan Billings (1671) Updated RedHat RPM spec file to include unreferenced files 2010-03-30 Jonathan Billings (1669) Move restorevol to bin from sbin in make dest 2010-03-30 Derrick Brashear (1668) darwin notify avoid reentrant vfs context panic 2010-03-30 Russ Allbery (1667) Update VCS instructions for Git 2010-03-30 Benjamin Kaduk (1665) Catch up to dynamically-sized cr_groups in FBSD80 2010-03-29 Davor Ocelic (1666) Minor state_analyzer manpage corrections 2010-03-29 Rod Widdowson (1649) Render the IP address for the "Ubik: Lost contact with sync-site" log message in the same way that all other IP addresses are (via afs_inet_ntoa, rather than stripping the buytes out in a manner which assumes a specific endianism). 2010-03-29 Davor Ocelic (1655) Initial; add state_analyzer manpage 2010-03-28 Simon Wilkinson (1042) Linux: Replace invalidate_inode_pages 2010-03-28 Jeffrey Altman (1664) Windows: buffers whose offsets are beyond EOF should be zero filled and locally allocated 2010-03-27 Claudio Bisegni (1656) GUI Update for Kerberos Ticket Renew 2010-03-27 Derrick Brashear (1663) aklog pt error table warning fix 2010-03-27 Derrick Brashear (1661) aklog more error tables 2010-03-27 Chas Williams - CONTRACTOR (1080) LINUX: you dont need to memset() after allocating credentials 2010-03-25 Jeffrey Altman (1660) Windows: afslogon.dll vs windows 7 2010-03-25 Jeffrey Altman (1659) Windows: aklog must reset viceId to 0 before pr_CreateUser call 2010-03-25 Jeffrey Altman (1658) Windows: output pt error messages as strings 2010-03-24 Derrick Brashear (1651) growl agent should handle port busy 2010-03-24 Derrick Brashear (1654) avoid double-free cell name canonicalization 2010-03-24 Derrick Brashear (1648) afsdump warning killing 2010-03-24 Simon Wilkinson (1647) Linux : Apply more dget_parent() pixie dust 2010-03-24 Derrick Brashear (1642) make 1.5.73 relnotes 2010-03-24 Derrick Brashear (1620) openafs 1.5.73 version strings 2010-03-24 Jeffrey Altman (1521) Updating UserGuide with Kerberos v5 authentication 2010-03-24 Asanka Herath (1633) Windows: Use a timestamp for the minidump filename 2010-03-24 Asanka Herath (1632) Windows: Monitor requests and gather diagnostics before a timeout 2010-03-24 Derrick Brashear (1641) add missed release notes 2010-03-24 Jeffrey Altman (1636) Windows: changelog for 1.5.73 2010-03-23 Jeffrey Altman (1639) Windows: cm_attrs_t requires inclusion of cm_vnodeops.h 2010-03-23 Jeffrey Altman (1638) Windows LWP and UNIX LWP do not have the same lwp_cpptr structure 2010-03-23 Marc Dionne (1637) Warning fix: print burstWait fields 2010-03-23 Marc Dionne (1635) Fix #ifdef typo 2010-03-23 Marc Dionne (1634) Define __USE_XOPEN conditionally 2010-03-23 Asanka Herath (1602) Windows: Make default mode bits configurable 2010-03-23 Derrick Brashear (1629) remove vnop needs discon lock 2010-03-23 Claudio Bisegni (1606) Develop Kerberos renew system for ticket 2010-03-23 Derrick Brashear (1631) kill MultiBreakVolumeCallBack too 2010-03-23 Andrew Deason (1628) Remove BreakVolumeCallBacks prototype 2010-03-23 Russ Allbery (1589) vldb_check man page should say -vheader, not -pheader 2010-03-23 Andrew Deason (1550) vos: correct syncvldb -verbose server byte order 2010-03-23 Derrick Brashear (1547) make tryevalfakestat really not block 2010-03-23 Derrick Brashear (1315) viced remove dead BreakVolumeCallBacks function 2010-03-23 Andrew Deason (1559) vos: Avoid LWP stack overflow error on SIGINT 2010-03-23 Andrew Deason (1558) vos: Use IOMGR_SoftSig for signals 2010-03-23 Andrew Deason (1557) vos: Mark longjmp-used variables as 'volatile' 2010-03-23 Russ Allbery (1617) Fix strict aliasing problems or add -fno-strict-aliasing 2010-03-22 Andrew Deason (1582) Use AC_USE_SYSTEM_EXTENSIONS 2010-03-22 Derrick Brashear (1590) aix mount failure unlock and seterror 2010-03-22 Derrick Brashear (1386) update link order 2010-03-22 Simon Wilkinson (1340) XDR: Stop the madness 2010-03-22 Russ Allbery (1616) Use sigset_t and sigfillset instead of memset 2010-03-22 Russ Allbery (1615) Move non-executable stack assembly code to end of file 2010-03-22 Derrick Brashear (1599) multibreak callbacks add host marking 2010-03-21 Derrick Brashear (1611) aix vfs table entry in rc script 2010-03-21 Derrick Brashear (1610) salvage variable initialization 2010-03-21 Derrick Brashear (1598) comment assumptions in lih0_r 2010-03-21 Andrew Deason (1235) Create missing root directory when ORPH_ATTACH 2010-03-21 Derrick Brashear (1609) aix krb5 error message handling 2010-03-21 Derrick Brashear (1608) panic prototype for aix 6 2010-03-21 Simon Wilkinson (1577) Don't count root session keyrings against quota 2010-03-20 Derrick Brashear (451) macos fsevents hinting 2010-03-19 Jeffrey Altman (1531) afsadminutil: translate krb5 error messages on Windows 2010-03-19 Andrew Deason (1596) volume_inline.h does not need sys/file.h 2010-03-19 Andrew Deason (1406) DAFS: Replace partition locks with volume locks 2010-03-19 Derrick Brashear (1594) macos uninstall redux 2010-03-19 Derrick Brashear (1593) update macos uninstaller 2010-03-19 Dan Hyde (1213) VOL_LOCK needed when traversing DiskPartitionList 2010-03-18 Benjamin Kaduk (1587) Catch up with FBSD80's removal of thread argument to VFS calls 2010-03-18 Derrick Brashear (1572) aix vnode hold simplification 2010-03-18 Derrick Brashear (1584) regain glock on storedata error exit 2010-03-18 Derrick Brashear (1583) kill apsl afssettings and fstab 2010-03-18 Evan Broder (778) Increase the maximum number of sysnames 2010-03-17 Andrew Deason (1405) Add code for locking individual volumes on disk 2010-03-17 Benjamin Kaduk (1576) Avoid panic on shutdown with memcache and INVARIANTS 2010-03-17 Benjamin Kaduk (1560) Allocate and free backing store for event mutices 2010-03-16 Derrick Brashear (1573) rx nat event connection reference 2010-03-16 Marc Dionne (1575) growlagent: remove generated Makefile with make distclean 2010-03-15 Antoine Verheijen (1574) Remove return of value for afs_MarinerLogFetch() 2010-03-15 Derrick Brashear (1554) freebsd per-event mutexes 2010-03-15 Andrew Deason (1545) vlserver: make rxinfo threadsafe 2010-03-15 Derrick Brashear (1538) afsdb lookup shouldn't leak memory on realname lookup 2010-03-15 Michael Meffie (1570) squash warning in db_verify 2010-03-13 Jeffrey Altman (1567) Windows: warnings removal for afskfw.c 2010-03-13 Jeffrey Altman (1529) Windows: afskfw - conditionalize use of krb5_get_error_message for KFW 3.1 and earlier 2010-03-13 Jeffrey Altman (1530) Windows: netidmgr - conditionalize use of krb5_get_error_message for KFW 3.1 and earlier 2010-03-11 Derrick Brashear (1561) macos dropbox fix for finder 2010-03-10 Derrick Brashear (1551) dkms configure correctly 2010-03-10 Andrew Deason (1556) Squash pthreaded vos warnings 2010-03-10 Simon Wilkinson (1555) Don't always use the local cell for db clients 2010-03-09 Simon Wilkinson (1552) Update RPM CellServDB 2010-03-09 Andrew Deason (1549) udebug: Fix byte ordering of last yes host 2010-03-09 Andrew Deason (1548) vldb_check: do not ntohl u_chars 2010-03-09 Andrew Deason (1404) Add FSYNC_VerifyCheckout 2010-03-09 Andrew Deason (1376) Add DAFS documentation overview for developers 2010-03-09 Andrew Deason (1358) Add VLockFileReinit 2010-03-09 Andrew Deason (1357) VLockFile: add a couple of asserts 2010-03-09 Andrew Deason (1356) Schedule all salvages via VScheduleSalvage_r 2010-03-09 Andrew Deason (1349) Add FSSYNC debug logging 2010-03-09 Andrew Deason (1390) Move *SYNC string translation out of fssync-debug 2010-03-09 Andrew Deason (1348) Do not rely on vol header for V*VolumeHandles_r 2010-03-09 Derrick Brashear (1544) darwin report kext load address 2010-03-09 Benjamin Kaduk (1541) Export prototypes for osi_fbsd_{alloc,free} for use in rx 2010-03-09 Benjamin Kaduk (1540) Use correct types for UFS devices 2010-03-09 Benjamin Kaduk (1539) Use the correct API for msleep() in FBSD's afs_osi_TimedSleep() 2010-03-09 Benjamin Kaduk (1526) FBSD build finishes for me 2010-03-08 Derrick Brashear (1537) afsconf srv lookup fill cellname 2010-03-07 Derrick Brashear (1533) Begin support for OpenBSD 4.7 2010-03-07 Derrick Brashear (1532) OpenBSD: eliminate use of VREF() macro 2010-03-07 Benjamin Kaduk (1528) Be type correct in osi_ThreadUnique() for FBSD 2010-03-07 Benjamin Kaduk (1527) FBSD module loads now 2010-03-06 Jeffrey Altman (1520) Windows: use krb5_get_error_message instead of error_message 2010-03-06 Simon Wilkinson (1524) Linux: Make keyring destructor remove all tokens 2010-03-06 Simon Wilkinson (1525) Linux: Fix builds on RHEL4 2010-03-06 Marc Dionne (1523) Linux: replace invalidate_inode_pages 2010-03-06 Jeffrey Altman (1519) Windows: use krb5_get_error_message to translate krb5 errors in afskfw library 2010-03-06 Jeffrey Altman (1518) Windows: use krb5_get_error_message in netidmgr_plugin 2010-03-06 Jeffrey Altman (1517) Windows: Add krb5 error message functions to loadfuncs header 2010-03-05 Jeffrey Altman (1514) Windows: reset local mount point count during freelance re-initialization 2010-03-05 Simon Wilkinson (1522) Linux : Don't leak GLOCK when writing CellServDB 2010-03-05 Derrick Brashear (1513) add growl agent for macos 2010-03-05 Derrick Brashear (1511) darwin afshelper fix startup check 2010-03-04 Derrick Brashear (1512) evalmount copy out volid for sure 2010-03-03 Derrick Brashear (1507) macos shutdown consistent behavior 2010-03-03 Derrick Brashear (1505) add user warning facility via mariner for macos 2010-03-03 Derrick Brashear (1504) support mariner messages sans vcache 2010-03-03 Derrick Brashear (1503) rewrite marinerlogfetching 2010-03-03 Derrick Brashear (1502) restore mariner storing message 2010-03-03 Derrick Brashear (1501) de-printf the cache manager 2010-03-03 Jason Edgecombe (1308) Add a section on how to tune the AFS cache using xstat_cm_test 2010-03-03 Marc Dionne (1506) Remove duplicate make targets in tubik, cleanup dependencies 2010-03-02 Derrick Brashear (1500) darwin vfsops ansification 2010-03-02 Derrick Brashear (1499) afs_util don't use printf 2010-03-02 Derrick Brashear (1371) BOP_MOVE and userspace move EXDEV helper 2010-03-01 Claudio Bisegni (1492) OSXPreferencePane checkAfsStatusForStartup method modification for search /afs volume for determinate if afs is on has been transfered into checkAfsStatus. checkAfsStatusForStartup method is used to check when afs start axitn system startup. Anyway these 2010-03-01 Marc Dionne (1489) Don't pass NULL to strcmp Patches merged into the stable branch Date Author Change# Description 2010-04-09 Hans-Werner Paulsen (1711) Build and install PIC versions of libafsrpc and libafsauthent 2010-04-01 Dan Hyde (1595) VOL_LOCK needed when traversing DiskPartitionList 2010-03-30 Simon Wilkinson (1580) Linux: don't count pag keys against root's keyring quotas 2010-03-25 Marc Dionne (1657) Print rxdebug statistics as unsigned values 2010-03-24 Evan Broder (1650) Increase the maximum number of sysnames 2010-03-23 Dan Hyde (1588) volmonitor keep vtrans lock 2010-03-23 Andrew Deason (1627) Add support for amd64_obsd46 2010-03-23 Andrew Deason (1626) Add amd64 subtarget for OpenBSD 2010-03-23 Andrew Deason (1624) libafs: WRITEPAGE_ACTIVATE is 2.6-only 2010-03-23 Andrew Deason (1613) Create missing root directory when ORPH_ATTACH 2010-03-23 Andrew Deason (1623) libafs: afs_backing_dev_info is 2.6-only 2010-03-23 Andrew Deason (1622) libafs: Remove some unused functions 2010-03-22 Russ Allbery (1618) Move non-executable stack assembly code to end of file 2010-03-18 Dan Hyde (1586) volmonitor copy link before calling free 2010-03-17 Andrew Deason (1368) h_TossStuff_r: make sure host does not go away 2010-03-17 Andrew Deason (1367) h_TossStuff_r: check held-ness after lock 2010-03-15 Michael Meffie (1571) Avoid 'static __inline' on HPUX 2010-03-10 Andrew Deason (1370) Allow GetSomeSpace_r to select an optimal host 2010-03-10 Andrew Deason (1369) Remove lih_r 2010-03-08 Derrick Brashear (1536) remove fc_test from normal build 2010-03-08 Derrick Brashear (1535) openafs 1.4.12 2010-03-07 Antoine Verheijen (1510) Begin support for OpenBSD 4.7 2010-03-07 Antoine Verheijen (1509) OpenBSD: eliminate use of VREF() macro 2010-03-05 Derrick Brashear (1516) darwin afshelper fix startup check 2010-03-05 Derrick Brashear (1515) correct cred mgmt typo 2010-03-03 Derrick Brashear (1508) remove the force.. comments 2010-03-03 Derrick Brashear (1498) Linux: bdi doesn't always have a name 2010-03-03 Derrick Brashear (1497) linux bdi allocate memory 2010-03-01 Derrick Brashear (1494) OSXPreferencePane checkAfsStatusForStartup method modification for search /afs volume for determinate if afs is on has been transfered into checkAfsStatus. checkAfsStatusForStartup method is used to check when afs start axitn system startup. Anyway these 2010-03-01 Derrick Brashear (1493) macos prefs pane more reliable running indicator Resolved Tickets Here is a list of tickets that have been resolved since March 1, 2010: ticket # state created title 21423: resolved Sep 07, 2005 Enhanced auto CACHESIZE code for afs.rc.linux 22608: resolved Oct 24, 2005 redhat-4 afs.rc smp startup broke 23229: resolved Nov 16, 2005 Openafs 1.4.0 cache on ext3 volume causes massive filesystem corruption 36725: resolved Aug 01, 2006 Relicense afssettings.m under saner license 37658: resolved Aug 14, 2006 openafs-1.4.1 libafsrpc missing symbols x86_64 41823: resolved Oct 05, 2006 reliability bug in caching seeked files ... 49718: resolved Dec 19, 2006 vos dump fails on amd64_linux26 client 53759: resolved Feb 11, 2007 1.4.2 Debian sarge afsd crash in afs_checkrootvolume 54062: resolved Feb 14, 2007 openafs 1.4.3rc2 still coredumps on openbsd40 54299: resolved Feb 17, 2007 problem after volume moves with 1.5.15 92653: resolved Apr 01, 2008 1.4.7pre2 - Dependency on /boot/config-{kernel-version} 106150: resolved Jul 06, 2008 Kernel memory leak with 1.4.7 on Linux 2.6.25 107089: resolved Jul 12, 2008 Kernel panic -- 1.5.39 110696: resolved Aug 06, 2008 OpenAFS 1.4.7 on Mac OS X 10.5.x: intermittent access failures 112681: resolved Aug 19, 2008 RHEL4 Kernel Panic (firefox 3 related?) 117415: resolved Sep 24, 2008 Is there any script to uninstall OpenAFS on Mac OS X 10.5 123798: resolved Dec 01, 2008 freebsd client panics if no root.afs 123806: resolved Dec 03, 2008 nbsd-44 pass 1 123820: resolved Dec 05, 2008 Request for multiple realm support in 1.4.x 124083: resolved Jan 03, 2009 afssettings does not use build system correctly 124591: resolved Apr 04, 2009 freebsd 8 wip 124761: resolved May 11, 2009 Issues blocked for inclusion in future stable releases 124877: resolved May 27, 2009 obsd 1_5_x fixups 125634: resolved Nov 12, 2009 OpenAFS bug: Uninstall.command for Mac OS X does not work (fix attached) 126067: resolved Jan 04, 2010 rewrite afs_MemWriteBlk() using afs_MemWritevBlk() 126107: resolved Jan 08, 2010 emacs out of AFS server space locks compute node in D wait state 126514: resolved Feb 16, 2010 Linux: Ooops in __wake_up_common (from bdi_start_fn) 126678: resolved Mar 05, 2010 Linux: 1.5.x doesn't build on RHEL4 126716: resolved Mar 10, 2010 1.5.72's vos examine doesn't use cell provided by -cell argument 126794: resolved Mar 22, 2010 Wince when foreign bull-dogs sent out their threate 126812: resolved Mar 24, 2010 OpenAFS 1.5.73 MacOSX 10.6.2 growlagent-openafs crashes 126813: resolved Mar 24, 2010 OpenAFS 1.5.73 aklog crash From jason@rampaginggeek.com Wed Apr 14 02:10:58 2010 From: jason@rampaginggeek.com (Jason Edgecombe) Date: Tue, 13 Apr 2010 21:10:58 -0400 Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: <4BC47100.1030802@secure-endpoints.com> References: <4BC47100.1030802@secure-endpoints.com> Message-ID: <4BC51622.8000903@rampaginggeek.com> Jeffrey Altman wrote: > In 2002, the OpenAFS version of the "vos listaddrs" command was updated > to include the Arla -printuuid and -noresolve options which permits the > UUID and IP address of registered file servers to be displayed. For > example: > > UUID: 006cab10-0e3e-1b20-a3-aa-2601a8c0aa77 > 24.193.47.88 > 192.168.122.1 > 192.168.1.38 > > In 2008, the -noresolve option was made generic so that it could apply > to all vos commands so that instead of seeing DNS names the actual IP > addresses of server could be viewed. This change was made because DNS > name resolution often makes it appear that a file server is properly > registered when instead it is in fact not. > > However, IP addresses are not the canonical method of identifying a file > server. For that the UUID is required and at the present time there is > no mechanism when using vos listvldb or vos examine to identify the UUID > of the server on which a volume is located. This lack has come up > several times in the #openafs IRC channel when attempting to help users > setup new cells or add new file servers. The most recent time on March > 30th. > > Gerrit http://gerrit.openafs.org/#change,1742 is an attempt to add > -printuuid as a standard option to all vos commands. The only issue at > the moment is what the format of the output should look like. UUIDs and > DNS names are long. Extending the existing format to include the UUID > inline with each server produces output that will not fit in an 80 > column terminal. > > An example of "vos examine -printuuid" output: > > root.cell 537870331 RW 42 K On-line > ASCLEPIUS.MIT.EDU [0037555a-be36-19a6-a2-4d-5e3c0912aa77] /vicepr > RWrite 537870331 ROnly 537870333 Backup 537870332 > MaxQuota 500 K > Creation Fri Jun 06 12:24:21 2008 > Copy Thu Feb 26 11:43:23 2009 > Backup Tue Apr 13 02:00:17 2010 > Last Update Thu Oct 18 12:44:23 2007 > 7647 accesses in the past day (i.e., vnode references) > > RWrite: 537870331 ROnly: 537870333 Backup: 537870332 > number of sites -> 4 > server ASCLEPIUS.MIT.EDU [0037555a-be36-19a6-a2-4d-5e3c0912aa77] > partition /vicepr RW Site > server ASCLEPIUS.MIT.EDU [0037555a-be36-19a6-a2-4d-5e3c0912aa77] > partition /vicepr RO Site > server MNEMOSYNE.MIT.EDU [005d91e8-f824-19a6-aa-5c-613c0912aa77] > partition /vicepr RO Site > server IXION.MIT.EDU [00086236-fa87-19a6-b4-de-ab015b12aa77] > partition /vicepr RO Site > > An example of "vos listvldb -printuuid" output: > > root.cell > RWrite: 536870915 ROnly: 536870916 > number of sites -> 4 > server bethlehem.your-file-system.com > [0008fa02-d48c-19b9-81-fc-419a1dccaa77] partition /vicepa RW Site > server bethlehem.your-file-system.com > [0008fa02-d48c-19b9-81-fc-419a1dccaa77] partition /vicepa RO Site > server faultline.your-file-system.com > [0007580a-7001-1aae-85-8e-2f9a1dccaa77] partition /vicepa RO Site > server cpe-24-193-47-88.nyc.res.rr.com > [006cab10-0e3e-1b20-a3-aa-2601a8c0aa77] partition /vicepa RO Site > > One alternative output format that could be used when the -printuuid > option is specified is found below. > > vos examine -printuuid: > > root.cell 537870331 RW 42 K On-line > UUID: 0037555a-be36-19a6-a2-4d-5e3c0912aa77 > Server ASCLEPIUS.MIT.EDU > Partition /vicepr > RWrite 537870331 ROnly 537870333 Backup 537870332 > MaxQuota 500 K > Creation Fri Jun 06 12:24:21 2008 > Copy Thu Feb 26 11:43:23 2009 > Backup Tue Apr 13 02:00:17 2010 > Last Update Thu Oct 18 12:44:23 2007 > 7647 accesses in the past day (i.e., vnode references) > > RWrite: 537870331 ROnly: 537870333 Backup: 537870332 > number of sites -> 4 > RW Site > server ASCLEPIUS.MIT.EDU > uuid 0037555a-be36-19a6-a2-4d-5e3c0912aa77 > partition /vicepr > RO Site > server ASCLEPIUS.MIT.EDU > uuid 0037555a-be36-19a6-a2-4d-5e3c0912aa77 > partition /vicepr > RO Site > server MNEMOSYNE.MIT.EDU > uuid 005d91e8-f824-19a6-aa-5c-613c0912aa77 > partition /vicepr > RO Site > server IXION.MIT.EDU > uuid 00086236-fa87-19a6-b4-de-ab015b12aa77 > partition /vicepr > > vos listvldb -printuuid: > > root.cell > RWrite: 536870915 ROnly: 536870916 > number of sites -> 4 > RW Site > server bethlehem.your-file-system.com > uuid 0008fa02-d48c-19b9-81-fc-419a1dccaa77 > partition /vicepa > RO Site > server bethlehem.your-file-system.com > uuid 0008fa02-d48c-19b9-81-fc-419a1dccaa77 > partition /vicepa > RO Site > server faultline.your-file-system.com > uuid 0007580a-7001-1aae-85-8e-2f9a1dccaa77 > partition /vicepa > RO Site > server cpe-24-193-47-88.nyc.res.rr.com > uuid 006cab10-0e3e-1b20-a3-aa-2601a8c0aa77 > partition /vicepa > > Please offer your opinions. As people have a variety of scripts that > parse the output of vos commands to automate behaviors, we would not be > changing the default output. Any format change would only be used when > the -printuuid option is specified. > I like this output style best: RO Site server cpe-24-193-47-88.nyc.res.rr.com uuid 006cab10-0e3e-1b20-a3-aa-2601a8c0aa77 partition /vicepa If everything is put on one line, I would prefer the uuid column first. That way, the columns line up better. Would it be possible to use a shortened form of the uuid like git uses short commit hash strings? Jason From atro.tossavainen+openafs@helsinki.fi Wed Apr 14 11:10:24 2010 From: atro.tossavainen+openafs@helsinki.fi (Atro Tossavainen) Date: Wed, 14 Apr 2010 13:10:24 +0300 (EEST) Subject: [OpenAFS] Re: Ubik problem In-Reply-To: <20100413131129.b790823c.adeason@sinenomine.net> Message-ID: <201004141010.o3EAAOZr014266@ruuvi.it.helsinki.fi> OK, I have it again. User reports inability to log in. $ kas -a dsakfksda Administrator's (dsakfksda) Password: ka> exa useraccount examine: ticket contained unknown key version number getting information for useraccount. So: $ udebug 128.214.88.114 7004 -long Host's addresses are: 128.214.88.114 10.0.0.3 172.16.0.1 172.17.0.1 172.18.0.1 Host's 128.214.88.114 time is Wed Apr 14 13:01:35 2010 Local time is Wed Apr 14 13:01:35 2010 (time differential 0 secs) Last yes vote for 128.214.58.174 was 14 secs ago (sync site); Last vote started 13 secs ago (at Wed Apr 14 13:01:22 2010) Local db version is 1271074432.4 I am not sync site Lowest host 128.214.58.174 was set 14 secs ago Sync host 128.214.58.174 was set 14 secs ago Sync site's db version is 1271074432.4 0 locked pages, 0 of them for write Server (128.214.58.174): (db 0.0) last vote rcvd 165054 secs ago (at Mon Apr 12 15:10:41 2010), last beacon sent 165054 secs ago (at Mon Apr 12 15:10:41 2010), last vote was no dbcurrent=0, up=1 beaconSince=1 $ udebug 128.214.58.174 7004 -long Host's addresses are: 128.214.58.174 Host's 128.214.58.174 time is Wed Apr 14 13:01:50 2010 Local time is Wed Apr 14 13:01:54 2010 (time differential 4 secs) Last yes vote for 128.214.58.174 was 12 secs ago (sync site); Last vote started 12 secs ago (at Wed Apr 14 13:01:42 2010) Local db version is 1271074432.4 I am sync site until 47 secs from now (at Wed Apr 14 13:02:41 2010) (2 servers) Recovery state 1f Sync site's db version is 1271074432.4 0 locked pages, 0 of them for write Last time a new db version was labelled was: 164878 secs ago (at Mon Apr 12 15:13:56 2010) Server (128.214.88.114 10.0.0.3 172.16.0.1 172.17.0.1 172.18.0.1): (db 1271074432.4) last vote rcvd -3 secs ago (at Wed Apr 14 13:01:57 2010), last beacon sent -3 secs ago (at Wed Apr 14 13:01:57 2010), last vote was yes dbcurrent=1, up=1 beaconSince=1 Nothing obvious - at least to my untrained eye. Using kas specifically against 128.214.58.174 (the sunx86_510 OpenAFS host) reproduces the error with this account. Using kas specifically against 128.214.88.114 (the sun4x_58 IBM AFS host) shows correct information, however. bos restart 128.214.58.174 kaserver made the problem go away. There is no indication of anything unusual in the AuthLog of 128.214.58.174. All pointers welcome. -- Atro Tossavainen (Mr.) / The Institute of Biotechnology at Systems Analyst, Techno-Amish & / the University of Helsinki, Finland, +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own. < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS From rtb@pclella.cern.ch Wed Apr 14 13:52:32 2010 From: rtb@pclella.cern.ch (Rainer Toebbicke) Date: Wed, 14 Apr 2010 14:52:32 +0200 Subject: [OpenAFS] Re: Ubik problem In-Reply-To: <201004141010.o3EAAOZr014266@ruuvi.it.helsinki.fi> References: <201004141010.o3EAAOZr014266@ruuvi.it.helsinki.fi> Message-ID: <4BC5BA90.8020608@pclella.cern.ch> Atro Tossavainen schrieb: > OK, I have it again. User reports inability to log in. > > $ kas -a dsakfksda > Administrator's (dsakfksda) Password: > ka> exa useraccount > examine: ticket contained unknown key version number getting information for useraccount. > One of your DB servers has an incorrect /usr/afs/etc/KeyFile (in Transarc-naming, if you use the /var/openafs style it's accordingly). Very likely you added a new key but did not propagate the KeyFile everywhere. "bos listkey " should help. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rainer Toebbicke European Laboratory for Particle Physics(CERN) - Geneva, Switzerland Phone: +41 22 767 8985 Fax: +41 22 767 7155 From atro.tossavainen+openafs@helsinki.fi Wed Apr 14 14:06:23 2010 From: atro.tossavainen+openafs@helsinki.fi (Atro Tossavainen) Date: Wed, 14 Apr 2010 16:06:23 +0300 (EEST) Subject: [OpenAFS] Re: Ubik problem In-Reply-To: <4BC5BA90.8020608@pclella.cern.ch> Message-ID: <201004141306.o3ED6NOW027593@ruuvi.it.helsinki.fi> Rainer, > One of your DB servers has an incorrect /usr/afs/etc/KeyFile (in > Transarc-naming, if you use the /var/openafs style it's accordingly). > > Very likely you added a new key but did not propagate the KeyFile everywhere. > "bos listkey " should help. According to bos listkey of the various servers (the two db/file ones and the new file-only-so-far) the key has the same cksum on all servers and has been last changed on the same date (which is a while ago). Which isn't that surprising given that I copied /usr/afs/etc from the old server verbatim. This does also not explain why the problem goes away with a kaserver restart - only to reappear in a bit? -- Atro Tossavainen (Mr.) / The Institute of Biotechnology at Systems Analyst, Techno-Amish & / the University of Helsinki, Finland, +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own. < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS From scs@umich.edu Wed Apr 14 15:47:26 2010 From: scs@umich.edu (Steve Simmons) Date: Wed, 14 Apr 2010 10:47:26 -0400 Subject: [OpenAFS] OS X, AFS Home Directories and SSH/Unix Permissions In-Reply-To: References: <393853E2-C3D1-4F6B-854C-ED0E1D06094D@cs.wisc.edu> Message-ID: On Apr 13, 2010, at 7:02 PM, Derrick Brashear wrote: >> Has anyone run into something like this? Is there a way to change = the permissions AFS reports to OSX, or is there a work around I'm = failing to see? >=20 > Check out the RealModes setting. Edit > /var/db/openafs/etc/config/settings.plist, and rerun > /var/db/openafs/etc/config/afssettings as root. Wow. How the hell did I miss that? I'm passing this on to our OSX = support guys. Steve= From scs@umich.edu Wed Apr 14 15:51:47 2010 From: scs@umich.edu (Steve Simmons) Date: Wed, 14 Apr 2010 10:51:47 -0400 Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: <4BC4E1FF.5050305@secure-endpoints.com> References: <4BC47100.1030802@secure-endpoints.com> <4BC4797B.3070202@email.unc.edu> <6A5BB6C1-955E-4740-8CDE-FB9CD7663BD0@umich.edu> <4BC4E1FF.5050305@secure-endpoints.com> Message-ID: On Apr 13, 2010, at 5:28 PM, Jeffrey Altman wrote: >>=20 >> I'm a long-time fan of having a switch that causes tools to dump = their data in an easy-to-machine-parse format. That isn't always doable, = but when it is, it's a big win. >=20 > As Andrew pointed out in another reply in this thread, the -format > switch is support to provide that but it fails to provide a consistent > (value - data) pair per line. Exactly my point. We currently snarf off all that data nightly via = script that parses the output from vos e -format. It works but was a = pain. Note, tho, that some data doesn't adapt well to single-line output. For = example,=20 ... root.cell RWrite: 536870915 ROnly: 536870916 number of sites -> 4 server bethlehem.your-file-system.com partition /vicepa RW Site server bethlehem.your-file-system.com partition /vicepa RO Site server faultline.your-file-system.com partition /vicepa RO Site server cpe-24-193-47-88.nyc.res.rr.com partition /vicepa RO Site RWrite: 536870915 ROnly: 536870916 number of sites -> 4 server bethlehem.your-file-system.com partition /vicepa RW Site server bethlehem.your-file-system.com partition /vicepa RO Site server faultline.your-file-system.com partition /vicepa RO Site server cpe-24-193-47-88.nyc.res.rr.com partition /vicepa RO Site ... just doesn't map well to single-line. We currently deal with this by = creating four records, each will all the data from the rest of the = output and the specifics of the four entries above. Steve From shadow@gmail.com Wed Apr 14 16:04:40 2010 From: shadow@gmail.com (Derrick Brashear) Date: Wed, 14 Apr 2010 11:04:40 -0400 Subject: [OpenAFS] Re: Ubik problem In-Reply-To: <201004141010.o3EAAOZr014266@ruuvi.it.helsinki.fi> References: <20100413131129.b790823c.adeason@sinenomine.net> <201004141010.o3EAAOZr014266@ruuvi.it.helsinki.fi> Message-ID: I'd suggest just using the IBM binary for the kaserver (and only the kaserver) in your OpenAFS installation (or better yet switching to krb5) On Wed, Apr 14, 2010 at 6:10 AM, Atro Tossavainen wrote: > OK, I have it again. =A0User reports inability to log in. > > $ kas -a dsakfksda > Administrator's (dsakfksda) Password: > ka> exa useraccount > examine: ticket contained unknown key version number getting information = for useraccount. > > So: > > $ udebug 128.214.88.114 7004 -long > Host's addresses are: 128.214.88.114 10.0.0.3 172.16.0.1 172.17.0.1 > 172.18.0.1 > Host's 128.214.88.114 time is Wed Apr 14 13:01:35 2010 > Local time is Wed Apr 14 13:01:35 2010 (time differential 0 secs) > Last yes vote for 128.214.58.174 was 14 secs ago (sync site); > Last vote started 13 secs ago (at Wed Apr 14 13:01:22 2010) > Local db version is 1271074432.4 > I am not sync site > Lowest host 128.214.58.174 was set 14 secs ago > Sync host 128.214.58.174 was set 14 secs ago > Sync site's db version is 1271074432.4 > 0 locked pages, 0 of them for write > > Server (128.214.58.174): (db 0.0) > last vote rcvd 165054 secs ago (at Mon Apr 12 15:10:41 2010), > last beacon sent 165054 secs ago (at Mon Apr 12 15:10:41 2010), last > vote was no > dbcurrent=3D0, up=3D1 beaconSince=3D1 > > > $ udebug 128.214.58.174 7004 -long > Host's addresses are: 128.214.58.174 > Host's 128.214.58.174 time is Wed Apr 14 13:01:50 2010 > Local time is Wed Apr 14 13:01:54 2010 (time differential 4 secs) > Last yes vote for 128.214.58.174 was 12 secs ago (sync site); > Last vote started 12 secs ago (at Wed Apr 14 13:01:42 2010) > Local db version is 1271074432.4 > I am sync site until 47 secs from now (at Wed Apr 14 13:02:41 2010) (2 > servers) > Recovery state 1f > Sync site's db version is 1271074432.4 > 0 locked pages, 0 of them for write > Last time a new db version was labelled was: > 164878 secs ago (at Mon Apr 12 15:13:56 2010) > > Server (128.214.88.114 10.0.0.3 172.16.0.1 172.17.0.1 172.18.0.1): (db > 1271074432.4) > last vote rcvd -3 secs ago (at Wed Apr 14 13:01:57 2010), > last beacon sent -3 secs ago (at Wed Apr 14 13:01:57 2010), last > vote was yes > dbcurrent=3D1, up=3D1 beaconSince=3D1 > > > Nothing obvious - at least to my untrained eye. > > Using kas specifically against 128.214.58.174 (the sunx86_510 OpenAFS > host) reproduces the error with this account. > > Using kas specifically against 128.214.88.114 (the sun4x_58 IBM AFS > host) shows correct information, however. > > bos restart 128.214.58.174 kaserver made the problem go away. > > There is no indication of anything unusual in the AuthLog of 128.214.58.1= 74. > > All pointers welcome. > > -- > Atro Tossavainen (Mr.) =A0 =A0 =A0 =A0 =A0 =A0 =A0 / The Institute of Bio= technology at > Systems Analyst, Techno-Amish & =A0 =A0 / the University of Helsinki, Fin= land, > +358-9-19158939 =A0UNIX Dinosaur =A0 =A0 / employs me, but my opinions ar= e my own. > < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHM= ENTS > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info > --=20 Derrick From jaltman@secure-endpoints.com Wed Apr 14 16:23:17 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Wed, 14 Apr 2010 11:23:17 -0400 Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: References: <4BC47100.1030802@secure-endpoints.com> <4BC4797B.3070202@email.unc.edu> <6A5BB6C1-955E-4740-8CDE-FB9CD7663BD0@umich.edu> <4BC4E1FF.5050305@secure-endpoints.com> Message-ID: <4BC5DDE5.3020703@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms000805090504050000090208 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/14/2010 10:51 AM, Steve Simmons wrote: >=20 > On Apr 13, 2010, at 5:28 PM, Jeffrey Altman wrote: >=20 >>> >>> I'm a long-time fan of having a switch that causes tools to dump thei= r data in an easy-to-machine-parse format. That isn't always doable, but = when it is, it's a big win. >> >> As Andrew pointed out in another reply in this thread, the -format >> switch is support to provide that but it fails to provide a consistent= >> (value - data) pair per line. >=20 > Exactly my point. We currently snarf off all that data nightly via scri= pt that parses the output from vos e -format. It works but was a pain. >=20 > Note, tho, that some data doesn't adapt well to single-line output. For= example,=20 >=20 > just doesn't map well to single-line. We currently deal with this by cr= eating four records, each will all the data from the rest of the output a= nd the specifics of the four entries above. >=20 > Steve Anyone want a -xml option? --------------ms000805090504050000090208 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MTQxNTIzMTdaMCMGCSqGSIb3DQEJBDEWBBQM6RyT +UATegYLd2oB+c/AAiDqPjBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBABJwHWePWNAkaLE7aB7Jtmf4i1sGm48PDIqm 6UatsbEm5AAugH0iEaAXXJZPWh2SSLlNDmwkKiOPXhr0iqnTKTLYsoPfhGKjE47aNEmJ2sVD iDst3alctOFjOfqAS5Vu5iOsylweb+Ux9Vpt42zskkxq/3lxLXSveXgXxlEckeyRi05w2pDw YSDBdLD8oFulS6iajAgzNnMQ4iuhb2GsPaUL1QTwPhyDBxxR3c/fTIxbIlnIc4IXkVgFUWAx 7Q82/idv/bkUVfJtkqY9UqMj7sCA2jUDPAwYMCaH4DkKdH1VEu1MiBxklokzMnp91biwd2OU 003rRtzb5N5Vfs7IDDIAAAAAAAA= --------------ms000805090504050000090208-- From shadow@gmail.com Wed Apr 14 16:37:33 2010 From: shadow@gmail.com (Derrick Brashear) Date: Wed, 14 Apr 2010 11:37:33 -0400 Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: <4BC5DDE5.3020703@secure-endpoints.com> References: <4BC47100.1030802@secure-endpoints.com> <4BC4797B.3070202@email.unc.edu> <6A5BB6C1-955E-4740-8CDE-FB9CD7663BD0@umich.edu> <4BC4E1FF.5050305@secure-endpoints.com> <4BC5DDE5.3020703@secure-endpoints.com> Message-ID: On Wed, Apr 14, 2010 at 11:23 AM, Jeffrey Altman wrote: > On 4/14/2010 10:51 AM, Steve Simmons wrote: >> >> On Apr 13, 2010, at 5:28 PM, Jeffrey Altman wrote: >> >>>> >>>> I'm a long-time fan of having a switch that causes tools to dump their data in an easy-to-machine-parse format. That isn't always doable, but when it is, it's a big win. >>> >>> As Andrew pointed out in another reply in this thread, the -format >>> switch is support to provide that but it fails to provide a consistent >>> (value - data) pair per line. >> >> Exactly my point. We currently snarf off all that data nightly via script that parses the output from vos e -format. It works but was a pain. >> >> Note, tho, that some data doesn't adapt well to single-line output. For example, >> >> just doesn't map well to single-line. We currently deal with this by creating four records, each will all the data from the rest of the output and the specifics of the four entries above. >> >> Steve > > Anyone want a -xml option? didn't we already have a patch for that in RT? -- Derrick From phalenor@gmail.com Wed Apr 14 16:50:53 2010 From: phalenor@gmail.com (Andy Cobaugh) Date: Wed, 14 Apr 2010 11:50:53 -0400 (EDT) Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: <4BC5DDE5.3020703@secure-endpoints.com> References: <4BC47100.1030802@secure-endpoints.com> <4BC4797B.3070202@email.unc.edu> <6A5BB6C1-955E-4740-8CDE-FB9CD7663BD0@umich.edu> <4BC4E1FF.5050305@secure-endpoints.com> <4BC5DDE5.3020703@secure-endpoints.com> Message-ID: On 2010-04-14 at 11:23, Jeffrey Altman ( jaltman@secure-endpoints.com ) said: > On 4/14/2010 10:51 AM, Steve Simmons wrote: >> >> On Apr 13, 2010, at 5:28 PM, Jeffrey Altman wrote: >> >>>> >>>> I'm a long-time fan of having a switch that causes tools to dump their data in an easy-to-machine-parse format. That isn't always doable, but when it is, it's a big win. >>> >>> As Andrew pointed out in another reply in this thread, the -format >>> switch is support to provide that but it fails to provide a consistent >>> (value - data) pair per line. >> >> Exactly my point. We currently snarf off all that data nightly via script that parses the output from vos e -format. It works but was a pain. >> >> Note, tho, that some data doesn't adapt well to single-line output. For example, >> >> just doesn't map well to single-line. We currently deal with this by creating four records, each will all the data from the rest of the output and the specifics of the four entries above. >> >> Steve > > Anyone want a -xml option? Yes, please. As much as I am not a fan of XML, it would make some of our lives easier for those of us using languages that include xml parsers. --andy From shadow@gmail.com Wed Apr 14 17:01:02 2010 From: shadow@gmail.com (Derrick Brashear) Date: Wed, 14 Apr 2010 12:01:02 -0400 Subject: [OpenAFS] A call to potential GSOC students: Modifying the output of vos commands to include server UUIDs Message-ID: Hey GSoC candidates! here's a simple project for you. vos examine already includes a "-format" switch to display a fixed, parseable format. add a "-xml" switch, and output in xml! Everything you need to change is in src/volser (vos.c and vsprocs.c). Ideally you won't require an external library to do this, but instead can just output xml directly, as we are unlikely to have any given xml library on all supported platforms. On Wed, Apr 14, 2010 at 11:50 AM, Andy Cobaugh wrote: > On 2010-04-14 at 11:23, Jeffrey Altman ( jaltman@secure-endpoints.com ) > said: >> >> On 4/14/2010 10:51 AM, Steve Simmons wrote: >>> >>> On Apr 13, 2010, at 5:28 PM, Jeffrey Altman wrote: >>> >>>>> >>>>> I'm a long-time fan of having a switch that causes tools to dump their >>>>> data in an easy-to-machine-parse format. That isn't always doable, but when >>>>> it is, it's a big win. >>>> >>>> As Andrew pointed out in another reply in this thread, the -format >>>> switch is support to provide that but it fails to provide a consistent >>>> (value - data) pair per line. >>> >>> Exactly my point. We currently snarf off all that data nightly via script >>> that parses the output from vos e -format. It works but was a pain. >>> >>> Note, tho, that some data doesn't adapt well to single-line output. For >>> example, >>> >>> just doesn't map well to single-line. We currently deal with this by >>> creating four records, each will all the data from the rest of the output >>> and the specifics of the four entries above. >>> >>> Steve >> >> Anyone want a -xml option? > > Yes, please. As much as I am not a fan of XML, it would make some of our > lives easier for those of us using languages that include xml parsers. > > --andy > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info > -- Derrick From fbo2@gmx.net Wed Apr 14 18:21:27 2010 From: fbo2@gmx.net (Frank Burkhardt) Date: Wed, 14 Apr 2010 19:21:27 +0200 Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: <4BC5DDE5.3020703@secure-endpoints.com> References: <4BC47100.1030802@secure-endpoints.com> <4BC4797B.3070202@email.unc.edu> <6A5BB6C1-955E-4740-8CDE-FB9CD7663BD0@umich.edu> <4BC4E1FF.5050305@secure-endpoints.com> <4BC5DDE5.3020703@secure-endpoints.com> Message-ID: <20100414172127.GA18471@postman.alpha> Hi, On Wed, Apr 14, 2010 at 11:23:17AM -0400, Jeffrey Altman wrote: [snip] > >>> I'm a long-time fan of having a switch that causes tools to dump their > >>> data in an easy-to-machine-parse format. That isn't always doable, but > >>> when it is, it's a big win. [snip] > Anyone want a -xml option? print "Yes - me." x $very_often; Especially for listvol it would be very helpful. Best, Frank From scs@umich.edu Wed Apr 14 18:52:17 2010 From: scs@umich.edu (Steve Simmons) Date: Wed, 14 Apr 2010 13:52:17 -0400 Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: <4BC5DDE5.3020703@secure-endpoints.com> References: <4BC47100.1030802@secure-endpoints.com> <4BC4797B.3070202@email.unc.edu> <6A5BB6C1-955E-4740-8CDE-FB9CD7663BD0@umich.edu> <4BC4E1FF.5050305@secure-endpoints.com> <4BC5DDE5.3020703@secure-endpoints.com> Message-ID: <0BBD85D4-1918-450C-9226-4E162143424C@umich.edu> On Apr 14, 2010, at 11:23 AM, Jeffrey Altman wrote: > On 4/14/2010 10:51 AM, Steve Simmons wrote: >>=20 >> On Apr 13, 2010, at 5:28 PM, Jeffrey Altman wrote: >>=20 >>>>=20 >>>> I'm a long-time fan of having a switch that causes tools to dump = their data in an easy-to-machine-parse format. That isn't always doable, = but when it is, it's a big win. >>>=20 >>> As Andrew pointed out in another reply in this thread, the -format >>> switch is support to provide that but it fails to provide a = consistent >>> (value - data) pair per line. >>=20 >> Exactly my point. We currently snarf off all that data nightly via = script that parses the output from vos e -format. It works but was a = pain. >>=20 >> Note, tho, that some data doesn't adapt well to single-line output. = For example,=20 >>=20 >> just doesn't map well to single-line. We currently deal with this by = creating four records, each will all the data from the rest of the = output and the specifics of the four entries above. >>=20 >> Steve >=20 > Anyone want a -xml option? Parsing xml in ad-hoc shell scripts is hell. On the other hand, all our = nightly data gathering scripts are in languages that have appropriate = xml parsers available. So yes, it would be useful. Or to be more = precise, it would *also* be useful. But comma-separated still has big = wins for some things. Steve= From atro.tossavainen+openafs@helsinki.fi Wed Apr 14 19:55:41 2010 From: atro.tossavainen+openafs@helsinki.fi (Atro Tossavainen) Date: Wed, 14 Apr 2010 21:55:41 +0300 (EEST) Subject: [OpenAFS] Re: Ubik problem In-Reply-To: Message-ID: <201004141855.o3EItfu4012245@ruuvi.it.helsinki.fi> Derrick, > I'd suggest just using the IBM binary for the kaserver (and only the > kaserver) in your OpenAFS installation That's an interesting thought, but unfortunately it's nowhere near an option. sunx86_ is quite simply not a supported platform for IBM AFS at all, even at 3.6 Patch 19 (August 2009). > (or better yet switching to krb5) Yes, I plan to do that. Eventually. At the moment, I have a number of things that I need to change and I'd like to minimise the amount of simultaneous changes. -- Atro Tossavainen (Mr.) / The Institute of Biotechnology at Systems Analyst, Techno-Amish & / the University of Helsinki, Finland, +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own. < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS From jason@rampaginggeek.com Wed Apr 14 23:30:42 2010 From: jason@rampaginggeek.com (Jason Edgecombe) Date: Wed, 14 Apr 2010 18:30:42 -0400 Subject: [OpenAFS] OS X, AFS Home Directories and SSH/Unix Permissions In-Reply-To: References: <393853E2-C3D1-4F6B-854C-ED0E1D06094D@cs.wisc.edu> Message-ID: <4BC64212.2010505@rampaginggeek.com> Derrick Brashear wrote: > On Tue, Apr 13, 2010 at 4:59 PM, Jacob Ela wrote: > >> Greetings All, >> >> I've been looking for some information on this because someone else has probably run into a similar issue, but I haven't found much that is recent or pointed towards solving the problem - though I've found some old email that suggests where this originates from... >> >> I've got a Mac Mini lab running OSX 10.6.2 and OpenAFS 1.4.11 (but also have seen this on a MacBook running 10.6.3 and 1.5.73.3). User's home directories live in AFS, and users get Kerberos/AFS credentials at login. >> >> I'm seeing on the Macs that all the unix file permissions on files in AFS are shown as 666, and from the old emails I've found I'm just guessing that this is to make AFS ACL's play nicely with the Finder (or rather the other way around). >> >> This has the unfortunate side effect that my users can't use SSH on the Macs, as the reported permissions on their ~/.ssh/config file suggest it is group and world writable. This causes SSH to error out when a user attempts to connect to another computer because of insecure config file permissions. Trying to chmod the file from a Mac doesn't change the unix permissions as they are reported to the Mac, though Linux hosts can see these new permissions. >> >> Has anyone run into something like this? Is there a way to change the permissions AFS reports to OSX, or is there a work around I'm failing to see? >> > > Check out the RealModes setting. Edit > /var/db/openafs/etc/config/settings.plist, and rerun > /var/db/openafs/etc/config/afssettings as root. > > > Is this documented somewhere? Jason From haba@kth.se Thu Apr 15 05:07:12 2010 From: haba@kth.se (Harald Barth) Date: Thu, 15 Apr 2010 06:07:12 +0200 (CEST) Subject: [OpenAFS] Re: Ubik problem In-Reply-To: <201004141855.o3EItfu4012245@ruuvi.it.helsinki.fi> References: <201004141855.o3EItfu4012245@ruuvi.it.helsinki.fi> Message-ID: <20100415.060712.10863420.haba@habanero.pdc.kth.se> > > I'd suggest just using the IBM binary for the kaserver (and only the > > kaserver) in your OpenAFS installation > > That's an interesting thought, but unfortunately it's nowhere near > an option. sunx86_ is quite simply not a supported platform for > IBM AFS at all, even at 3.6 Patch 19 (August 2009). "It's dead Jim." If you really want to run kaserver in 2010, you'll have to do it on hardware matching the age of the software, say an Sun SS10. It's not like that there hasn't been an upgrade path to krb5 for years. Harald. From fcombernous@kezia.com Thu Apr 15 08:24:38 2010 From: fcombernous@kezia.com (Fabien COMBERNOUS) Date: Thu, 15 Apr 2010 09:24:38 +0200 Subject: [OpenAFS] fix about info.numServers ? Message-ID: <4BC6BF36.5060106@kezia.com> Hi, I'm setting up an AFS cell with MacOSX. My first server of the cell is up and running. I started to setup an additional host. Unfortunatly, during this setup, i killed the fileserver process with the kill command. And now the bosserver think that a fileserver is running i think. I get this log in FileLog : Thu Apr 15 09:18:57 2010 File server starting Thu Apr 15 09:18:57 2010 Failed to increase open file limit, using default Thu Apr 15 09:18:57 2010 vl_Initialize: info.numServers=26052 (> MAXSERVERS=20) Can you provide help to fix this issue. Best regards, -- *Fabien COMBERNOUS* /unix system engineer/ www.kezia.com *Tel: +33 (0) 467 992 986* Kezia Group From rtb@pclella.cern.ch Thu Apr 15 09:13:53 2010 From: rtb@pclella.cern.ch (Rainer Toebbicke) Date: Thu, 15 Apr 2010 10:13:53 +0200 Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: References: <4BC47100.1030802@secure-endpoints.com> <4BC4797B.3070202@email.unc.edu> <6A5BB6C1-955E-4740-8CDE-FB9CD7663BD0@umich.edu> <4BC4E1FF.5050305@secure-endpoints.com> <4BC5DDE5.3020703@secure-endpoints.com> Message-ID: <4BC6CAC1.3000105@pclella.cern.ch> Andy Cobaugh schrieb: >> >> Anyone want a -xml option? > I don't care as long as that is taken as a "cherry on the icing" option, not as a pretext to abandon improving normal vos output. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rainer Toebbicke European Laboratory for Particle Physics(CERN) - Geneva, Switzerland Phone: +41 22 767 8985 Fax: +41 22 767 7155 From fcombernous@kezia.com Thu Apr 15 09:27:10 2010 From: fcombernous@kezia.com (Fabien COMBERNOUS) Date: Thu, 15 Apr 2010 10:27:10 +0200 Subject: [OpenAFS] fix about info.numServers ? In-Reply-To: <4BC6BF36.5060106@kezia.com> References: <4BC6BF36.5060106@kezia.com> Message-ID: <4BC6CDDE.4010109@kezia.com> Fabien COMBERNOUS wrote: > Hi, > > I'm setting up an AFS cell with MacOSX. My first server of the cell is > up and running. I started to setup an additional host. Unfortunatly, > during this setup, i killed the fileserver process with the kill > command. And now the bosserver think that a fileserver is running i > think. I get this log in FileLog : > > Thu Apr 15 09:18:57 2010 File server starting > Thu Apr 15 09:18:57 2010 Failed to increase open file limit, using > default > Thu Apr 15 09:18:57 2010 vl_Initialize: info.numServers=26052 (> > MAXSERVERS=20) > > Can you provide help to fix this issue. > > Best regards, I solved the issue by reinstalling the afs package. For the archive: Be carefull, the uninstall script does not work. I simply moved /Library/OpenAFS out of this path and rebooted. -- *Fabien COMBERNOUS* /unix system engineer/ www.kezia.com *Tel: +33 (0) 467 992 986* Kezia Group From jaltman@secure-endpoints.com Thu Apr 15 13:50:45 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Thu, 15 Apr 2010 08:50:45 -0400 Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: <0BBD85D4-1918-450C-9226-4E162143424C@umich.edu> References: <4BC47100.1030802@secure-endpoints.com> <4BC4797B.3070202@email.unc.edu> <6A5BB6C1-955E-4740-8CDE-FB9CD7663BD0@umich.edu> <4BC4E1FF.5050305@secure-endpoints.com> <4BC5DDE5.3020703@secure-endpoints.com> <0BBD85D4-1918-450C-9226-4E162143424C@umich.edu> Message-ID: <4BC70BA5.2020103@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms050000030000060507030409 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/14/2010 1:52 PM, Steve Simmons wrote: > Parsing xml in ad-hoc shell scripts is hell. On the other hand, all our= nightly data gathering scripts are in languages that have appropriate xm= l parsers available. So yes, it would be useful. Or to be more precise, i= t would *also* be useful. But comma-separated still has big wins for some= things. Since you have a good idea of how you would use a comma separated list, I would encourage you to propose a -csv option as well. Either provide a patch or at least detail a proposal of how the data should be represent= ed. --------------ms050000030000060507030409 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MTUxMjUwNDVaMCMGCSqGSIb3DQEJBDEWBBReTtm/ lPiD7SpU/QQI8+J/ZCbEdDBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAC2QEWfPXd9xlOXnrG24c+i6JyRSkeWT2tHB v6OEs/eocd9EVI3DOJifrT1g9EagXlwtVmR9wvFW4M4i9cHP2mHJ19A14P7fnvO8V/knh6mE yJoAVyTxU21SM8RlkMHPeYdNnlnl53EVfmAMCyza4521KtVXLc2UVs6COlZLPHSiP47ioqSX Zw5Y1o0sBCCzCffnTV+6+qijRzqrcG4B1ejU0q3hLee1P7E54zAES7e42obNzoMjL7fzvSFt U/chItpnHQdiXUEqKUXpMal+2ZyGmqbpniZXTCO5U2Jz/jrHkRjyX7Czc9OBEzWRkg9BBrqb 5p7IlpdjkC9kmNnpZrwAAAAAAAA= --------------ms050000030000060507030409-- From boyland@cs.uwm.edu Thu Apr 15 14:03:52 2010 From: boyland@cs.uwm.edu (John Tang Boyland) Date: Thu, 15 Apr 2010 08:03:52 -0500 Subject: [OpenAFS] Re: deadlock in OpenAFS 1.4.11 (Solaris 5.10) In-Reply-To: Your message of "Mon, 12 Apr 2010 10:14:40 EDT." Message-ID: <12345.1271336632@pabst.cs.uwm.edu> Update: After a week, I got up early enough to reboot the compute server when few people were on it. As part of this process I noticed that it had been set up with a memcache; I changed this back to a disk cache. The reason why I think this is a deadlock issue is that the processes make no progress after a week, and indeed are resistant to "kill -9" etc. Even shutting down the machine gets stuck -- it has to be power-cycled. But with a larger cache, it seems likely we won't see this behavior again. Thanks for the help, everyone. John Derrick Brashear wrote: ] you might as well reboot it. i suspect (and wondered before) if the ] real issue was not deadlock but that the machine simply went into a ] loop, and with a cache that small it's likely it did. not the best ] behavior, of course but not the most urgent thing to pursue at the ] moment. From adeason@sinenomine.net Thu Apr 15 15:08:44 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Thu, 15 Apr 2010 09:08:44 -0500 Subject: [OpenAFS] Re: Modifying the output of vos commands to include server UUIDs References: <4BC47100.1030802@secure-endpoints.com> <4BC4797B.3070202@email.unc.edu> <6A5BB6C1-955E-4740-8CDE-FB9CD7663BD0@umich.edu> <4BC4E1FF.5050305@secure-endpoints.com> <4BC5DDE5.3020703@secure-endpoints.com> <4BC6CAC1.3000105@pclella.cern.ch> Message-ID: <20100415090844.b642d734.adeason@sinenomine.net> On Thu, 15 Apr 2010 10:13:53 +0200 Rainer Toebbicke wrote: > Andy Cobaugh schrieb: > > >> > >> Anyone want a -xml option? > > > > I don't care as long as that is taken as a "cherry on the icing" > option, not as a pretext to abandon improving normal vos output. ...nor abandoning abstracting vsprocs-like functionality enough to just use it as a library. -- Andrew Deason adeason@sinenomine.net From bbense@slac.stanford.edu Thu Apr 15 16:20:17 2010 From: bbense@slac.stanford.edu (Booker Bense) Date: Thu, 15 Apr 2010 08:20:17 -0700 (PDT) Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: <4BC70BA5.2020103@secure-endpoints.com> References: <4BC47100.1030802@secure-endpoints.com> <4BC4797B.3070202@email.unc.edu> <6A5BB6C1-955E-4740-8CDE-FB9CD7663BD0@umich.edu> <4BC4E1FF.5050305@secure-endpoints.com> <4BC5DDE5.3020703@secure-endpoints.com> <0BBD85D4-1918-450C-9226-4E162143424C@umich.edu> <4BC70BA5.2020103@secure-endpoints.com> Message-ID: On Thu, 15 Apr 2010, Jeffrey Altman wrote: > On 4/14/2010 1:52 PM, Steve Simmons wrote: > >> Parsing xml in ad-hoc shell scripts is hell. On the other >> hand, all our nightly data gathering scripts are in languages >> that have appropriate xml parsers available. So yes, it would >> be useful. Or to be more precise, it would *also* be useful. >> But comma-separated still has big wins for some things. > YAML might be a reasonable compromise if there's only the tuit's to get one new option. _ Booker C. Bense From sxw@inf.ed.ac.uk Thu Apr 15 16:25:16 2010 From: sxw@inf.ed.ac.uk (Simon Wilkinson) Date: Thu, 15 Apr 2010 16:25:16 +0100 Subject: [OpenAFS] Modifying the output of vos commands to include server UUIDs In-Reply-To: References: <4BC47100.1030802@secure-endpoints.com> <4BC4797B.3070202@email.unc.edu> <6A5BB6C1-955E-4740-8CDE-FB9CD7663BD0@umich.edu> <4BC4E1FF.5050305@secure-endpoints.com> <4BC5DDE5.3020703@secure-endpoints.com> <0BBD85D4-1918-450C-9226-4E162143424C@umich.edu> <4BC70BA5.2020103@secure-endpoints.com> Message-ID: <0C07D74C-61F9-4E98-9817-E57F7363A193@inf.ed.ac.uk> On 15 Apr 2010, at 16:20, Booker Bense wrote: >=20 > YAML might be a reasonable compromise if there's only the tuit's > to get one new option. I suspect that there aren't the tuits for any new options. If those = expressing a desire for csv, xml, yaml, etc. want any of them, I'm sure = patches would be welcome... S. From stephen@physics.unc.edu Thu Apr 15 20:37:02 2010 From: stephen@physics.unc.edu (Stephen Joyce) Date: Thu, 15 Apr 2010 15:37:02 -0400 (EDT) Subject: [OpenAFS] bos -localauth not working Message-ID: I just added a new key to the KeyFile on my db and file servers. This key is for my campus's central krb5 realm. Everything seems to be functioning normally regarding tickets and tokens. I can kinit and aklog using tickets from the foreign krb5 realm and manipulate files and folders in my cell. However when I tried to use the -localauth flag to bos to restart server processes, it no longer works. It does work if I have tokens rather than using -localauth. Everything else appears to be working fine, but I'd like to recover the ability to use -localauth if at all possible. Errors I get: (no tokens, but I am root): # bos restart fs5 -all -localauth bos: failed to restart srevers (ticket contained unknown key version number) # kinit user/admin (valid password entered) # aklog # bos restart fs5 -all (success) I've double-checked the new kvno is as expected, and have no problems on the clients. So far the only symptom is bos. What could I have missed? Servers are OpenAFS 1.4.5 on Linux (yes, I know it's old. Upgrades are planned, but not *right now*). Cheers, Stephen From shadow@gmail.com Thu Apr 15 20:39:43 2010 From: shadow@gmail.com (Derrick Brashear) Date: Thu, 15 Apr 2010 15:39:43 -0400 Subject: [OpenAFS] bos -localauth not working In-Reply-To: References: Message-ID: does localauth work after a bosserver restart? On Thu, Apr 15, 2010 at 3:37 PM, Stephen Joyce wrote: > I just added a new key to the KeyFile on my db and file servers. This key is > for my campus's central krb5 realm. > > Everything seems to be functioning normally regarding tickets and tokens. I > can kinit and aklog using tickets from the foreign krb5 realm and manipulate > files and folders in my cell. > > However when I tried to use the -localauth flag to bos to restart server > processes, it no longer works. It does work if I have tokens rather than > using -localauth. > > Everything else appears to be working fine, but I'd like to recover the > ability to use -localauth if at all possible. Errors I get: > > (no tokens, but I am root): > # bos restart fs5 -all -localauth > bos: failed to restart srevers (ticket contained unknown key version number) > > # kinit user/admin > (valid password entered) > # aklog > # bos restart fs5 -all > (success) > > I've double-checked the new kvno is as expected, and have no problems on the > clients. So far the only symptom is bos. > > What could I have missed? > > Servers are OpenAFS 1.4.5 on Linux (yes, I know it's old. Upgrades are > planned, but not *right now*). > > Cheers, Stephen > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info > -- Derrick From stephen@physics.unc.edu Thu Apr 15 20:46:07 2010 From: stephen@physics.unc.edu (Stephen Joyce) Date: Thu, 15 Apr 2010 15:46:07 -0400 (EDT) Subject: [OpenAFS] bos -localauth not working In-Reply-To: References: Message-ID: On Thu, 15 Apr 2010, Derrick Brashear wrote: > does localauth work after a bosserver restart? Yes... Glad it was something simple! > On Thu, Apr 15, 2010 at 3:37 PM, Stephen Joyce wrote: >> I just added a new key to the KeyFile on my db and file servers. This key is >> for my campus's central krb5 realm. >> >> Everything seems to be functioning normally regarding tickets and tokens. I >> can kinit and aklog using tickets from the foreign krb5 realm and manipulate >> files and folders in my cell. >> >> However when I tried to use the -localauth flag to bos to restart server >> processes, it no longer works. It does work if I have tokens rather than >> using -localauth. >> >> Everything else appears to be working fine, but I'd like to recover the >> ability to use -localauth if at all possible. Errors I get: >> >> (no tokens, but I am root): >> # bos restart fs5 -all -localauth >> bos: failed to restart srevers (ticket contained unknown key version number) >> >> # kinit user/admin >> (valid password entered) >> # aklog >> # bos restart fs5 -all >> (success) >> >> I've double-checked the new kvno is as expected, and have no problems on the >> clients. So far the only symptom is bos. >> >> What could I have missed? >> >> Servers are OpenAFS 1.4.5 on Linux (yes, I know it's old. Upgrades are >> planned, but not *right now*). >> >> Cheers, Stephen >> _______________________________________________ >> OpenAFS-info mailing list >> OpenAFS-info@openafs.org >> https://lists.openafs.org/mailman/listinfo/openafs-info >> > > > > -- > Derrick > > > -- > > From bampfamd@berkeley.edu Thu Apr 15 22:18:56 2010 From: bampfamd@berkeley.edu (bampfamd@berkeley.edu) Date: Thu, 15 Apr 2010 14:18:56 -0700 Subject: [OpenAFS] openAFS 1.4.12 Kernel Panic on restart? (mac) Message-ID: ------=_20100415141856_60636 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Sorry, I am unfamiliar with using these scripts to decode the panic logs, but I have included both an attachment and a text copy of the log here. If you could help it would be greatly appreciated! thanks! --------------------------------------------------------------------- Thu Apr 15 13:48:03 2010 panic(cpu 1 caller 0x001AB0FE): Kernel trap at 0x3177b411, type 14=page fault, registers: CR0: 0x8001003b, CR2: 0x3177b411, CR3: 0x010e4000, CR4: 0x000006e0 EAX: 0x00000023, EBX: 0x00000000, ECX: 0x039cb000, EDX: 0x02f5b100 CR2: 0x3177b411, EBP: 0x21143f4c, ESI: 0x039cb000, EDI: 0x210dbb94 EFL: 0x00010216, EIP: 0x3177b411, CS: 0x00000004, DS: 0x0000000c Error code: 0x00000010 Backtrace (CPU 1), Frame : Return Address (4 potential args on stack) 0x21143d88 : 0x12b4c6 (0x45f91c 0x21143dbc 0x13355c 0x0) 0x21143dd8 : 0x1ab0fe (0x469a98 0x3177b411 0xe 0x469248) 0x21143eb8 : 0x1a1713 (0x21143ecc 0x21143f4c 0x3177b411 0xe) 0x21143ec4 : 0x3177b411 (0xe 0x380048 0x8e62000c 0xc) 0x21143f4c : 0x3177aec0 (0x3179d7c0 0x1f4 0x0 0x10624dd3) 0x21143f88 : 0x3176acd8 (0x1f4 0x0 0x0 0x0) 0x21143fac : 0x3178007e (0x317978d0 0x3177fb18 0x2b25018 0x210dbb94) 0x21143fc8 : 0x1a14fc (0x210dbb94 0x0 0x1a40b5 0x39cce40) Backtrace terminated-invalid frame pointer 0 BSD process name corresponding to current thread: kernel_task Mac OS version: 9L31a Kernel version: Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 System model name: iMac4,2 (Mac-F4218EC8) System uptime in nanoseconds: 10331785353733 unloaded kexts: org.openafs.filesystems.afs 1.4.12 - last unloaded 10331531078921 loaded kexts: org.openafs.filesystems.afs 1.4.12 - last loaded 20825984843 com.apple.filesystems.autofs 2.0.2 com.apple.driver.AppleHDAPlatformDriver 1.7.1a2 com.apple.driver.AppleHDAHardwareConfigDriver 1.7.1a2 com.apple.driver.AppleHDA 1.7.1a2 com.apple.driver.AppleUpstreamUserClient 2.7.5 com.apple.driver.AppleIntelGMA950 5.4.8 com.apple.driver.AppleGraphicsControl 2.8.15 com.apple.driver.AppleIntelGMAX3100 5.4.8 com.apple.Dont_Steal_Mac_OS_X 6.0.3 com.apple.driver.AppleIntelIntegratedFramebuffer 5.4.8 com.apple.driver.AppleUSBOpticalMouse 3.2.0 com.apple.driver.AppleHDAController 1.7.1a2 com.apple.iokit.IOFireWireIP 1.7.7 com.apple.driver.AppleIRController 113 com.apple.driver.AudioIPCDriver 1.0.6 com.apple.driver.ACPI_SMC_PlatformPlugin 3.4.0a17 com.apple.driver.AppleLPC 1.3.1 com.apple.driver.AppleBacklight 1.6.0 com.apple.driver.AppleTyMCEDriver 1.0.0d28 com.apple.driver.AppleUSBMergeNub 3.5.2 com.apple.driver.USBCameraFirmwareLoader 1.0.9 com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.1.1 com.apple.iokit.SCSITaskUserClient 2.1.1 com.apple.driver.XsanFilter 2.7.91 com.apple.iokit.IOATAPIProtocolTransport 1.5.3 com.apple.iokit.IOAHCIBlockStorage 1.2.2 com.apple.driver.AppleUSBHub 3.4.9 com.apple.iokit.IOUSBUserClient 3.5.2 com.apple.driver.AppleFWOHCI 3.9.7 com.apple.iokit.AppleYukon2 3.1.13b2 com.apple.driver.AirPortBrcm43xx 366.91.21 com.apple.driver.AppleAHCIPort 1.7.0 com.apple.driver.AppleIntelPIIXATA 2.0.1 com.apple.driver.AppleFileSystemDriver 1.1.0 com.apple.driver.AppleUSBEHCI 3.4.6 com.apple.driver.AppleUSBUHCI 3.5.2 com.apple.driver.AppleEFINVRAM 1.2.0 com.apple.driver.AppleRTC 1.2.3 com.apple.driver.AppleHPET 1.4 com.apple.driver.AppleACPIPCI 1.2.5 com.apple.driver.AppleACPIButtons 1.2.5 com.apple.driver.AppleSMBIOS 1.4 com.apple.driver.AppleACPIEC 1.2.5 com.apple.driver.AppleAPIC 1.4 com.apple.security.seatbelt 107.12 com.apple.nke.applicationfirewall 1.8.77 com.apple.security.TMSafetyNet 3 com.apple.driver.AppleIntelCPUPowerManagement 76.2.0 com.apple.driver.DiskImages 199 com.apple.BootCache 30.4 com.apple.driver.DspFuncLib 1.7.1a2 com.apple.iokit.IOHDAFamily 1.7.1a2 com.apple.iokit.IOAudioFamily 1.6.9fc5 com.apple.kext.OSvKernDSPLib 1.1 com.apple.driver.IOPlatformPluginFamily 3.4.0a17 com.apple.iokit.IONDRVSupport 1.7.3 com.apple.iokit.IOGraphicsFamily 1.7.3 com.apple.driver.AppleSMC 2.3.1d1 com.apple.iokit.IOUSBHIDDriver 3.4.6 com.apple.driver.AppleUSBComposite 3.2.0 com.apple.iokit.IOSCSIBlockCommandsDevice 2.1.1 com.apple.iokit.IOBDStorageFamily 1.5 com.apple.iokit.IODVDStorageFamily 1.5 com.apple.iokit.IOCDStorageFamily 1.5 com.apple.iokit.IOSCSIArchitectureModelFamily 2.1.1 com.apple.iokit.IOFireWireFamily 3.4.9 com.apple.iokit.IO80211Family 216.1 com.apple.iokit.IOAHCIFamily 1.5.0 com.apple.iokit.IOATAFamily 2.0.1 com.apple.iokit.IOUSBFamily 3.5.2 com.apple.iokit.IONetworkingFamily 1.6.1 com.apple.driver.AppleEFIRuntime 1.2.0 com.apple.iokit.IOSMBusFamily 1.1 com.apple.iokit.IOHIDFamily 1.5.5 com.apple.iokit.IOStorageFamily 1.5.6 com.apple.driver.AppleACPIPlatform 1.2.5 com.apple.iokit.IOACPIFamily 1.2.0 com.apple.iokit.IOPCIFamily 2.6 --------------------------------------------------------------------- > On Thu, Apr 8, 2010 at 6:19 PM, wrote: >> So i installed OpenAFS 1.4.12 on a Leopard Mac OS X computer earlier and >> tried running it (i had a slow afs loading issue earlier...but this >> version fixed that). Even though this version fixed that slow loading >> issue, I get the Kernel Panic message (the "You need to power down your >> computer...") every time I try to power down the computer/restart it. I >> assume that the kernel panic happens when the system is trying to >> unmount >> the AFS server...but as of right now, it happens every single time I >> turn >> off my computer. >> >> If the kernel panic log is needed I will post one up. But does anyone >> have >> any idea as of right now? > > a decoded panic log would be ideal, if you could. the decode-panic > sript should be able to help with that. > ------=_20100415141856_60636 Content-Type: application/octet-stream; name="2010-04-15-134803.panic" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="2010-04-15-134803.panic" VGh1IEFwciAxNSAxMzo0ODowMyAyMDEwCnBhbmljKGNwdSAxIGNhbGxlciAweDAwMUFCMEZFKTog S2VybmVsIHRyYXAgYXQgMHgzMTc3YjQxMSwgdHlwZSAxND1wYWdlIGZhdWx0LCByZWdpc3RlcnM6 CkNSMDogMHg4MDAxMDAzYiwgQ1IyOiAweDMxNzdiNDExLCBDUjM6IDB4MDEwZTQwMDAsIENSNDog MHgwMDAwMDZlMApFQVg6IDB4MDAwMDAwMjMsIEVCWDogMHgwMDAwMDAwMCwgRUNYOiAweDAzOWNi MDAwLCBFRFg6IDB4MDJmNWIxMDAKQ1IyOiAweDMxNzdiNDExLCBFQlA6IDB4MjExNDNmNGMsIEVT STogMHgwMzljYjAwMCwgRURJOiAweDIxMGRiYjk0CkVGTDogMHgwMDAxMDIxNiwgRUlQOiAweDMx NzdiNDExLCBDUzogIDB4MDAwMDAwMDQsIERTOiAgMHgwMDAwMDAwYwpFcnJvciBjb2RlOiAweDAw MDAwMDEwCgpCYWNrdHJhY2UgKENQVSAxKSwgRnJhbWUgOiBSZXR1cm4gQWRkcmVzcyAoNCBwb3Rl bnRpYWwgYXJncyBvbiBzdGFjaykKMHgyMTE0M2Q4OCA6IDB4MTJiNGM2ICgweDQ1ZjkxYyAweDIx MTQzZGJjIDB4MTMzNTVjIDB4MCkgCjB4MjExNDNkZDggOiAweDFhYjBmZSAoMHg0NjlhOTggMHgz MTc3YjQxMSAweGUgMHg0NjkyNDgpIAoweDIxMTQzZWI4IDogMHgxYTE3MTMgKDB4MjExNDNlY2Mg MHgyMTE0M2Y0YyAweDMxNzdiNDExIDB4ZSkgCjB4MjExNDNlYzQgOiAweDMxNzdiNDExICgweGUg MHgzODAwNDggMHg4ZTYyMDAwYyAweGMpIAoweDIxMTQzZjRjIDogMHgzMTc3YWVjMCAoMHgzMTc5 ZDdjMCAweDFmNCAweDAgMHgxMDYyNGRkMykgCjB4MjExNDNmODggOiAweDMxNzZhY2Q4ICgweDFm NCAweDAgMHgwIDB4MCkgCjB4MjExNDNmYWMgOiAweDMxNzgwMDdlICgweDMxNzk3OGQwIDB4MzE3 N2ZiMTggMHgyYjI1MDE4IDB4MjEwZGJiOTQpIAoweDIxMTQzZmM4IDogMHgxYTE0ZmMgKDB4MjEw ZGJiOTQgMHgwIDB4MWE0MGI1IDB4MzljY2U0MCkgCkJhY2t0cmFjZSB0ZXJtaW5hdGVkLWludmFs aWQgZnJhbWUgcG9pbnRlciAwCgpCU0QgcHJvY2VzcyBuYW1lIGNvcnJlc3BvbmRpbmcgdG8gY3Vy cmVudCB0aHJlYWQ6IGtlcm5lbF90YXNrCgpNYWMgT1MgdmVyc2lvbjoKOUwzMWEKCktlcm5lbCB2 ZXJzaW9uOgpEYXJ3aW4gS2VybmVsIFZlcnNpb24gOS44LjA6IFdlZCBKdWwgMTUgMTY6NTU6MDEg UERUIDIwMDk7IHJvb3Q6eG51LTEyMjguMTUuNH4xL1JFTEVBU0VfSTM4NgpTeXN0ZW0gbW9kZWwg bmFtZTogaU1hYzQsMiAoTWFjLUY0MjE4RUM4KQoKU3lzdGVtIHVwdGltZSBpbiBuYW5vc2Vjb25k czogMTAzMzE3ODUzNTM3MzMKdW5sb2FkZWQga2V4dHM6Cm9yZy5vcGVuYWZzLmZpbGVzeXN0ZW1z LmFmcwkxLjQuMTIgLSBsYXN0IHVubG9hZGVkIDEwMzMxNTMxMDc4OTIxCmxvYWRlZCBrZXh0czoK b3JnLm9wZW5hZnMuZmlsZXN5c3RlbXMuYWZzCTEuNC4xMiAtIGxhc3QgbG9hZGVkIDIwODI1OTg0 ODQzCmNvbS5hcHBsZS5maWxlc3lzdGVtcy5hdXRvZnMJMi4wLjIKY29tLmFwcGxlLmRyaXZlci5B cHBsZUhEQVBsYXRmb3JtRHJpdmVyCTEuNy4xYTIKY29tLmFwcGxlLmRyaXZlci5BcHBsZUhEQUhh cmR3YXJlQ29uZmlnRHJpdmVyCTEuNy4xYTIKY29tLmFwcGxlLmRyaXZlci5BcHBsZUhEQQkxLjcu MWEyCmNvbS5hcHBsZS5kcml2ZXIuQXBwbGVVcHN0cmVhbVVzZXJDbGllbnQJMi43LjUKY29tLmFw cGxlLmRyaXZlci5BcHBsZUludGVsR01BOTUwCTUuNC44CmNvbS5hcHBsZS5kcml2ZXIuQXBwbGVH cmFwaGljc0NvbnRyb2wJMi44LjE1CmNvbS5hcHBsZS5kcml2ZXIuQXBwbGVJbnRlbEdNQVgzMTAw CTUuNC44CmNvbS5hcHBsZS5Eb250X1N0ZWFsX01hY19PU19YCTYuMC4zCmNvbS5hcHBsZS5kcml2 ZXIuQXBwbGVJbnRlbEludGVncmF0ZWRGcmFtZWJ1ZmZlcgk1LjQuOApjb20uYXBwbGUuZHJpdmVy LkFwcGxlVVNCT3B0aWNhbE1vdXNlCTMuMi4wCmNvbS5hcHBsZS5kcml2ZXIuQXBwbGVIREFDb250 cm9sbGVyCTEuNy4xYTIKY29tLmFwcGxlLmlva2l0LklPRmlyZVdpcmVJUAkxLjcuNwpjb20uYXBw bGUuZHJpdmVyLkFwcGxlSVJDb250cm9sbGVyCTExMwpjb20uYXBwbGUuZHJpdmVyLkF1ZGlvSVBD RHJpdmVyCTEuMC42CmNvbS5hcHBsZS5kcml2ZXIuQUNQSV9TTUNfUGxhdGZvcm1QbHVnaW4JMy40 LjBhMTcKY29tLmFwcGxlLmRyaXZlci5BcHBsZUxQQwkxLjMuMQpjb20uYXBwbGUuZHJpdmVyLkFw cGxlQmFja2xpZ2h0CTEuNi4wCmNvbS5hcHBsZS5kcml2ZXIuQXBwbGVUeU1DRURyaXZlcgkxLjAu MGQyOApjb20uYXBwbGUuZHJpdmVyLkFwcGxlVVNCTWVyZ2VOdWIJMy41LjIKY29tLmFwcGxlLmRy aXZlci5VU0JDYW1lcmFGaXJtd2FyZUxvYWRlcgkxLjAuOQpjb20uYXBwbGUuaW9raXQuSU9TQ1NJ TXVsdGltZWRpYUNvbW1hbmRzRGV2aWNlCTIuMS4xCmNvbS5hcHBsZS5pb2tpdC5TQ1NJVGFza1Vz ZXJDbGllbnQJMi4xLjEKY29tLmFwcGxlLmRyaXZlci5Yc2FuRmlsdGVyCTIuNy45MQpjb20uYXBw bGUuaW9raXQuSU9BVEFQSVByb3RvY29sVHJhbnNwb3J0CTEuNS4zCmNvbS5hcHBsZS5pb2tpdC5J T0FIQ0lCbG9ja1N0b3JhZ2UJMS4yLjIKY29tLmFwcGxlLmRyaXZlci5BcHBsZVVTQkh1YgkzLjQu OQpjb20uYXBwbGUuaW9raXQuSU9VU0JVc2VyQ2xpZW50CTMuNS4yCmNvbS5hcHBsZS5kcml2ZXIu QXBwbGVGV09IQ0kJMy45LjcKY29tLmFwcGxlLmlva2l0LkFwcGxlWXVrb24yCTMuMS4xM2IyCmNv bS5hcHBsZS5kcml2ZXIuQWlyUG9ydEJyY200M3h4CTM2Ni45MS4yMQpjb20uYXBwbGUuZHJpdmVy LkFwcGxlQUhDSVBvcnQJMS43LjAKY29tLmFwcGxlLmRyaXZlci5BcHBsZUludGVsUElJWEFUQQky LjAuMQpjb20uYXBwbGUuZHJpdmVyLkFwcGxlRmlsZVN5c3RlbURyaXZlcgkxLjEuMApjb20uYXBw bGUuZHJpdmVyLkFwcGxlVVNCRUhDSQkzLjQuNgpjb20uYXBwbGUuZHJpdmVyLkFwcGxlVVNCVUhD SQkzLjUuMgpjb20uYXBwbGUuZHJpdmVyLkFwcGxlRUZJTlZSQU0JMS4yLjAKY29tLmFwcGxlLmRy aXZlci5BcHBsZVJUQwkxLjIuMwpjb20uYXBwbGUuZHJpdmVyLkFwcGxlSFBFVAkxLjQKY29tLmFw cGxlLmRyaXZlci5BcHBsZUFDUElQQ0kJMS4yLjUKY29tLmFwcGxlLmRyaXZlci5BcHBsZUFDUElC dXR0b25zCTEuMi41CmNvbS5hcHBsZS5kcml2ZXIuQXBwbGVTTUJJT1MJMS40CmNvbS5hcHBsZS5k cml2ZXIuQXBwbGVBQ1BJRUMJMS4yLjUKY29tLmFwcGxlLmRyaXZlci5BcHBsZUFQSUMJMS40CmNv bS5hcHBsZS5zZWN1cml0eS5zZWF0YmVsdAkxMDcuMTIKY29tLmFwcGxlLm5rZS5hcHBsaWNhdGlv bmZpcmV3YWxsCTEuOC43Nwpjb20uYXBwbGUuc2VjdXJpdHkuVE1TYWZldHlOZXQJMwpjb20uYXBw bGUuZHJpdmVyLkFwcGxlSW50ZWxDUFVQb3dlck1hbmFnZW1lbnQJNzYuMi4wCmNvbS5hcHBsZS5k cml2ZXIuRGlza0ltYWdlcwkxOTkKY29tLmFwcGxlLkJvb3RDYWNoZQkzMC40CmNvbS5hcHBsZS5k cml2ZXIuRHNwRnVuY0xpYgkxLjcuMWEyCmNvbS5hcHBsZS5pb2tpdC5JT0hEQUZhbWlseQkxLjcu MWEyCmNvbS5hcHBsZS5pb2tpdC5JT0F1ZGlvRmFtaWx5CTEuNi45ZmM1CmNvbS5hcHBsZS5rZXh0 Lk9Tdktlcm5EU1BMaWIJMS4xCmNvbS5hcHBsZS5kcml2ZXIuSU9QbGF0Zm9ybVBsdWdpbkZhbWls eQkzLjQuMGExNwpjb20uYXBwbGUuaW9raXQuSU9ORFJWU3VwcG9ydAkxLjcuMwpjb20uYXBwbGUu aW9raXQuSU9HcmFwaGljc0ZhbWlseQkxLjcuMwpjb20uYXBwbGUuZHJpdmVyLkFwcGxlU01DCTIu My4xZDEKY29tLmFwcGxlLmlva2l0LklPVVNCSElERHJpdmVyCTMuNC42CmNvbS5hcHBsZS5kcml2 ZXIuQXBwbGVVU0JDb21wb3NpdGUJMy4yLjAKY29tLmFwcGxlLmlva2l0LklPU0NTSUJsb2NrQ29t bWFuZHNEZXZpY2UJMi4xLjEKY29tLmFwcGxlLmlva2l0LklPQkRTdG9yYWdlRmFtaWx5CTEuNQpj b20uYXBwbGUuaW9raXQuSU9EVkRTdG9yYWdlRmFtaWx5CTEuNQpjb20uYXBwbGUuaW9raXQuSU9D RFN0b3JhZ2VGYW1pbHkJMS41CmNvbS5hcHBsZS5pb2tpdC5JT1NDU0lBcmNoaXRlY3R1cmVNb2Rl bEZhbWlseQkyLjEuMQpjb20uYXBwbGUuaW9raXQuSU9GaXJlV2lyZUZhbWlseQkzLjQuOQpjb20u YXBwbGUuaW9raXQuSU84MDIxMUZhbWlseQkyMTYuMQpjb20uYXBwbGUuaW9raXQuSU9BSENJRmFt aWx5CTEuNS4wCmNvbS5hcHBsZS5pb2tpdC5JT0FUQUZhbWlseQkyLjAuMQpjb20uYXBwbGUuaW9r aXQuSU9VU0JGYW1pbHkJMy41LjIKY29tLmFwcGxlLmlva2l0LklPTmV0d29ya2luZ0ZhbWlseQkx LjYuMQpjb20uYXBwbGUuZHJpdmVyLkFwcGxlRUZJUnVudGltZQkxLjIuMApjb20uYXBwbGUuaW9r aXQuSU9TTUJ1c0ZhbWlseQkxLjEKY29tLmFwcGxlLmlva2l0LklPSElERmFtaWx5CTEuNS41CmNv bS5hcHBsZS5pb2tpdC5JT1N0b3JhZ2VGYW1pbHkJMS41LjYKY29tLmFwcGxlLmRyaXZlci5BcHBs ZUFDUElQbGF0Zm9ybQkxLjIuNQpjb20uYXBwbGUuaW9raXQuSU9BQ1BJRmFtaWx5CTEuMi4wCmNv bS5hcHBsZS5pb2tpdC5JT1BDSUZhbWlseQkyLjYKCg== ------=_20100415141856_60636-- From tcreedon@easystreet.net Fri Apr 16 00:37:09 2010 From: tcreedon@easystreet.net (Ted Creedon) Date: Thu, 15 Apr 2010 16:37:09 -0700 Subject: [OpenAFS] Missing AFS Client tabs? Message-ID: --001636b2bc5532b73604844ef935 Content-Type: text/plain; charset=ISO-8859-1 OpenAFS for Windows 1.5.73:on Windows Server 2003 2 lock symbols appear in the system tray the "Drive Letters" and "Advanced" tabs are missing from the AFS Client popup. Thanks Tedc --001636b2bc5532b73604844ef935 Content-Type: text/html; charset=ISO-8859-1 OpenAFS for Windows 1.5.73:on Windows Server 2003

2 lock symbols appear in the system tray

the "Drive Letters" and "Advanced" tabs are missing from the AFS Client popup.

Thanks

Tedc


--001636b2bc5532b73604844ef935-- From jaltman@secure-endpoints.com Fri Apr 16 01:42:06 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Thu, 15 Apr 2010 20:42:06 -0400 Subject: [OpenAFS] Missing AFS Client tabs? In-Reply-To: References: Message-ID: <4BC7B25E.6000705@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms090101000609090803000108 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/15/2010 7:37 PM, Ted Creedon wrote: > OpenAFS for Windows 1.5.73:on Windows Server 2003 >=20 > 2 lock symbols appear in the system tray >=20 > the "Drive Letters" and "Advanced" tabs are missing from the AFS Client= > popup. >=20 > Thanks >=20 > Tedc >=20 >=20 The Drive Letters and Advanced tabs are not compatible with Vista and above. They have been removed. This is documented in the release notes and was discussed on this mailing list before the change was made. The two icons are the result of running both the AFS Authentication tool and Network Identity Manager. Please choose one. Network Identity Manager has an option to automatically disable the AFS Authentication Tool if that is your choice. Jeffrey Altman --------------ms090101000609090803000108 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MTYwMDQyMDZaMCMGCSqGSIb3DQEJBDEWBBQ5czuZ 5SUEqbcugYSXRIjWl/6X0TBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAJiQC9QHHarVJlTOb52Hz+q0olXT+x9hRXkC cvOcTHnGYvKiLJanSRT86rO76foUUb8MfXWpngWOSzr4soNb8eLuJBSX4UI0As6HsYrI/XqY gT625xaRfQgrd/fs6FCuOYVNWVTPXoFVo2YNpz1ffKjo4nSKN2zxzcxNc7gvJeRIeRE5VIN/ F0w7vA4JlSU6UnYeISd3qUh04N7EAE+u6AKCUV+GiayTWaoX1waJjORgMFZavV9hssJwSJ2M X1cZZFc5ERhVbqI66Bx7viRbTTHQQ+Pd0Jj/yp/fn1jyqCMMIO1d8MX3EqQhM7tQXvAr2B1e J5bBb7LVf5TCgPPo+QYAAAAAAAA= --------------ms090101000609090803000108-- From adeason@sinenomine.net Fri Apr 16 01:44:22 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Thu, 15 Apr 2010 19:44:22 -0500 Subject: [OpenAFS] Re: Ubik problem References: <201004141855.o3EItfu4012245@ruuvi.it.helsinki.fi> Message-ID: <20100415194422.b34491ec.adeason@sinenomine.net> On Wed, 14 Apr 2010 21:55:41 +0300 (EEST) Atro Tossavainen wrote: > Derrick, > > > I'd suggest just using the IBM binary for the kaserver (and only the > > kaserver) in your OpenAFS installation > > That's an interesting thought, but unfortunately it's nowhere near > an option. sunx86_ is quite simply not a supported platform for > IBM AFS at all, even at 3.6 Patch 19 (August 2009). Older OpenAFS releases could be another option, but I don't know how useful of an answer that is. I'm not sure what could have caused that, so I don't have a particular range in mind; maybe just earlier 1.4... 1.4.9? 1.4.2? That's not a good solution, of course, but I don't know how much enthusiasm you're going to get for debugging kas issues in one's spare time... -- Andrew Deason adeason@sinenomine.net From rra@stanford.edu Fri Apr 16 02:13:28 2010 From: rra@stanford.edu (Russ Allbery) Date: Thu, 15 Apr 2010 18:13:28 -0700 Subject: [OpenAFS] Re: Ubik problem In-Reply-To: <20100415194422.b34491ec.adeason@sinenomine.net> (Andrew Deason's message of "Thu, 15 Apr 2010 19:44:22 -0500") References: <201004141855.o3EItfu4012245@ruuvi.it.helsinki.fi> <20100415194422.b34491ec.adeason@sinenomine.net> Message-ID: <87pr20nqrr.fsf@windlord.stanford.edu> Andrew Deason writes: > Atro Tossavainen wrote: >> Derrick, >> >> > I'd suggest just using the IBM binary for the kaserver (and only the >> > kaserver) in your OpenAFS installation >> >> That's an interesting thought, but unfortunately it's nowhere near >> an option. sunx86_ is quite simply not a supported platform for >> IBM AFS at all, even at 3.6 Patch 19 (August 2009). > Older OpenAFS releases could be another option, but I don't know how > useful of an answer that is. I'm not sure what could have caused that, > so I don't have a particular range in mind; maybe just earlier 1.4... > 1.4.9? 1.4.2? We were successfully running a 1.2.x version of kaserver on SPARC Solaris, and upgrading to 1.4.2 on Linux failed (albeit with different symptoms; it would just stop successfully giving out tickets for a while and then come back, regularly), so we stuck with 1.2.x on SPARC until we turned it off entirely. -- Russ Allbery (rra@stanford.edu) From shadow@gmail.com Fri Apr 16 04:02:33 2010 From: shadow@gmail.com (Derrick Brashear) Date: Thu, 15 Apr 2010 23:02:33 -0400 Subject: [OpenAFS] Re: Ubik problem In-Reply-To: <87pr20nqrr.fsf@windlord.stanford.edu> References: <201004141855.o3EItfu4012245@ruuvi.it.helsinki.fi> <20100415194422.b34491ec.adeason@sinenomine.net> <87pr20nqrr.fsf@windlord.stanford.edu> Message-ID: On Thu, Apr 15, 2010 at 9:13 PM, Russ Allbery wrote: > Andrew Deason writes: >> Atro Tossavainen wrote: > >>> Derrick, >>> >>> > I'd suggest just using the IBM binary for the kaserver (and only the >>> > kaserver) in your OpenAFS installation >>> >>> That's an interesting thought, but unfortunately it's nowhere near >>> an option. =A0sunx86_ is quite simply not a supported platform for >>> IBM AFS at all, even at 3.6 Patch 19 (August 2009). > >> Older OpenAFS releases could be another option, but I don't know how >> useful of an answer that is. I'm not sure what could have caused that, >> so I don't have a particular range in mind; maybe just earlier 1.4... >> 1.4.9? 1.4.2? > > We were successfully running a 1.2.x version of kaserver on SPARC Solaris= , > and upgrading to 1.4.2 on Linux failed (albeit with different symptoms; i= t > would just stop successfully giving out tickets for a while and then come > back, regularly), so we stuck with 1.2.x on SPARC until we turned it off > entirely. I'm pretty sure it "broke" between 1.2.11 and 1.4.1. --=20 Derrick From fcombernous@kezia.com Fri Apr 16 08:08:24 2010 From: fcombernous@kezia.com (Fabien COMBERNOUS) Date: Fri, 16 Apr 2010 09:08:24 +0200 Subject: [OpenAFS] released volume, deleted Message-ID: <4BC80CE8.80100@kezia.com> Hi the list, I'm testing OpenAFS with MacOSX 10.5.8 and OpenAFS 1.5.73. Here setup of my cell : I started to configure my first server. It hosts now several volumes with some data. All was looking to run fine. Then i configured a second host. This host was added in the cell, only fs service was created. I tested to create a voluem one the second host with success. I was able to get information from the 1st host about the 2rd host. All was looking to run fine. Then i added a site to be able to have a RO copy of my data hosted in 2 volumes by my 1st server. Then i used the vos release command to sync the data. All looked to running fine. The vos release command returned this kind of following output : Released volume 536870918 successfully But since this action all volumes i released are broken and offline. The vos listvol command give this message about the released volumes : Could not attach volume 536870918 I can't access to data. In the VolserLog file i have this log : Thu Apr 15 10:54:30 2010 Starting AFS Volserver 2.0 (/usr/afs/bin/volserver) Thu Apr 15 11:24:32 2010 1 Volser: Clone: Cloning volume 536870918 to new volume 536870919 Thu Apr 15 11:24:32 2010 Clone 536870918: filecount 28 -> 29 diskused 5338 -> 5338 Thu Apr 15 11:24:32 2010 SYNC_ask: negative response on circuit 'FSSYNC' Thu Apr 15 11:24:32 2010 FSYNC_askfs: FSSYNC request denied for reason=101 Thu Apr 15 11:26:24 2010 1 Volser: Delete: volume 536870919 deleted Thu Apr 15 11:48:45 2010 1 Volser: Clone: Cloning volume 536870933 to new volume 536870934 Thu Apr 15 11:48:45 2010 Clone 536870933: filecount 4 -> 5 diskused 5839 -> 5839 Thu Apr 15 11:48:45 2010 SYNC_ask: negative response on circuit 'FSSYNC' Thu Apr 15 11:48:45 2010 FSYNC_askfs: FSSYNC request denied for reason=101 Thu Apr 15 11:50:43 2010 1 Volser: Delete: volume 536870934 deleted But after a vos salvage data are back. I'm not sure all data but at least some data. It is just a volume used for tests. What happened ? Best regards, -- *Fabien COMBERNOUS* /unix system engineer/ www.kezia.com *Tel: +33 (0) 467 992 986* Kezia Group -- *Fabien COMBERNOUS* /unix system engineer/ www.kezia.com *Tel: +33 (0) 467 992 986* Kezia Group From fcombernous@kezia.com Fri Apr 16 14:00:46 2010 From: fcombernous@kezia.com (Fabien COMBERNOUS) Date: Fri, 16 Apr 2010 15:00:46 +0200 Subject: [OpenAFS] released volume, deleted In-Reply-To: References: <4BC80CE8.80100@kezia.com> Message-ID: <4BC85F7E.7040603@kezia.com> Steven Jenkins wrote: > Could you provide your fileserver configuration? (ie, the output of > bos status $servername -long) Is it possible that you've used the > non-Demand Attach Fileserver configuration with 1.5, which has Demand > Attach? e.g., http://blog.endpoint.com/2009/06/getting-started-with-demand-attach.html > and http://www.dementia.org/twiki/bin/view/AFSLore/DemandAttach > Thank you for your answer. Links you provided are very interesting. We are using MacOSX as server. Since i noticed that for this OS the production release of OpenAFS is 1.4, i reinstalled my cell with this version. I did the same configuration and now a vos release command runs like a charm. Unfortunately, I don't have more time to continue about OpenAFS 1.5 tests. Best regards, -- *Fabien COMBERNOUS* /unix system engineer/ www.kezia.com *Tel: +33 (0) 467 992 986* Kezia Group From fcombernous@kezia.com Fri Apr 16 14:58:05 2010 From: fcombernous@kezia.com (Fabien COMBERNOUS) Date: Fri, 16 Apr 2010 15:58:05 +0200 Subject: [OpenAFS] OpenAFS algorithm Message-ID: <4BC86CED.8020001@kezia.com> Hi, We are testing OpenAFS. We have a new cell, hosted by two servers located in two differents cities A and B. Only on server (in A) have a RW volume, and all servers (in A and B) have a RO copy of the volume. From an OpenAFS client located in B, i tried to access to data of the cell. The time necessary to display the picture lets me to say that the client contacted the remote server in A. My question is how to permit client in B to use server in B ? I didn't found any document explaining the algorithm used by OpenAFS to decide the server contacted by the client. Best regards, -- *Fabien COMBERNOUS* /unix system engineer/ www.kezia.com *Tel: +33 (0) 467 992 986* Kezia Group From adeason@sinenomine.net Fri Apr 16 15:34:43 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Fri, 16 Apr 2010 09:34:43 -0500 Subject: [OpenAFS] Re: OpenAFS algorithm References: <4BC86CED.8020001@kezia.com> Message-ID: <20100416093443.a7772b50.adeason@sinenomine.net> On Fri, 16 Apr 2010 15:58:05 +0200 Fabien COMBERNOUS wrote: > My question is how to permit client in B to use server in B ? I didn't > found any document explaining the algorithm used by OpenAFS to decide > the server contacted by the client. 'fs setserverprefs' / 'fs getserverprefs'. You can get information on either via their manpages (fs_setserverprefs(1)) or here: The default preferences tend to not be very good (there is a project to improve them), so for such a distributed setup you probably want to set them yourself. Possibly in some init script on the client so you don't lose the preferences on reboot. Also, you want to make sure that you are accessing the RO data. Running 'fs whereis /afs/path/to/file' should mention that the file is on multiple hosts, if you are accessing the RO. -- Andrew Deason adeason@sinenomine.net From tcreedon@easystreet.net Fri Apr 16 15:36:08 2010 From: tcreedon@easystreet.net (Ted Creedon) Date: Fri, 16 Apr 2010 07:36:08 -0700 Subject: [OpenAFS] Missing AFS Client tabs? In-Reply-To: <4BC7B25E.6000705@secure-endpoints.com> References: <4BC7B25E.6000705@secure-endpoints.com> Message-ID: --000e0cd4ce4a37580604845b88bf Content-Type: text/plain; charset=ISO-8859-1 The documentation needs updating. On Thu, Apr 15, 2010 at 5:42 PM, Jeffrey Altman < jaltman@secure-endpoints.com> wrote: > On 4/15/2010 7:37 PM, Ted Creedon wrote: > > OpenAFS for Windows 1.5.73:on Windows Server 2003 > > > > 2 lock symbols appear in the system tray > > > > the "Drive Letters" and "Advanced" tabs are missing from the AFS Client > > popup. > > > > Thanks > > > > Tedc > > > > > > The Drive Letters and Advanced tabs are not compatible with Vista and > above. They have been removed. This is documented in the release notes > and was discussed on this mailing list before the change was made. > > The two icons are the result of running both the AFS Authentication tool > and Network Identity Manager. Please choose one. Network Identity > Manager has an option to automatically disable the AFS Authentication > Tool if that is your choice. > > Jeffrey Altman > > > --000e0cd4ce4a37580604845b88bf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The documentation needs updating.

On Thu,= Apr 15, 2010 at 5:42 PM, Jeffrey Altman <jaltman@secure-endpoi= nts.com> wrote:
On 4/15/2010= 7:37 PM, Ted Creedon wrote:
> OpenAFS for Windows 1.5.73:on Windows Server 2003
>
> 2 lock symbols appear in the system tray
>
> the "Drive Letters" and "Advanced" tabs are missin= g from the AFS Client
> popup.
>
> Thanks
>
> Tedc
>
>

The Drive Letters and Advanced tabs are not compatible with Vista and=
above. =A0They have been removed. =A0This is documented in the release note= s
and was discussed on this mailing list before the change was made.

The two icons are the result of running both the AFS Authentication tool and Network Identity Manager. =A0Please choose one. =A0 Network Identity Manager has an option to automatically disable the AFS Authentication
Tool if that is your choice.

Jeffrey Altman



--000e0cd4ce4a37580604845b88bf-- From haba@kth.se Fri Apr 16 17:16:22 2010 From: haba@kth.se (Harald Barth) Date: Fri, 16 Apr 2010 18:16:22 +0200 (CEST) Subject: [OpenAFS] OpenAFS algorithm In-Reply-To: <4BC86CED.8020001@kezia.com> References: <4BC86CED.8020001@kezia.com> Message-ID: <20100416.181622.166956551.haba@habanero.pdc.kth.se> > My question is how to permit client in B to use server in B ? I > didn't found any document explaining the algorithm used by OpenAFS > to decide the server contacted by the client. The algoritm is very old and if your IP numbers do not reflect your network topology it probably yields incorrect results. Have a look at man fs_setserverprefs and man fs_getserverprefs a lower value indicates a greater preference but first check that the clients really knows that there is more than one copy (something like this): $ fs where /afs/pdc.kth.se/home/ File /afs/pdc.kth.se/home/ is on hosts kinilaw.pdc.kth.se morena.pdc.kth.se sculpin.pdc.kth.se houting.pdc.kth.se As my list from fs gets is quite long, I came up with this to find out which one should be the prefered server: $ fs gets | awk '$1 ~ "'$(echo $(fs where /afs/pdc.kth.se/home/ | awk -Fhosts\ '{print $2}') | sed "s/\ /|/g")'"' | sort +1 -2n Harald. From mdw@umich.edu Fri Apr 16 17:19:45 2010 From: mdw@umich.edu (Marcus Watts) Date: Fri, 16 Apr 2010 12:19:45 -0400 Subject: [OpenAFS] Re: Ubik problem In-Reply-To: References: <201004141855.o3EItfu4012245@ruuvi.it.helsinki.fi> <20100415194422.b34491ec.adeason@sinenomine.net> <87pr20nqrr.fsf@windlord.stanford.edu> Message-ID: Derrick Brashear sent: > Date: Thu, 15 Apr 2010 23:02:33 EDT > To: Russ Allbery > cc: openafs-info@openafs.org > From: Derrick Brashear > Subject: Re: [OpenAFS] Re: Ubik problem > > On Thu, Apr 15, 2010 at 9:13 PM, Russ Allbery wrote: > > Andrew Deason writes: > >> Atro Tossavainen wrote: > > > >>> Derrick, > >>> > >>> > I'd suggest just using the IBM binary for the kaserver (and only the > >>> > kaserver) in your OpenAFS installation > >>> > >>> That's an interesting thought, but unfortunately it's nowhere near > >>> an option. =A0sunx86_ is quite simply not a supported platform for > >>> IBM AFS at all, even at 3.6 Patch 19 (August 2009). > > > >> Older OpenAFS releases could be another option, but I don't know how > >> useful of an answer that is. I'm not sure what could have caused that, > >> so I don't have a particular range in mind; maybe just earlier 1.4... > >> 1.4.9? 1.4.2? > > > > We were successfully running a 1.2.x version of kaserver on SPARC Solaris= > , > > and upgrading to 1.4.2 on Linux failed (albeit with different symptoms; i= > t > > would just stop successfully giving out tickets for a while and then come > > back, regularly), so we stuck with 1.2.x on SPARC until we turned it off > > entirely. > > I'm pretty sure it "broke" between 1.2.11 and 1.4.1. > > --=20 > Derrick Gah. You made me drag out my kaserver notes! Worse! You made me *run* the thing! Bad! Bad! "broke" is a pretty vague description, so... >From the previous descriptions, it sounds like there might be ubik sync issues. That could be caused either by problems in ubik, or unrelated problems that cause server crashes. The reports do not include notes on any resulting core dumps, and the ubik problem reports clearly indicate another serious problem with server address determination. I experimented with building a version of 1.2.11, running it and using some of the diagnostic tools, followed by trying to run the resulting database with 1.4.12. I certainly didn't thoroughly explore things. I now have an interesting list of "problems". /1/ ubik_hdr.size got changed to be a short, not a long. ntohl is wrong. This is in ubik proper as well as kaserver diagnostics. Fortunately, this doesn't seem to break too much. /2/ udebug address output byte swap issues. Previously mentioned as fixed. /3/ kadb_check complains about a lot of stuff, and the output does not make much sense. A lot of this looks like endian issues, but also I think this tool probably started as a temporary hack and never well cleaned up. The output was probably never really 'clean" in the first place. /4/ I never got kaserver to core dump (granted, I'm not pushing it real hard.) I think at least in some basic way, the kaserver in 1.4.12 still "works". So I am still curious as to what Derrick meant by "broke". possible generic action items, /1/ fix uhdr.size usage issues. (ntohs/htons not ntohl/htonl). /2/ fix kadb_check to produce correct output. Should match on little and big-endian machines. /3/ fix kadb_check to produce "better" output? For Atro Tossavainen, I think my recommendations are: /1/ can he only run one source version of kaserver on all db hosts (not a mixed ibm/openafs env), /2/ can he resolve the server setup such that when udebug is run, it only reports "correct" IP addresses? (Ideally only the primary, but the other interfaces should be ok so long as packets sent through them get to the same place.) /3/ can he resolve time so that he never sees "last beacon sent -3 secs ago"?, ubik does care, even more than kerberos, about time. /4/ can he resolve his keyfile reference such that he never gets "unknown key version number"? (My suspicion, he's got path issues between differently built binaries.) -Marcus Watts From shadow@gmail.com Fri Apr 16 17:30:50 2010 From: shadow@gmail.com (Derrick Brashear) Date: Fri, 16 Apr 2010 12:30:50 -0400 Subject: [OpenAFS] Re: Ubik problem In-Reply-To: References: <201004141855.o3EItfu4012245@ruuvi.it.helsinki.fi> <20100415194422.b34491ec.adeason@sinenomine.net> <87pr20nqrr.fsf@windlord.stanford.edu> Message-ID: On Fri, Apr 16, 2010 at 12:19 PM, Marcus Watts wrote: > Derrick Brashear sent: > >> Date: =A0 =A0Thu, 15 Apr 2010 23:02:33 EDT >> To: =A0 =A0 =A0Russ Allbery >> cc: =A0 =A0 =A0openafs-info@openafs.org >> From: =A0 =A0Derrick Brashear >> Subject: Re: [OpenAFS] Re: Ubik problem >> >> On Thu, Apr 15, 2010 at 9:13 PM, Russ Allbery wrote: >> > Andrew Deason writes: >> >> Atro Tossavainen wrote: >> > >> >>> Derrick, >> >>> >> >>> > I'd suggest just using the IBM binary for the kaserver (and only t= he >> >>> > kaserver) in your OpenAFS installation >> >>> >> >>> That's an interesting thought, but unfortunately it's nowhere near >> >>> an option. =3DA0sunx86_ is quite simply not a supported platform for >> >>> IBM AFS at all, even at 3.6 Patch 19 (August 2009). >> > >> >> Older OpenAFS releases could be another option, but I don't know how >> >> useful of an answer that is. I'm not sure what could have caused that= , >> >> so I don't have a particular range in mind; maybe just earlier 1.4... >> >> 1.4.9? 1.4.2? >> > >> > We were successfully running a 1.2.x version of kaserver on SPARC Sola= ris=3D >> , >> > and upgrading to 1.4.2 on Linux failed (albeit with different symptoms= ; i=3D >> t >> > would just stop successfully giving out tickets for a while and then c= ome >> > back, regularly), so we stuck with 1.2.x on SPARC until we turned it o= ff >> > entirely. >> >> I'm pretty sure it "broke" between 1.2.11 and 1.4.1. >> >> --=3D20 >> Derrick > > Gah. =A0You made me drag out my kaserver notes! =A0Worse! =A0You made me > *run* the thing! =A0Bad! =A0Bad! > > "broke" is a pretty vague description, so... > > From the previous descriptions, it sounds like there might be ubik sync i= ssues. That's not what I was referring to. I think it's between ubik database reads and the clients. > That could be caused either by problems in ubik, or unrelated problems > that cause server crashes. =A0The reports do not include notes on any res= ulting > core dumps, and the ubik problem reports clearly indicate another serious > problem with server address determination. > > I experimented with building a version of 1.2.11, running it and using so= me > of the diagnostic tools, followed by trying to run the resulting database= with > 1.4.12. =A0I certainly didn't thoroughly explore things. =A0I now have an= interesting > list of "problems". > > /1/ ubik_hdr.size got changed to be a short, not a long. =A0ntohl is wron= g. =A0This > =A0 =A0 =A0 =A0is in ubik proper as well as kaserver diagnostics. =A0Fort= unately, this > =A0 =A0 =A0 =A0doesn't seem to break too much. > /2/ udebug address output byte swap issues. =A0Previously mentioned as fi= xed. > /3/ kadb_check complains about a lot of stuff, and the output does not > =A0 =A0 =A0 =A0make much sense. =A0A lot of this looks like endian issues= , but > =A0 =A0 =A0 =A0also I think this tool probably started as a temporary hac= k and > =A0 =A0 =A0 =A0never well cleaned up. =A0The output was probably never re= ally > =A0 =A0 =A0 =A0'clean" in the first place. > /4/ I never got kaserver to core dump (granted, I'm not pushing it real h= ard.) > > I think at least in some basic way, the kaserver in 1.4.12 still "works". > So I am still curious as to what Derrick meant by "broke". > > possible generic action items, > /1/ fix uhdr.size usage issues. (ntohs/htons not ntohl/htonl). > /2/ fix kadb_check to produce correct output. =A0Should match on little > =A0 =A0 =A0 =A0and big-endian machines. > /3/ fix kadb_check to produce "better" output? > > For Atro Tossavainen, I think my recommendations are: > /1/ can he only run one source version of kaserver on all db hosts (not a > =A0 =A0 =A0 =A0mixed ibm/openafs env), > /2/ can he resolve the server setup such that when udebug is > =A0 =A0 =A0 =A0run, it only reports "correct" IP addresses? =A0(Ideally o= nly > =A0 =A0 =A0 =A0the primary, but the other interfaces should be ok so long > =A0 =A0 =A0 =A0as packets sent through them get to the same place.) > /3/ can he resolve time so that he never sees "last beacon sent -3 secs a= go"?, > =A0 =A0 =A0 =A0ubik does care, even more than kerberos, about time. > /4/ can he resolve his keyfile reference such that he never gets > =A0 =A0 =A0 =A0"unknown key version number"? > =A0 =A0 =A0 =A0(My suspicion, he's got path issues between differently bu= ilt binaries.) no, because i suspect 4 is the "real issue" --=20 Derrick From adeason@sinenomine.net Fri Apr 16 17:38:41 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Fri, 16 Apr 2010 11:38:41 -0500 Subject: [OpenAFS] Re: Ubik problem References: <201004141855.o3EItfu4012245@ruuvi.it.helsinki.fi> <20100415194422.b34491ec.adeason@sinenomine.net> <87pr20nqrr.fsf@windlord.stanford.edu> Message-ID: <20100416113841.cefbbded.adeason@sinenomine.net> On Fri, 16 Apr 2010 12:19:45 -0400 Marcus Watts wrote: > I think at least in some basic way, the kaserver in 1.4.12 still "works". > So I am still curious as to what Derrick meant by "broke". My guess would be periodically throwing kvno errors and periodically not serving requests, according to what this thread has said. The "not reliably reproducible" kind of brokenness. > /2/ can he resolve the server setup such that when udebug is > run, it only reports "correct" IP addresses? (Ideally only > the primary, but the other interfaces should be ok so long > as packets sent through them get to the same place.) I do think this can be solved by just removing the 'M ' in NetRetsrict on the new server, by the way. > /4/ can he resolve his keyfile reference such that he never gets > "unknown key version number"? > (My suspicion, he's got path issues between differently built binaries.) That wouldn't cause these errors to just appear after the server's been running for awhile, and go away on restart. -- Andrew Deason adeason@sinenomine.net From shadow@gmail.com Fri Apr 16 17:43:30 2010 From: shadow@gmail.com (Derrick Brashear) Date: Fri, 16 Apr 2010 12:43:30 -0400 Subject: [OpenAFS] Re: Ubik problem In-Reply-To: References: <201004141855.o3EItfu4012245@ruuvi.it.helsinki.fi> <20100415194422.b34491ec.adeason@sinenomine.net> <87pr20nqrr.fsf@windlord.stanford.edu> Message-ID: It might actually be worth valgrinding. On Fri, Apr 16, 2010 at 12:30 PM, Derrick Brashear wrote= : > On Fri, Apr 16, 2010 at 12:19 PM, Marcus Watts wrote: >> Derrick Brashear sent: >> >>> Date: =A0 =A0Thu, 15 Apr 2010 23:02:33 EDT >>> To: =A0 =A0 =A0Russ Allbery >>> cc: =A0 =A0 =A0openafs-info@openafs.org >>> From: =A0 =A0Derrick Brashear >>> Subject: Re: [OpenAFS] Re: Ubik problem >>> >>> On Thu, Apr 15, 2010 at 9:13 PM, Russ Allbery wrote: >>> > Andrew Deason writes: >>> >> Atro Tossavainen wrote: >>> > >>> >>> Derrick, >>> >>> >>> >>> > I'd suggest just using the IBM binary for the kaserver (and only = the >>> >>> > kaserver) in your OpenAFS installation >>> >>> >>> >>> That's an interesting thought, but unfortunately it's nowhere near >>> >>> an option. =3DA0sunx86_ is quite simply not a supported platform fo= r >>> >>> IBM AFS at all, even at 3.6 Patch 19 (August 2009). >>> > >>> >> Older OpenAFS releases could be another option, but I don't know how >>> >> useful of an answer that is. I'm not sure what could have caused tha= t, >>> >> so I don't have a particular range in mind; maybe just earlier 1.4..= . >>> >> 1.4.9? 1.4.2? >>> > >>> > We were successfully running a 1.2.x version of kaserver on SPARC Sol= aris=3D >>> , >>> > and upgrading to 1.4.2 on Linux failed (albeit with different symptom= s; i=3D >>> t >>> > would just stop successfully giving out tickets for a while and then = come >>> > back, regularly), so we stuck with 1.2.x on SPARC until we turned it = off >>> > entirely. >>> >>> I'm pretty sure it "broke" between 1.2.11 and 1.4.1. >>> >>> --=3D20 >>> Derrick >> >> Gah. =A0You made me drag out my kaserver notes! =A0Worse! =A0You made me >> *run* the thing! =A0Bad! =A0Bad! >> >> "broke" is a pretty vague description, so... >> >> From the previous descriptions, it sounds like there might be ubik sync = issues. > > That's not what I was referring to. I think it's between ubik database > reads and the clients. > >> That could be caused either by problems in ubik, or unrelated problems >> that cause server crashes. =A0The reports do not include notes on any re= sulting >> core dumps, and the ubik problem reports clearly indicate another seriou= s >> problem with server address determination. >> >> I experimented with building a version of 1.2.11, running it and using s= ome >> of the diagnostic tools, followed by trying to run the resulting databas= e with >> 1.4.12. =A0I certainly didn't thoroughly explore things. =A0I now have a= n interesting >> list of "problems". >> >> /1/ ubik_hdr.size got changed to be a short, not a long. =A0ntohl is wro= ng. =A0This >> =A0 =A0 =A0 =A0is in ubik proper as well as kaserver diagnostics. =A0For= tunately, this >> =A0 =A0 =A0 =A0doesn't seem to break too much. >> /2/ udebug address output byte swap issues. =A0Previously mentioned as f= ixed. >> /3/ kadb_check complains about a lot of stuff, and the output does not >> =A0 =A0 =A0 =A0make much sense. =A0A lot of this looks like endian issue= s, but >> =A0 =A0 =A0 =A0also I think this tool probably started as a temporary ha= ck and >> =A0 =A0 =A0 =A0never well cleaned up. =A0The output was probably never r= eally >> =A0 =A0 =A0 =A0'clean" in the first place. >> /4/ I never got kaserver to core dump (granted, I'm not pushing it real = hard.) >> >> I think at least in some basic way, the kaserver in 1.4.12 still "works"= . >> So I am still curious as to what Derrick meant by "broke". >> >> possible generic action items, >> /1/ fix uhdr.size usage issues. (ntohs/htons not ntohl/htonl). >> /2/ fix kadb_check to produce correct output. =A0Should match on little >> =A0 =A0 =A0 =A0and big-endian machines. >> /3/ fix kadb_check to produce "better" output? >> >> For Atro Tossavainen, I think my recommendations are: >> /1/ can he only run one source version of kaserver on all db hosts (not = a >> =A0 =A0 =A0 =A0mixed ibm/openafs env), >> /2/ can he resolve the server setup such that when udebug is >> =A0 =A0 =A0 =A0run, it only reports "correct" IP addresses? =A0(Ideally = only >> =A0 =A0 =A0 =A0the primary, but the other interfaces should be ok so lon= g >> =A0 =A0 =A0 =A0as packets sent through them get to the same place.) >> /3/ can he resolve time so that he never sees "last beacon sent -3 secs = ago"?, >> =A0 =A0 =A0 =A0ubik does care, even more than kerberos, about time. >> /4/ can he resolve his keyfile reference such that he never gets >> =A0 =A0 =A0 =A0"unknown key version number"? >> =A0 =A0 =A0 =A0(My suspicion, he's got path issues between differently b= uilt binaries.) > > no, because i suspect 4 is the "real issue" > > > -- > Derrick > --=20 Derrick From shadow@gmail.com Fri Apr 16 17:44:03 2010 From: shadow@gmail.com (Derrick Brashear) Date: Fri, 16 Apr 2010 12:44:03 -0400 Subject: [OpenAFS] Missing AFS Client tabs? In-Reply-To: References: <4BC7B25E.6000705@secure-endpoints.com> Message-ID: On Fri, Apr 16, 2010 at 10:36 AM, Ted Creedon wro= te: > The documentation needs updating. Cool. Submit the changes to gerrit when they're done. > On Thu, Apr 15, 2010 at 5:42 PM, Jeffrey Altman > wrote: >> >> On 4/15/2010 7:37 PM, Ted Creedon wrote: >> > OpenAFS for Windows 1.5.73:on Windows Server 2003 >> > >> > 2 lock symbols appear in the system tray >> > >> > the "Drive Letters" and "Advanced" tabs are missing from the AFS Clien= t >> > popup. >> > >> > Thanks >> > >> > Tedc >> > >> > >> >> The Drive Letters and Advanced tabs are not compatible with Vista and >> above. =A0They have been removed. =A0This is documented in the release n= otes >> and was discussed on this mailing list before the change was made. >> >> The two icons are the result of running both the AFS Authentication tool >> and Network Identity Manager. =A0Please choose one. =A0 Network Identity >> Manager has an option to automatically disable the AFS Authentication >> Tool if that is your choice. >> >> Jeffrey Altman >> >> > > --=20 Derrick From jaltman@secure-endpoints.com Fri Apr 16 18:04:40 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Fri, 16 Apr 2010 13:04:40 -0400 Subject: [OpenAFS] OpenAFS algorithm In-Reply-To: <20100416.181622.166956551.haba@habanero.pdc.kth.se> References: <4BC86CED.8020001@kezia.com> <20100416.181622.166956551.haba@habanero.pdc.kth.se> Message-ID: <4BC898A8.5010006@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms020106060006080208050504 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/16/2010 12:16 PM, Harald Barth wrote: >=20 >> My question is how to permit client in B to use server in B ? I >> didn't found any document explaining the algorithm used by OpenAFS >> to decide the server contacted by the client. >=20 > The algorithm is very old and if your IP numbers do not reflect your > network topology it probably yields incorrect results. >=20 OpenAFS clients on Windows since last Fall have implemented the results of Jake Thebault-Spieker's GSoC project that computes the server preferences based upon the observed round trip times measured for each server instance. Jake is working on an implementation for the UNIX clients. A copy of the slides from Jake's presentation at the European AFS Conference 2009 can be found at http://www.dia.uniroma3.it/~afscon09/docs/part2.pdf Jeffrey Altman --------------ms020106060006080208050504 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MTYxNzA0NDBaMCMGCSqGSIb3DQEJBDEWBBSqHis4 Z/WiXgxuiBZbXmgOpcbylzBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBABCHXXEzumm/vIoVrOir4mJVl4eQpy+Zo2aH pDnZIQZWnd+d7ysrTwZqgPAxBGTUnG/97NDwHbYJmziZEkRJFwuRkqZ4j/BkSObVoV6HCrA3 Iwu/ov+B872xGnofbdGXwVNZtK9ObCcnnKBqhDKrvOeZj7t24MMuHPhElMZERoDFfPw3aQPs fcbNMObB/+zPpm7GhgPTHHwSM+3fMQuuEsc2DIxR1EYjhg5+DVIcfafpBLqGMkT8c2b9gw3I 1nIrzvmal8RgaeYkyGmwCln1JrMj35KeaOApwt2KVN93tKqLHq9l7qcOHQvOf6qRZrS2raoC yaA1viRAcGnLznsDa/4AAAAAAAA= --------------ms020106060006080208050504-- From tcreedon@easystreet.net Fri Apr 16 18:25:51 2010 From: tcreedon@easystreet.net (Ted Creedon) Date: Fri, 16 Apr 2010 10:25:51 -0700 Subject: [OpenAFS] Missing AFS Client tabs? In-Reply-To: References: <4BC7B25E.6000705@secure-endpoints.com> Message-ID: --00504502bb552433ff04845de7d5 Content-Type: text/plain; charset=ISO-8859-1 Except I don't know the procedure to map drives... Ted On Fri, Apr 16, 2010 at 9:44 AM, Derrick Brashear wrote: > On Fri, Apr 16, 2010 at 10:36 AM, Ted Creedon > wrote: > > The documentation needs updating. > > Cool. Submit the changes to gerrit when they're done. > > > On Thu, Apr 15, 2010 at 5:42 PM, Jeffrey Altman > > wrote: > >> > >> On 4/15/2010 7:37 PM, Ted Creedon wrote: > >> > OpenAFS for Windows 1.5.73:on Windows Server 2003 > >> > > >> > 2 lock symbols appear in the system tray > >> > > >> > the "Drive Letters" and "Advanced" tabs are missing from the AFS > Client > >> > popup. > >> > > >> > Thanks > >> > > >> > Tedc > >> > > >> > > >> > >> The Drive Letters and Advanced tabs are not compatible with Vista and > >> above. They have been removed. This is documented in the release notes > >> and was discussed on this mailing list before the change was made. > >> > >> The two icons are the result of running both the AFS Authentication tool > >> and Network Identity Manager. Please choose one. Network Identity > >> Manager has an option to automatically disable the AFS Authentication > >> Tool if that is your choice. > >> > >> Jeffrey Altman > >> > >> > > > > > > > > -- > Derrick > --00504502bb552433ff04845de7d5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Except I don't know the procedure to map drives...

Ted

On Fri, Apr 16, 2010 at 9:44 AM, Derrick Brashear = <shadow@gmail.com<= /a>> wrote:
On Fri, Apr 16, 2= 010 at 10:36 AM, Ted Creedon <tcreedon@easystreet.net> wrote:
> The documentation needs updating.

Cool. Submit the changes to gerrit when they're done.

> On Thu, Apr 15, 2010 at 5:42 PM, Jeffrey Altman
> <jaltman@secure-end= points.com> wrote:
>>
>> On 4/15/2010 7:37 PM, Ted Creedon wrote:
>> > OpenAFS for Windows 1.5.73:on Windows Server 2003
>> >
>> > 2 lock symbols appear in the system tray
>> >
>> > the "Drive Letters" and "Advanced" tabs a= re missing from the AFS Client
>> > popup.
>> >
>> > Thanks
>> >
>> > Tedc
>> >
>> >
>>
>> The Drive Letters and Advanced tabs are not compatible with Vista = and
>> above. =A0They have been removed. =A0This is documented in the rel= ease notes
>> and was discussed on this mailing list before the change was made.=
>>
>> The two icons are the result of running both the AFS Authenticatio= n tool
>> and Network Identity Manager. =A0Please choose one. =A0 Network Id= entity
>> Manager has an option to automatically disable the AFS Authenticat= ion
>> Tool if that is your choice.
>>
>> Jeffrey Altman
>>
>>
>
>



--
Derrick

--00504502bb552433ff04845de7d5-- From jaltman@secure-endpoints.com Fri Apr 16 19:00:16 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Fri, 16 Apr 2010 14:00:16 -0400 Subject: [OpenAFS] Missing AFS Client tabs? In-Reply-To: References: <4BC7B25E.6000705@secure-endpoints.com> Message-ID: <4BC8A5B0.5010106@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms030805040304020703000104 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/16/2010 1:25 PM, Ted Creedon wrote: > Except I don't know the procedure to map drives... >=20 > Ted How to map drives is discussed in your Windows documentation. You map drives to \\AFS exactly the same way you map drives to any other UNC path on Windows. Note that the release notes for OpenAFS for Windows have stated for many years now that drive mapping should be performed using the Explorer shell. Jeffrey Altman --------------ms030805040304020703000104 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MTYxODAwMTZaMCMGCSqGSIb3DQEJBDEWBBQTc6ea nCA3hmb2x7hU7HwEcjb0LzBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAKfqKq95OHOg+z5nYKYzanIuhwrzxyChaJtT GFIB1gf8TFnmpljePJvGzmGjUMhxlL8efnykKEzPmTEl1dCkQ7jQ610+png+eF0Hw2u7sHE2 V/NAD1GTgD1KKsZ40CrHIvMsnP15BtQIP0oUdxXwIJOBA3gjwhZ/uI2hgRN8o8kH+HMrzfBP ROoBjhgp/S0eqwAxyH08lx7WwaYcdfr5IuET+kRUexRg/1A1wwvtUZ7k7df1yn/bksvA6tkc 7JWH5JNC2wd/x40N3Ldso16EAazEGDLQnEq9apwGnvZkii0z5r7FVdSlG31pq+95f0KuqtBw DA4G/jpskTsYIW4bfI0AAAAAAAA= --------------ms030805040304020703000104-- From tcreedon@easystreet.net Fri Apr 16 19:07:18 2010 From: tcreedon@easystreet.net (Ted Creedon) Date: Fri, 16 Apr 2010 11:07:18 -0700 Subject: [OpenAFS] Missing AFS Client tabs? In-Reply-To: <4BC8A5B0.5010106@secure-endpoints.com> References: <4BC7B25E.6000705@secure-endpoints.com> <4BC8A5B0.5010106@secure-endpoints.com> Message-ID: --00504502cd4859f6a004845e7beb Content-Type: text/plain; charset=ISO-8859-1 The windows documentation shows the 3 tabs.. On Fri, Apr 16, 2010 at 11:00 AM, Jeffrey Altman < jaltman@secure-endpoints.com> wrote: > On 4/16/2010 1:25 PM, Ted Creedon wrote: > > Except I don't know the procedure to map drives... > > > > Ted > > How to map drives is discussed in your Windows documentation. You map > drives to \\AFS exactly the same way you map drives to any other UNC > path on Windows. Note that the release notes for OpenAFS for Windows > have stated for many years now that drive mapping should be performed > using the Explorer shell. > > Jeffrey Altman > > --00504502cd4859f6a004845e7beb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The windows documentation shows the 3 tabs..

On Fri, Apr 16, 2010 at 11:00 AM, Jeffrey Altman <= jaltman@secure-endpoints.co= m> wrote:
On 4/16/2010 1:25 PM, Ted Creedon wrote:
> Except I don't know the procedure to map drives...
>
> Ted

How to map drives is discussed in your Windows documentation. =A0You = map
drives to \\AFS exactly the same way you map drives to any other UNC
path on Windows. =A0Note that the release notes for OpenAFS for Windows
have stated for many years now that drive mapping should be performed
using the Explorer shell.

Jeffrey Altman


--00504502cd4859f6a004845e7beb-- From mdw@umich.edu Fri Apr 16 21:33:40 2010 From: mdw@umich.edu (Marcus Watts) Date: Fri, 16 Apr 2010 16:33:40 -0400 Subject: [OpenAFS] Re: Ubik problem In-Reply-To: References: <201004141855.o3EItfu4012245@ruuvi.it.helsinki.fi> <20100415194422.b34491ec.adeason@sinenomine.net> <87pr20nqrr.fsf@windlord.stanford.edu> Message-ID: Derrick Brashear writes: > Date: Fri, 16 Apr 2010 12:43:30 EDT > To: Marcus Watts > cc: openafs-info@openafs.org > From: Derrick Brashear > Subject: Re: [OpenAFS] Re: Ubik problem > > It might actually be worth valgrinding. > > On Fri, Apr 16, 2010 at 12:30 PM, Derrick Brashear wrote= > : > > On Fri, Apr 16, 2010 at 12:19 PM, Marcus Watts wrote: > >> Derrick Brashear sent: > >> > >>> Date: =A0 =A0Thu, 15 Apr 2010 23:02:33 EDT > >>> To: =A0 =A0 =A0Russ Allbery > >>> cc: =A0 =A0 =A0openafs-info@openafs.org > >>> From: =A0 =A0Derrick Brashear > >>> Subject: Re: [OpenAFS] Re: Ubik problem > >>> > >>> On Thu, Apr 15, 2010 at 9:13 PM, Russ Allbery wrote: > >>> > Andrew Deason writes: > >>> >> Atro Tossavainen wrote: > >>> > > >>> >>> Derrick, > >>> >>> > >>> >>> > I'd suggest just using the IBM binary for the kaserver (and only = > the > >>> >>> > kaserver) in your OpenAFS installation > >>> >>> > >>> >>> That's an interesting thought, but unfortunately it's nowhere near > >>> >>> an option. =3DA0sunx86_ is quite simply not a supported platform fo= > r > >>> >>> IBM AFS at all, even at 3.6 Patch 19 (August 2009). > >>> > > >>> >> Older OpenAFS releases could be another option, but I don't know how > >>> >> useful of an answer that is. I'm not sure what could have caused tha= > t, > >>> >> so I don't have a particular range in mind; maybe just earlier 1.4..= > . > >>> >> 1.4.9? 1.4.2? > >>> > > >>> > We were successfully running a 1.2.x version of kaserver on SPARC Sol= > aris=3D > >>> , > >>> > and upgrading to 1.4.2 on Linux failed (albeit with different symptom= > s; i=3D > >>> t > >>> > would just stop successfully giving out tickets for a while and then = > come > >>> > back, regularly), so we stuck with 1.2.x on SPARC until we turned it = > off > >>> > entirely. > >>> > >>> I'm pretty sure it "broke" between 1.2.11 and 1.4.1. > >>> > >>> --=3D20 > >>> Derrick > >> > >> Gah. =A0You made me drag out my kaserver notes! =A0Worse! =A0You made me > >> *run* the thing! =A0Bad! =A0Bad! > >> > >> "broke" is a pretty vague description, so... > >> > >> From the previous descriptions, it sounds like there might be ubik sync = > issues. > > > > That's not what I was referring to. I think it's between ubik database > > reads and the clients. > > > >> That could be caused either by problems in ubik, or unrelated problems > >> that cause server crashes. =A0The reports do not include notes on any re= > sulting > >> core dumps, and the ubik problem reports clearly indicate another seriou= > s > >> problem with server address determination. > >> > >> I experimented with building a version of 1.2.11, running it and using s= > ome > >> of the diagnostic tools, followed by trying to run the resulting databas= > e with > >> 1.4.12. =A0I certainly didn't thoroughly explore things. =A0I now have a= > n interesting > >> list of "problems". > >> > >> /1/ ubik_hdr.size got changed to be a short, not a long. =A0ntohl is wro= > ng. =A0This > >> =A0 =A0 =A0 =A0is in ubik proper as well as kaserver diagnostics. =A0For= > tunately, this > >> =A0 =A0 =A0 =A0doesn't seem to break too much. > >> /2/ udebug address output byte swap issues. =A0Previously mentioned as f= > ixed. > >> /3/ kadb_check complains about a lot of stuff, and the output does not > >> =A0 =A0 =A0 =A0make much sense. =A0A lot of this looks like endian issue= > s, but > >> =A0 =A0 =A0 =A0also I think this tool probably started as a temporary ha= > ck and > >> =A0 =A0 =A0 =A0never well cleaned up. =A0The output was probably never r= > eally > >> =A0 =A0 =A0 =A0'clean" in the first place. > >> /4/ I never got kaserver to core dump (granted, I'm not pushing it real = > hard.) > >> > >> I think at least in some basic way, the kaserver in 1.4.12 still "works"= > . > >> So I am still curious as to what Derrick meant by "broke". > >> > >> possible generic action items, > >> /1/ fix uhdr.size usage issues. (ntohs/htons not ntohl/htonl). > >> /2/ fix kadb_check to produce correct output. =A0Should match on little > >> =A0 =A0 =A0 =A0and big-endian machines. > >> /3/ fix kadb_check to produce "better" output? > >> > >> For Atro Tossavainen, I think my recommendations are: > >> /1/ can he only run one source version of kaserver on all db hosts (not = > a > >> =A0 =A0 =A0 =A0mixed ibm/openafs env), > >> /2/ can he resolve the server setup such that when udebug is > >> =A0 =A0 =A0 =A0run, it only reports "correct" IP addresses? =A0(Ideally = > only > >> =A0 =A0 =A0 =A0the primary, but the other interfaces should be ok so lon= > g > >> =A0 =A0 =A0 =A0as packets sent through them get to the same place.) > >> /3/ can he resolve time so that he never sees "last beacon sent -3 secs = > ago"?, > >> =A0 =A0 =A0 =A0ubik does care, even more than kerberos, about time. > >> /4/ can he resolve his keyfile reference such that he never gets > >> =A0 =A0 =A0 =A0"unknown key version number"? > >> =A0 =A0 =A0 =A0(My suspicion, he's got path issues between differently b= > uilt binaries.) > > > > no, because i suspect 4 is the "real issue" > > > > > > -- > > Derrick > > > > > > --=20 > Derrick I tried valgrind. Run #1 with stripped binaries - I got lots of "stuff". First 5 complaints about uninitialized reads of size 4 come from various bits of lwp. Various later complaints are from deep inside of rx. I didn't see anything that looked unique or specific to kaserver. Generally speaking, valgrind didn't like anything lwp did at all. I got tired of looking up symbols, so tried again with non-stripped binaries. valgrind core dumps instantly. The resulting core dump is badly damaged. It might be worth trying again with a copy of kaserver built with "-g". That shouldn't make a difference, but ... So, yup, valgrind would be nice. So far, it's not being very helpful. Andrew talks a bit about "errors that appear after the server's been running for a while". If this is a memory corruption problem, then there is a good likelyhood of random seg faults, possible core dumps, and server restarts. If there are not core dumps, then it should be possible to reconfigure things so there are. Those core dumps would help a lot. Call tracebacks for failure points would tell us what code paths and data matter here. Just knowing that the software is restarting spontaneously (cat /var/log/openafs/BosLog ?) would help a lot. Some other problems that could cause intermittent behavior include: /1/ flapping network routes. We already know there are multiple addresses... /2/ DNS. Unlikely, but ubik likely depends on dns. if "host `hostname`" lists more than one ip address, round robin behavior in dns might result in oddness. /3/ dueling ubik masters. Wasn't there once a problem with byte ordering and ubik ip address ranking? We definitely have multiple code bases in the picture. Duelling masters--uh, just don't go there. /4/ roving ubik master selection. With only 2 hosts, I don't quite understand how this could happen (but see previous). But since we know the key files aren't consistent, which machines can do "localauth" to others will definitely vary, which could easily look like "it stops working after a while". Usually this is usually only a problem with > 2 db hosts. -Marcus Watts From Atro.Tossavainen@helsinki.fi Fri Apr 16 21:42:10 2010 From: Atro.Tossavainen@helsinki.fi (Atro Tossavainen) Date: Fri, 16 Apr 2010 23:42:10 +0300 (EEST) Subject: [OpenAFS] Re: Ubik problem In-Reply-To: Message-ID: <201004162042.o3GKgAZ1024624@ruuvi.it.helsinki.fi> Marcus, thanks for the insight. > /1/ can he only run one source version of kaserver on all db hosts (not a > mixed ibm/openafs env), I suppose there isn't much to prevent me from running the OpenAFS 1.4.12 version of kaserver on sun4x_58 as well if the list elders figure it is helpful. I won't be able to run a sunx86_510 version of anything IBM because such things don't exist. > /2/ can he resolve the server setup such that when udebug is > run, it only reports "correct" IP addresses? (Ideally only > the primary, but the other interfaces should be ok so long > as packets sent through them get to the same place.) I suppose I could also think of upgrading IBM AFS to 3.6 2.59 (Patch 15) which is the last version to which I have access on sun4x_58 and which should have a consistent handling of NetRestrict across all servers. > /3/ can he resolve time so that he never sees "last beacon sent -3 secs ago"?, > ubik does care, even more than kerberos, about time. sunx86_510 on 128.214.58.174 and sun4x_58 on 128.214.88.114 are NTP peers with each other as well as clients to the same time servers elsewhere on the Uni network. If you have insight as to why this might be a failure, I'm all ears. My gut feeling is that time sync problems between the two don't exist. I ran "xclock -digital -update 1" for a while side by side and they're less than a second apart at worst in a few minutes of doing this. > /4/ can he resolve his keyfile reference such that he never gets > "unknown key version number"? > (My suspicion, he's got path issues between differently built binaries.) Explain "path issues". The OpenAFS on sunx86_510 was built with "--enable-transarc-paths". /usr/afs/etc/KeyFile exists and is identical on all hosts. -- Atro Tossavainen (Mr.) / The Institute of Biotechnology at Systems Analyst, Techno-Amish & / the University of Helsinki, Finland, +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own. < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS From atro.tossavainen+openafs@helsinki.fi Fri Apr 16 21:51:34 2010 From: atro.tossavainen+openafs@helsinki.fi (Atro Tossavainen) Date: Fri, 16 Apr 2010 23:51:34 +0300 (EEST) Subject: [OpenAFS] Re: Ubik problem In-Reply-To: <20100416113841.cefbbded.adeason@sinenomine.net> Message-ID: <201004162051.o3GKpYnt025100@ruuvi.it.helsinki.fi> > > /2/ can he resolve the server setup such that when udebug is > > run, it only reports "correct" IP addresses? (Ideally only > > the primary, but the other interfaces should be ok so long > > as packets sent through them get to the same place.) > > I do think this can be solved by just removing the 'M ' in NetRetsrict > on the new server, by the way. The M is (and always was) there in the old IBM AFS server's NetRestrict file only. But but but. I may have found another NetRestrict related issue that just might have something to do with the whole mess. Let's go back a few weeks. I set the new server up on a different IP address to begin with (as it was a "development" server that I was deploying alongside the sun4x_58 128.214.58.174, which was still in production at that time). At that time, I only made it a fileserver and gradually moved all the files from the old sun4x_58 128.214.58.174 onto it. After the other sun4x_58 box developed a hardware problem, I figured I'd just throw all other servers on in the the sunx86_510 "development" box, change the IP address, vos changeaddr, done. I've only just now spotted it that I had a NetRestrict on the new server that had the "old" development IP address. So it has had a NetRestrict that enabled two specific IP addresses, neither of which was the address it is supposed to have, 128.214.58.174. It does not seem to have been such a problem because files (and to some extent, other data...) have been served from the new server all this time, but it's certainly not a good thing to have there. Changed, bos restart localhost -all, let's see if it changes anything. DOH! If this was it, I'm really sorry to have wasted everybody's time with it. -- Atro Tossavainen (Mr.) / The Institute of Biotechnology at Systems Analyst, Techno-Amish & / the University of Helsinki, Finland, +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own. < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS From atro.tossavainen+openafs@helsinki.fi Fri Apr 16 22:07:01 2010 From: atro.tossavainen+openafs@helsinki.fi (Atro Tossavainen) Date: Sat, 17 Apr 2010 00:07:01 +0300 (EEST) Subject: [OpenAFS] Re: Ubik problem In-Reply-To: Message-ID: <201004162107.o3GL712v025540@ruuvi.it.helsinki.fi> > Andrew talks a bit about "errors that appear after the server's been > running for a while". If this is a memory corruption problem, then > there is a good likelyhood of random seg faults, possible core dumps, > and server restarts. There are no coredumps. (Fileserver and volserver have dumped core previously, and I've got them saved away, so I figure if there were going to be any, at least I am not doing anything to stop it.) I only just restarted all servers deliberately after changing the faulty NetRestrict, but my previous AuthLog on the sunx86_510 extends from Wed Apr 14 15:15 to Fri Apr 16 23:40 which is when I did. I don't think kaserver is restarting spontaneously. > paths and data matter here. Just knowing that the software is restarting > spontaneously (cat /var/log/openafs/BosLog ?) would help a lot. sunx86_510 # less BosLog Sun Apr 11 04:00:58 2010: Server directory access is okay Mon Apr 12 15:09:23 2010: kaserver exited on signal 15 Mon Apr 12 15:11:08 2010: kaserver exited on signal 15 Wed Apr 14 13:07:52 2010: kaserver exited on signal 15 Wed Apr 14 15:14:57 2010: kaserver exited on signal 15 Fri Apr 16 23:44:22 2010: upserverS10x86 exited on signal 15 Fri Apr 16 23:44:22 2010: vlserver exited on signal 15 Fri Apr 16 23:44:22 2010: kaserver exited on signal 15 Fri Apr 16 23:44:22 2010: ptserver exited on signal 15 Fri Apr 16 23:44:22 2010: fs:vol exited on signal 15 Fri Apr 16 23:44:22 2010: upclientetc exited on signal 15 Fri Apr 16 23:45:02 2010: fs:file exited with code 0 > Some other problems that could cause intermittent behavior include: > > /1/ flapping network routes. We already know there are multiple addresses... And a static route. > /2/ DNS. Unlikely, but ubik likely depends on dns. if "host `hostname`" > lists more than one ip address, round robin behavior in dns > might result in oddness. It doesn't. >From DNS, the hostname returns exactly one address. Even if host name resolution was somehow involved, which seems unlikely to my untrained mind, /etc/hosts takes preference, and since it's Solaris, you *have* to have a separate name for each IP address you want to configure on a network interface. Like this: # ls /etc/hostname.nge* hostname.nge0 hostname.nge1 hostname.nge2 # cat /etc/hostname.nge* replicon-dev replicon-rfc1918 replicon # cat /etc/hosts # grep replicon /etc/hosts 128.214.209.84 replicon-dev 128.214.58.174 replicon 10.0.0.20 replicon-rfc1918 nge0 is down and unplumbed now that the "development" server is no more, nge1 is the RFC1918 address, and nge2 is the real McCoy. > But since we know the key files aren't consistent, You "know" that? That's a misassumption at best. sun4x_58 # cksum /usr/afs/etc/KeyFile 2143645127 100 /usr/afs/etc/KeyFile sunx86_510 # cksum /usr/afs/etc/KeyFile 2143645127 100 /usr/afs/etc/KeyFile -- Atro Tossavainen (Mr.) / The Institute of Biotechnology at Systems Analyst, Techno-Amish & / the University of Helsinki, Finland, +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own. < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS From atro.tossavainen+openafs@helsinki.fi Fri Apr 16 22:12:01 2010 From: atro.tossavainen+openafs@helsinki.fi (Atro Tossavainen) Date: Sat, 17 Apr 2010 00:12:01 +0300 (EEST) Subject: [OpenAFS] Re: Ubik problem In-Reply-To: <201004162051.o3GKpYnt025100@ruuvi.it.helsinki.fi> Message-ID: <201004162112.o3GLC17j025634@ruuvi.it.helsinki.fi> Replying to myself... > I've only just now spotted it that I had a NetRestrict on the new server > that had the "old" development IP address. So it has had a NetRestrict > that enabled two specific IP addresses, neither of which was the address > it is supposed to have, 128.214.58.174. Doh doh doh doh, it's midnight here and I shouldn't be messing with servers. NetRestrict _disables_ interfaces. NetInfo _enables_ them. NetInfo had 128.214.58.174 already, and NetRestrict correctly had 10.0.0.20 and 128.214.209.84. Now that the latter doesn't exist any more, I can safely remove it, but I shouldn't be *restricting* the server from using 128.214.58.174... NetInfo: 128.214.58.174 NetRestrict: 10.0.0.20 bos restart localhost -localauth -all :-) -- Atro Tossavainen (Mr.) / The Institute of Biotechnology at Systems Analyst, Techno-Amish & / the University of Helsinki, Finland, +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own. < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS From mdw@umich.edu Fri Apr 16 22:58:13 2010 From: mdw@umich.edu (Marcus Watts) Date: Fri, 16 Apr 2010 17:58:13 -0400 Subject: [OpenAFS] Re: Ubik problem In-Reply-To: <201004162107.o3GL712v025540@ruuvi.it.helsinki.fi> References: <201004162107.o3GL712v025540@ruuvi.it.helsinki.fi> Message-ID: Atro Tossavainen writes: > You "know" that? That's a misassumption at best. > > sun4x_58 # cksum /usr/afs/etc/KeyFile > 2143645127 100 /usr/afs/etc/KeyFile > > sunx86_510 # cksum /usr/afs/etc/KeyFile > 2143645127 100 /usr/afs/etc/KeyFile You say your software said "ticket contained unknown key version number" If it said that, a ticket that came from contained a key version number that doesn't match what's in it. Having said that, no, in fact, I said more than I should have. I should have said, "we know the key data isn't consistent". If there's any combination of "-localauth" that doesn't work, *then* I could correctly say the key files aren't consistent. *That* smoking gun hasn't been produced yet, and may not exist. What I *can* say is that the key data between your key files and your KA database is NOT consistent. (because you said: ka> exa useraccount examine: ticket contained unknown key version number getting information for useraccount. ) So, here's how to diagnose that. Try to reproduce these results: strawdogs-root# bos listkeys strawdogs -localauth key 3 has cksum 1207506455 key 4 has cksum 1508428935 key 0 has cksum 436464802 Keys last changed on Fri Apr 16 02:09:06 2010. All done. strawdogs-root# (do this for each of your hosts. since you claim your key files are identical, you *should* see the same results.) strawdogs-root# kas inter admin -server strawdogs Administrator's (admin) Password: ka> e afs User data for afs key (0) cksum is 436464802, last cpw: Fri Apr 16 02:06:44 2010 password will never expire. An unlimited number of unsuccessful authentications is permitted. entry never expires. Max ticket lifetime 100.00 hours. last mod on Fri Apr 16 02:06:44 2010 by permit password reuse ka> (do this for each of your hosts.) You'll only see one key for afs in each copy of ka. The key version and checksum should be the same on all servers. The cksum and kvno that appear that should match one entry in the keyfile. You might have other keys in your keyfile. I have multiple keys because one matches what I currently have in kerberos 5, and another is probably old junk. They won't matter to ka (well, except for ubik.) If one kadb contains a key in the keyfile, and other kadb's key is not in the keyfile, then whether you get a working ticket on any particular request is a 50% venture. If one host has ubik problems, then that's going to shift the odds. You ought to also be able to dump out kadb using "kadb_check". That's not going to work on your little endian machines. Since you have at least one big-endian machine, you could copy kadb to that host, run kadb_check there, and compare the output between your different servers. Once you've found a sane kaserver.DB*, you can move it out of the way and let ubik replicate it, or if you haven't fixed that, you can copy it over manually (when kaserver isn't running of course.) -Marcus Watts From atro.tossavainen+openafs@helsinki.fi Sat Apr 17 00:04:07 2010 From: atro.tossavainen+openafs@helsinki.fi (Atro Tossavainen) Date: Sat, 17 Apr 2010 02:04:07 +0300 (EEST) Subject: [OpenAFS] Re: Ubik problem In-Reply-To: Message-ID: <201004162304.o3GN47o4028512@ruuvi.it.helsinki.fi> > So, here's how to diagnose that. > > Try to reproduce these results: > > strawdogs-root# bos listkeys strawdogs -localauth The keys have the same cksums on both hosts and were last changed on the same date. This is hardly surprising since I copied the keyfiles over from the old server to the new server. > strawdogs-root# kas inter admin -server strawdogs > Administrator's (admin) Password: > ka> e afs The results are again identical and consistent between the two servers. > You'll only see one key for afs in each copy of ka. > The key version and checksum should be the same on all servers. The > cksum and kvno that appear that should match one entry in the keyfile. They do. > You ought to also be able to dump out kadb using "kadb_check". I've just unpacked a fresh copy of openafs-1.4.12-src.tar.bz2 and I don't see any files named 'kadb*' in the OpenAFS source tree. What am I missing? -- Atro Tossavainen (Mr.) / The Institute of Biotechnology at Systems Analyst, Techno-Amish & / the University of Helsinki, Finland, +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own. < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS From mdw@umich.edu Sat Apr 17 00:44:42 2010 From: mdw@umich.edu (Marcus Watts) Date: Fri, 16 Apr 2010 19:44:42 -0400 Subject: [OpenAFS] Re: Ubik problem In-Reply-To: <201004162304.o3GN47o4028512@ruuvi.it.helsinki.fi> References: <201004162304.o3GN47o4028512@ruuvi.it.helsinki.fi> Message-ID: > Date: Sat, 17 Apr 2010 02:04:07 +0300 > To: openafs-info@openafs.org > From: Atro Tossavainen > Subject: Re: [OpenAFS] Re: Ubik problem > > > So, here's how to diagnose that. > > > > Try to reproduce these results: > > > > strawdogs-root# bos listkeys strawdogs -localauth > > The keys have the same cksums on both hosts and were last changed > on the same date. This is hardly surprising since I copied the > keyfiles over from the old server to the new server. > > > strawdogs-root# kas inter admin -server strawdogs > > Administrator's (admin) Password: > > ka> e afs > > The results are again identical and consistent between the two servers. > > > You'll only see one key for afs in each copy of ka. > > The key version and checksum should be the same on all servers. The > > cksum and kvno that appear that should match one entry in the keyfile. > > They do. > > > You ought to also be able to dump out kadb using "kadb_check". > > I've just unpacked a fresh copy of openafs-1.4.12-src.tar.bz2 and > I don't see any files named 'kadb*' in the OpenAFS source tree. > What am I missing? > > -- > Atro Tossavainen (Mr.) / The Institute of Biotechnology at > Systems Analyst, Techno-Amish & / the University of Helsinki, Finland, > +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own. > < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info You should try doing this this again: $ kas -a dsakfksda Administrator's (dsakfksda) Password: ka> exa useraccount examine: ticket contained unknown key version number getting information for useraccount. If you get something different, congrats. You apparently fixed something. If you still get this, then there's something different between the path this went through, and what I suggested you check by hand above. Is your client talking to the right db hosts? Here's a wrinkle to consider: for almost everything, only the key of afs matters. For ka service, and its service ticket, "examine" uses something different, ka> e AuthServer.Admin User data for AuthServer.Admin (NOTGS+NOSEAL) key (1) cksum is 3726591373, last cpw: Fri Apr 16 01:59:52 2010 password will never expire. An unlimited number of unsuccessful authentications is permitted. entry never expires. Max ticket lifetime 10.00 hours. last mod on Fri Apr 16 01:59:52 2010 by permit password reuse ka> You might want to check that on each of your servers. I've no idea how this could get out of sync. Although... At one point, I think kaserver was capable of doing automatic rekeying for at least tgt. I can't find the logic in openafs today-- was this IBM only? So far as kadb_check goes, You didn't build and install it, did you? And you didn't try "find . -type f -print | xargs egrep kadb_check" Here's what you missed: in src/kauth/Makefile.in, find these lines: ${DEST}/etc/kadb_check: rebuild ${INSTALL} -f $? $@ ... ${DESTDIR}${afssrvsbindir}/kadb_check: rebuild ${INSTALL} -f $? $@ That says, take the binary "rebuild" (built from rebuild.c and other sources), and install it as "kadb_check". Yes, it's a bit strange. -Marcus Watts From haba@kth.se Sat Apr 17 14:31:27 2010 From: haba@kth.se (Harald Barth) Date: Sat, 17 Apr 2010 15:31:27 +0200 (CEST) Subject: [OpenAFS] OpenAFS algorithm In-Reply-To: <4BC898A8.5010006@secure-endpoints.com> References: <4BC86CED.8020001@kezia.com> <20100416.181622.166956551.haba@habanero.pdc.kth.se> <4BC898A8.5010006@secure-endpoints.com> Message-ID: <20100417.153127.248095159.haba@habanero.pdc.kth.se> > OpenAFS clients on Windows since last Fall have implemented the > results of Jake Thebault-Spieker's GSoC project that computes the > server preferences based upon the observed round trip times measured > for each server instance. Sorry, I had a Unix-narrow mind =:-) > Jake is working on an implementation for the UNIX clients. We like! There are bandwidth measuring counters in Arla but they were never used to set any priorities automatically. Harald. From crestani@informatik.uni-tuebingen.de Tue Apr 6 07:04:06 2010 From: crestani@informatik.uni-tuebingen.de (Marcus Crestani) Date: Tue, 06 Apr 2010 08:04:06 +0200 Subject: [OpenAFS] Documentation for Preference Pane in 1.4.12 on MacOSX Message-ID: I have trouble getting the new maintenance release 1.4.12 working properly on MacOSX 10.6.3. We use Kerberos 5 to authenticate and our user's homes are stored in AFS, so we need to get a Token at login time. We have a working setup with OpenAFS 1.4.11 that obtains a Kerberos Ticket during login and uses the loginwindow's LoginHook to convert the Kerberos Ticket to an AFS Token. After I've installed 1.4.12, this does not seem work any longer. On a first login attempt, I do not get an token at login time. To get one, I have to logout and login again. But then, the Finder process stalls for a couple of minutes with a spinning wheel. Something is terribly wrong here. I have the feeling that the new Preference Pane and our previous solution do not work together. To understand what happens, I could use some insight on the new Preference Pane. Is there some documentation? Especially, it would be useful to have answers to the following questions: - What is the purpose of the "Backgrounder" Launch Agent it.infn.lnf.network.AFSBackgrounder.plist? How is it connected to the Preference Pane? - Where does the Preference Pane store its settings? - What happens in the background when I check/uncheck the several options like "Get Krb5 credential at login", "Use aklog", "get credential at login time", "Backgrounder"? - Where does the stuff under the "Parameter" tab get stored? How does the AFS startup get these values? I'd appreciate any help, either ideas concerning my described problems or answers to my questions that should help me figuring things out. Please CC me, since I am not subscribed on the list. Thanks in advance! -- Marcus From adeason@sinenomine.net Sat Apr 17 21:04:30 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Sat, 17 Apr 2010 15:04:30 -0500 Subject: [OpenAFS] Re: Ubik problem References: <20100416113841.cefbbded.adeason@sinenomine.net> <201004162051.o3GKpYnt025100@ruuvi.it.helsinki.fi> Message-ID: <20100417150430.a659af87.adeason@sinenomine.net> On Fri, 16 Apr 2010 23:51:34 +0300 (EEST) Atro Tossavainen wrote: > I figured I'd just throw all other servers on in the the sunx86_510 > "development" box, change the IP address, vos changeaddr, done. I know it's not intuitive, but 'vos changeaddr' should not be used to change fileserver addresses for modern fileservers. A fileserver will detect its addresses on startup and will register those addresses with the VLDB; so if you just move the fileserver and start it, the VLDB will know about the new addresses. changeaddr can screw stuff up (though it's not going to cause ubik being weird like you're seeing) There is a new command, 'vos setaddrs', to change fileserver addresses in the VLDB without restarting them, but that's new in 1.5. And you shouldn't need such a thing most of the time anyway. -- Andrew Deason adeason@sinenomine.net From shadow@gmail.com Mon Apr 19 04:04:00 2010 From: shadow@gmail.com (Derrick Brashear) Date: Sun, 18 Apr 2010 23:04:00 -0400 Subject: [OpenAFS] Missing AFS Client tabs? In-Reply-To: References: <4BC7B25E.6000705@secure-endpoints.com> <4BC8A5B0.5010106@secure-endpoints.com> Message-ID: On Fri, Apr 16, 2010 at 2:07 PM, Ted Creedon wrot= e: > The windows documentation shows the 3 tabs.. Can you offer a URL? (note, if the url is openafs.org, that's not Windows documentation; That's AFS documentation. Read again what he said) > On Fri, Apr 16, 2010 at 11:00 AM, Jeffrey Altman > wrote: >> >> On 4/16/2010 1:25 PM, Ted Creedon wrote: >> > Except I don't know the procedure to map drives... >> > >> > Ted >> >> How to map drives is discussed in your Windows documentation. =A0You map >> drives to \\AFS exactly the same way you map drives to any other UNC >> path on Windows. =A0Note that the release notes for OpenAFS for Windows >> have stated for many years now that drive mapping should be performed >> using the Explorer shell. >> >> Jeffrey Altman >> > > --=20 Derrick From fcombernous@kezia.com Mon Apr 19 08:30:24 2010 From: fcombernous@kezia.com (Fabien COMBERNOUS) Date: Mon, 19 Apr 2010 09:30:24 +0200 Subject: [OpenAFS] OpenAFS algorithm In-Reply-To: <20100416.181622.166956551.haba@habanero.pdc.kth.se> References: <4BC86CED.8020001@kezia.com> <20100416.181622.166956551.haba@habanero.pdc.kth.se> Message-ID: <4BCC0690.5090601@kezia.com> Thank you for your input. Harald Barth wrote: >> My question is how to permit client in B to use server in B ? I >> didn't found any document explaining the algorithm used by OpenAFS >> to decide the server contacted by the client. >> > > The algoritm is very old and if your IP numbers do not reflect your > network topology it probably yields incorrect results. > What do you meens by an IP number do not reflect the network topology ? > Have a look at man fs_setserverprefs and man fs_getserverprefs > I already tried to play with. but without any result. > a lower value indicates a greater preference > > but first check that the clients really knows that there is more than one copy (something like this): > > $ fs where /afs/pdc.kth.se/home/ > File /afs/pdc.kth.se/home/ is on hosts kinilaw.pdc.kth.se morena.pdc.kth.se sculpin.pdc.kth.se houting.pdc.kth.se > The fs where command report me that the path is hosted only on one server. But i have a RO copy on the two servers. How to use the local copy ? > As my list from fs gets is quite long, I came up with this to find out > which one should be the prefered server: > > $ fs gets | awk '$1 ~ "'$(echo $(fs where /afs/pdc.kth.se/home/ | awk -Fhosts\ '{print $2}') | sed "s/\ /|/g")'"' | sort +1 -2n > My fs gets retyurn the two servers. And in the office B the server B is with priority 54, server A is with priority 30001. -- *Fabien COMBERNOUS* /unix system engineer/ www.kezia.com *Tel: +33 (0) 467 992 986* Kezia Group From fcombernous@kezia.com Mon Apr 19 08:43:47 2010 From: fcombernous@kezia.com (Fabien COMBERNOUS) Date: Mon, 19 Apr 2010 09:43:47 +0200 Subject: [OpenAFS] Documentation for Preference Pane in 1.4.12 on MacOSX In-Reply-To: References: Message-ID: <4BCC09B3.80609@kezia.com> Marcus Crestani wrote: > I have trouble getting the new maintenance release 1.4.12 working > properly on MacOSX 10.6.3. We use Kerberos 5 to authenticate and our > user's homes are stored in AFS, so we need to get a Token at login time. > We have a working setup with OpenAFS 1.4.11 that obtains a Kerberos > Ticket during login and uses the loginwindow's LoginHook to convert the > Kerberos Ticket to an AFS Token. > > After I've installed 1.4.12, this does not seem work any longer. On a > first login attempt, I do not get an token at login time. To get one, I > have to logout and login again. But then, the Finder process stalls for > a couple of minutes with a spinning wheel. Something is terribly wrong > here. I have the feeling that the new Preference Pane and our previous > solution do not work together. > I tested OpenAFS 1.4.12 only with MacOSX 10.5.8. It is running like a charm. I also tested OpenAFS 1.5.73 with MacOSX 1.6.3. It is also running like a charm. Sorry but i didn't meet any issue like yours. > To understand what happens, I could use some insight on the new > Preference Pane. Is there some documentation? Especially, it would be > useful to have answers to the following questions: > > - What is the purpose of the "Backgrounder" Launch Agent > it.infn.lnf.network.AFSBackgrounder.plist? How is it connected to the > Preference Pane? > > - Where does the Preference Pane store its settings? > > - What happens in the background when I check/uncheck the several > options like "Get Krb5 credential at login", "Use aklog", "get > credential at login time", "Backgrounder"? > > - Where does the stuff under the "Parameter" tab get stored? How does > the AFS startup get these values? > > I'd appreciate any help, either ideas concerning my described problems > or answers to my questions that should help me figuring things out. > > Please CC me, since I am not subscribed on the list. Thanks in advance! > > To answer to many of our questions, you can use fseventer tool [1]. It is a useful free closed source software to know the files modified and/or created by a GUI on MacOSX. I planed to do it by myself, but i didn't yet have enough time. Best regards, [1] http://www.fernlightning.com/doku.php?id=software:fseventer:start -- *Fabien COMBERNOUS* /unix system engineer/ www.kezia.com *Tel: +33 (0) 467 992 986* Kezia Group From haba@kth.se Mon Apr 19 10:27:35 2010 From: haba@kth.se (Harald Barth) Date: Mon, 19 Apr 2010 11:27:35 +0200 (CEST) Subject: [OpenAFS] OpenAFS algorithm In-Reply-To: <4BCC0690.5090601@kezia.com> References: <4BC86CED.8020001@kezia.com> <20100416.181622.166956551.haba@habanero.pdc.kth.se> <4BCC0690.5090601@kezia.com> Message-ID: <20100419.112735.234659640.haba@habanero.pdc.kth.se> Everything I will say should probably end with the sentence "and on Windows it might work differently". > What do you meens by an IP number do not reflect the network topology ? If your server is on A.B.C.X and your client on A.B.C.Y, it should work automatically, otherwise not. > > $ fs where /afs/pdc.kth.se/home/ > > File /afs/pdc.kth.se/home/ is on hosts kinilaw.pdc.kth.se morena.pdc.kth.se sculpin.pdc.kth.se houting.pdc.kth.se > The fs where command report me that the path is hosted only on one > server. But i have a RO copy on the two servers. How to use the > local copy ? If only one server is reported from the fs where command your client has probably not figured out that there is another one. Does "fs where /afs/pdc.kth.se/home/" give you the same result as I get? (your Internet connection may hinder you from testing that). Have you tried things like "fs checkv" or "fs checks"? Any error message about not being able to contact the server in the kernel log? > My fs gets retyurn the two servers. And in the office B the server B is with priority 54, server A is with priority 30001. 54 looks like set by hand. 30001 looks like an automatically assigned value. But if the client does not know that there are two RO, it does not use the priorities. Harald. From jaltman@secure-endpoints.com Mon Apr 19 11:33:16 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Mon, 19 Apr 2010 11:33:16 +0100 Subject: [OpenAFS] Missing AFS Client tabs? In-Reply-To: References: <4BC7B25E.6000705@secure-endpoints.com> <4BC8A5B0.5010106@secure-endpoints.com> Message-ID: <4BCC316C.9010103@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms030707060601090306010005 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/19/2010 4:04 AM, Derrick Brashear wrote: > On Fri, Apr 16, 2010 at 2:07 PM, Ted Creedon = wrote: >> The windows documentation shows the 3 tabs.. >=20 > Can you offer a URL? > (note, if the url is openafs.org, that's not Windows documentation; > That's AFS documentation. Read again what he said) I suspect that Ted is referring to the Windows Quick Start Guide which is part of the wiki. http://www.dementia.org/twiki/bin/view/AFSLore/WindowsEndUserQuickStartGu= ide As such, anyone that requests a wiki account can edit it. Jeffrey Altman --------------ms030707060601090306010005 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MTkxMDMzMTZaMCMGCSqGSIb3DQEJBDEWBBTzFWeA 4/pn1m+taeMU3cf7UUroyDBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAAqx/kRrfZd/PIOl9XfmZXpUFjfgDt1szHFs lxFC77qkIvoycJiFDaf9k9e/fbsm8RL8VNGExExLUBhDBUN5PcBp7SvxYdffzJMVrnS5JG4+ LV23BNTxYf45/6uWCLX3RuVx4f5jjzZomeQDcXCcDWYnSPwLPzH2iYv5TRS3cRDXHvEmhhEY 1NXUCJmyxKeX4j4XYCxK6If4A74z8tR/K3wUH3eG2vwnyfe6L/wMFnya25Fvr4KgWz1SZ/ca fTSujZiradTC6BK0B7FPJEiihD5MFEtMiwIMS9lcUS543i0yv14QyeSkVShEJnXttLsWnK/U 2NWBA20uxyDBx38siHMAAAAAAAA= --------------ms030707060601090306010005-- From haba@kth.se Mon Apr 19 14:23:25 2010 From: haba@kth.se (Harald Barth) Date: Mon, 19 Apr 2010 15:23:25 +0200 (CEST) Subject: [OpenAFS] SRPMs for the RPMs Message-ID: <20100419.152325.168973235.haba@habanero.pdc.kth.se> To every kind soul making RPMs (or other packages): I would appreciate if the SRPMs (or equivalent) would be available alongside the binaries. Because if I can not recreate the RPMs from scratch I as well should make my own. Currently I'm most interrested in the SuSE 11.2 ones, but the RHEL ones will be in the future, too. Thanks, Harald. From tcreedon@easystreet.net Mon Apr 19 14:51:41 2010 From: tcreedon@easystreet.net (Ted Creedon) Date: Mon, 19 Apr 2010 06:51:41 -0700 Subject: [OpenAFS] Re: [OpenAFS-Doc] Forwarded documentation rant In-Reply-To: <201004191335.o3JDZRb3013043@thirdoffive.cmf.nrl.navy.mil> References: <4BCB8E43.8030102@secure-endpoints.com> <201004191335.o3JDZRb3013043@thirdoffive.cmf.nrl.navy.mil> Message-ID: --001636e1f7acb74b2b0484974237 Content-Type: text/plain; charset=ISO-8859-1 I had the old IBM docs converted to LaTex several years ago. I published the Quick Start with switches for Linux, Unix, etc. in quarto handbook form (4 pages/sheet). and made myself a pocket book. Forgotten is all the sophisticated forward and reverse cross referencing and page numbering and chapter/section pointers. On Mon, Apr 19, 2010 at 6:35 AM, Chas Williams (CONTRACTOR) < chas@cmf.nrl.navy.mil> wrote: > In message <4BCB8E43.8030102@secure-endpoints.com>,Jeffrey Altman writes: > >into a source form (including consistent formatting and > >indexing) that could be used by contributors to submit > >changes. All of the documentation that we have is now > >in DocBook format and the man pages are in Perl POD format. > ... > >It has only been in the 18 months that the XML sources > >have been available in this easy to edit form. It has > >been my hope that with the improved source format availability > >that a broader range of users and administrators would > >contribute to the depth, breadth, and usability of the > >available documentation. > > the formatting isnt entirely consistent. it is close however. it was > inconsistent in the original html, i tried to correct it somewhat in > the xml but alas i am only a human. someone really needs to write (and > i was going to do it) a document that decribes what tags should be used > in the various examples. > > other projects have similar style guides and i really think it would help > people out. learning docbook is pretty easy but applying it consistently > is not easy. > > on a general note, people might be intimidated by the sheer volume of > documentation. usually, it is not enough documentation when it comes > to open source projects. openafs is one of the few to my knowledge that > actually has a pretty complete set of documentation. some of the docs > are outdated now, but at one point is was correct and consistent. > _______________________________________________ > OpenAFS-doc mailing list > OpenAFS-doc@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-doc > --001636e1f7acb74b2b0484974237 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I had the old IBM docs converted to LaTex several years ago.

I publi= shed the Quick Start with switches for Linux, Unix, etc. in quarto handbook= form (4 pages/sheet). and made myself a pocket book.

Forgotten is a= ll the sophisticated forward and reverse cross referencing and page numberi= ng and chapter/section pointers.


On Mon, Apr 19, 2010 at 6:35 AM, Chas Wi= lliams (CONTRACTOR) <chas@cmf.nrl.navy.mil> wrote:
In message <4BCB8E43.8030102@secure-endpoints.com>,Jeffrey Altman= writes:
>into a source form (including consistent formatting and
>indexing) that could be used by contributors to submit
>changes. =A0All of the documentation that we have is now
>in DocBook format and the man pages are in Perl POD format.
...
>It has only been in the 18 months that the XML source= s
>have been available in this easy to edit form. =A0It has
>been my hope that with the improved source format availability
>that a broader range of users and administrators would
>contribute to the depth, breadth, and usability of the
>available documentation.

the formatting isnt entirely consistent. =A0it is close however. =A0i= t was
inconsistent in the original html, i tried to correct it somewhat in
the xml but alas i am only a human. =A0someone really needs to write (and i was going to do it) a document that decribes what tags should be used
in the various examples.

other projects have similar style guides and i really think it would help people out. =A0learning docbook is pretty easy but applying it consistently=
is not easy.

on a general note, people might be intimidated by the sheer volume of
documentation. =A0usually, it is not enough documentation when it comes
to open source projects. =A0openafs is one of the few to my knowledge that<= br> actually has a pretty complete set of documentation. =A0some of the docs are outdated now, but at one point is was correct and consistent.
_________________________________________= ______
OpenAFS-doc mailing list
OpenAFS-doc@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-doc

--001636e1f7acb74b2b0484974237-- From shadow@gmail.com Mon Apr 19 15:27:14 2010 From: shadow@gmail.com (Derrick Brashear) Date: Mon, 19 Apr 2010 10:27:14 -0400 Subject: [OpenAFS] SRPMs for the RPMs In-Reply-To: <20100419.152325.168973235.haba@habanero.pdc.kth.se> References: <20100419.152325.168973235.haba@habanero.pdc.kth.se> Message-ID: the ideal situation is we'd just use the one srpm already available from openafs.org for the release. On Mon, Apr 19, 2010 at 9:23 AM, Harald Barth wrote: > > To every kind soul making RPMs (or other packages): I would appreciate > if the SRPMs (or equivalent) would be available alongside the > binaries. Because if I can not recreate the RPMs from scratch I as > well should make my own. Currently I'm most interrested in the SuSE > 11.2 ones, but the RHEL ones will be in the future, too. > > Thanks, > Harald. > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info > -- Derrick From chas@cmf.nrl.navy.mil Mon Apr 19 15:29:46 2010 From: chas@cmf.nrl.navy.mil (Chas Williams (CONTRACTOR)) Date: Mon, 19 Apr 2010 10:29:46 -0400 Subject: [OpenAFS] Re: [OpenAFS-Doc] Forwarded documentation rant In-Reply-To: Message-ID: <201004191429.o3JETkGd016413@thirdoffive.cmf.nrl.navy.mil> In message ,Ted Creedon writes: >Forgotten is all the sophisticated forward and reverse cross referencing and >page numbering and chapter/section pointers. it is still there. btw, you cant reference by page numbers. this is a very strange idea. different media is going to have different page numbers. references inside the admin reference manual were lost though. however, that documents has changed enough that it probably wasnt very correct. From haba@kth.se Mon Apr 19 16:10:42 2010 From: haba@kth.se (Harald Barth) Date: Mon, 19 Apr 2010 17:10:42 +0200 (CEST) Subject: [OpenAFS] SRPMs for the RPMs In-Reply-To: References: <20100419.152325.168973235.haba@habanero.pdc.kth.se> Message-ID: <20100419.171042.124521600.haba@habanero.pdc.kth.se> > the ideal situation is we'd just use the one srpm already available > from openafs.org for the release. This would be preferable, but for example my RPM packaging skills are not that good to write the prereqs depending on the distro and version. The distros do have different names on the packages. So I prefer to get the SRPM that gets produced alongside the RPM in the rpmbuild process until we get to the unified RPM nirvana. Harald. From ktdreyer@ktdreyer.com Mon Apr 19 16:41:06 2010 From: ktdreyer@ktdreyer.com (Ken Dreyer) Date: Mon, 19 Apr 2010 09:41:06 -0600 Subject: [OpenAFS] experience of SQLite on AFS Message-ID: Thought I would add another datapoint to the discussion of SQLite on AFS. We have several Solaris 10 servers running OpenAFS client 1.4.x and PHP 5.2.x. We really wanted to get PHP's PDO-SQLite extension working with AFS. (PHP bundles SQLite 3.3.x). We anticipate that most of our uses would be read-only, but a few applications would need to make occasional INSERTs and so on. SQLite has an option in os_unix.c (SQLITE_ENABLE_LOCKING_STYLE) to automatically figure out the database's filesystem type and use the most appropriate locking mechanism for that filesystem. Adam Megacz wrote a patch to SQLite back in 2006 that added AFS to this list of filesystems SQLite could detect. I'm not certain, but I think this only works for OSX (Adam, correct me if I'm wrong :-) Additionally, SQLite also has the (undocumented?) ability to define a fixed locking style at compile-time with SQLITE_FIXED_LOCKING_STYLE. This is the variable that we manipulated in our tests when we compiled PDO-SQLite. fnctl - Byte-range locking. Since we're using OpenAFS 1.4, this pretends to work but actually doesn't lock anything. flock - Whole-file locking. This completely hung on Solaris when opening sqlite files on read-only mounts. Even if the SQLite operations were read-only (SELECT, etc), PHP hung. dot-lock - did not work, as SQLite wanted to write dot-files to our read-only mounts. no locks - worked I did not expect the flock-style locking to hang when opening files that were mounted read-only, but it was 100% repeatable. We figured that read-access was better than nothing, so we use no locks currently and warn our PHP developers. We hope we can make use of byte-range locking some day when OpenAFS supports this on *nix. - Ken From shadow@gmail.com Mon Apr 19 17:01:05 2010 From: shadow@gmail.com (Derrick Brashear) Date: Mon, 19 Apr 2010 12:01:05 -0400 Subject: [OpenAFS] experience of SQLite on AFS In-Reply-To: References: Message-ID: On Mon, Apr 19, 2010 at 11:41 AM, Ken Dreyer wrote: > Thought I would add another datapoint to the discussion of SQLite on AFS. > > We have several Solaris 10 servers running OpenAFS client 1.4.x and > PHP 5.2.x. We really wanted to get PHP's PDO-SQLite extension working > with AFS. (PHP bundles SQLite 3.3.x). We anticipate that most of our > uses would be read-only, but a few applications would need to make > occasional INSERTs and so on. > > SQLite has an option in os_unix.c (SQLITE_ENABLE_LOCKING_STYLE) to > automatically figure out the database's filesystem type and use the > most appropriate locking mechanism for that filesystem. Adam Megacz > wrote a patch to SQLite back in 2006 that added AFS to this list of > filesystems SQLite could detect. I'm not certain, but I think this > only works for OSX (Adam, correct me if I'm wrong :-) > > Additionally, SQLite also has the (undocumented?) ability to define a > fixed locking style at compile-time with SQLITE_FIXED_LOCKING_STYLE. > This is the variable that we manipulated in our tests when we compiled > PDO-SQLite. > > fnctl - Byte-range locking. Since we're using OpenAFS 1.4, this > pretends to work but actually doesn't lock anything. > flock - Whole-file locking. This completely hung on Solaris when > opening sqlite files on read-only mounts. Even if the SQLite > operations were read-only (SELECT, etc), PHP hung. > dot-lock - did not work, as SQLite wanted to write dot-files to our > read-only mounts. > no locks - worked > > I did not expect the flock-style locking to hang when opening files > that were mounted read-only, but it was 100% repeatable. cmdebug output? truss output? something? can i suggest trying it on a directory where you have rlk and not merely rl? > We figured > that read-access was better than nothing, so we use no locks currently > and warn our PHP developers. We hope we can make use of byte-range > locking some day when OpenAFS supports this on *nix. -- Derrick From adeason@sinenomine.net Mon Apr 19 17:55:12 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Mon, 19 Apr 2010 11:55:12 -0500 Subject: [OpenAFS] Re: experience of SQLite on AFS References: Message-ID: <20100419115512.861a1fb3.adeason@sinenomine.net> On Mon, 19 Apr 2010 09:41:06 -0600 Ken Dreyer wrote: > fnctl - Byte-range locking. Since we're using OpenAFS 1.4, this > pretends to work but actually doesn't lock anything. > flock - Whole-file locking. This completely hung on Solaris when > opening sqlite files on read-only mounts. Even if the SQLite > operations were read-only (SELECT, etc), PHP hung. > dot-lock - did not work, as SQLite wanted to write dot-files to our > read-only mounts. > no locks - worked Er, by 'read-only mounts' you do mean directories where you only have read permissions, right? Not mounting RO volumes? -- Andrew Deason adeason@sinenomine.net From jaltman@secure-endpoints.com Mon Apr 19 17:55:24 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Mon, 19 Apr 2010 17:55:24 +0100 Subject: [OpenAFS] experience of SQLite on AFS In-Reply-To: References: Message-ID: <4BCC8AFC.5000706@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms040706050103020009050405 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/19/2010 4:41 PM, Ken Dreyer wrote: > Thought I would add another datapoint to the discussion of SQLite on AF= S. >=20 > We have several Solaris 10 servers running OpenAFS client 1.4.x and > PHP 5.2.x. We really wanted to get PHP's PDO-SQLite extension working > with AFS. (PHP bundles SQLite 3.3.x). We anticipate that most of our > uses would be read-only, but a few applications would need to make > occasional INSERTs and so on. >=20 > SQLite has an option in os_unix.c (SQLITE_ENABLE_LOCKING_STYLE) to > automatically figure out the database's filesystem type and use the > most appropriate locking mechanism for that filesystem. Adam Megacz > wrote a patch to SQLite back in 2006 that added AFS to this list of > filesystems SQLite could detect. I'm not certain, but I think this > only works for OSX (Adam, correct me if I'm wrong :-) >=20 > Additionally, SQLite also has the (undocumented?) ability to define a > fixed locking style at compile-time with SQLITE_FIXED_LOCKING_STYLE. > This is the variable that we manipulated in our tests when we compiled > PDO-SQLite. >=20 > fnctl - Byte-range locking. Since we're using OpenAFS 1.4, this > pretends to work but actually doesn't lock anything. > flock - Whole-file locking. This completely hung on Solaris when > opening sqlite files on read-only mounts. Even if the SQLite > operations were read-only (SELECT, etc), PHP hung. > dot-lock - did not work, as SQLite wanted to write dot-files to our > read-only mounts. > no locks - worked >=20 > I did not expect the flock-style locking to hang when opening files > that were mounted read-only, but it was 100% repeatable. We figured > that read-access was better than nothing, so we use no locks currently > and warn our PHP developers. We hope we can make use of byte-range > locking some day when OpenAFS supports this on *nix. >=20 > - Ken Ken: It would be very helpful if you could repeat these tests with flock and file a bug report to openafs-bugs@openafs.org with the details of the deadlock. It is only be receiving a bug report that we will know that there is a problem that needs to be fixed. Thank you. Jeffrey Altman --------------ms040706050103020009050405 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MTkxNjU1MjRaMCMGCSqGSIb3DQEJBDEWBBQwOZ9Q KGSRumUzETqvGlrKgPnRfDBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAGRAHwAalHJmWIkwkb39Dk5OKopLE964niHj c+DXhOHUNvpAWtjeI/v9OWOTLvhGVwyTsdGxCAeDKURgn79IHf3YwxBFPuzng04Um5r8n9f0 MZg11MlQt2SVUdXIfFcKy3hnpHv0vOxl14P7dtvYSDRnIV4/mCDgu2Uhr+1DtGisJk+sErG+ WIKTcGg0F8coGB/oMzslHiFGiRyBL/OoesZRi/maZBIfa5tEHSFdiiPYuo9t3fXPI3dqoJhu 9VluGyj89F/J7qe9LQvIbR+AF7LaEI0IaEhgQWr2EMK+ac4StL28tGByIoqdiXF1kw4u9xbo i5QN8/IjjgqH7KVgKqAAAAAAAAA= --------------ms040706050103020009050405-- From rra@stanford.edu Mon Apr 19 20:08:14 2010 From: rra@stanford.edu (Russ Allbery) Date: Mon, 19 Apr 2010 12:08:14 -0700 Subject: [OpenAFS] Re: [OpenAFS-Doc] Forwarded documentation rant In-Reply-To: <201004191429.o3JETkGd016413@thirdoffive.cmf.nrl.navy.mil> (Chas Williams's message of "Mon, 19 Apr 2010 10:29:46 -0400") References: <201004191429.o3JETkGd016413@thirdoffive.cmf.nrl.navy.mil> Message-ID: <878w8jclb5.fsf@windlord.stanford.edu> "Chas Williams (CONTRACTOR)" writes: > it is still there. btw, you cant reference by page numbers. this is > a very strange idea. different media is going to have different page > numbers. references inside the admin reference manual were lost though. > however, that documents has changed enough that it probably wasnt very > correct. POD is capable of including enough information that you could get them back, and most of the high-level references are still there. The low-level references (to specific sections of particular pieces of documentation) would need additional annotations. Some work on the generation scripts to get more of the references to hyperlink properly would be good, as would some investigation of currently available POD formatters to see which ones would give the best cross-referenced printable output. On the other hand, I'm not sure how large the audience is for that work any more. Printing things like this out has I think become a lot less common over the years. That's one of the reasons why our original focus was on turning the reference guide into man pages; on our UNIX-like platforms, that's a far more common documentation access method than printed or printable manuals. -- Russ Allbery (rra@stanford.edu) From Coy.Hile@COYHILE.COM Mon Apr 19 21:28:51 2010 From: Coy.Hile@COYHILE.COM (Coy Hile) Date: Mon, 19 Apr 2010 20:28:51 +0000 Subject: [OpenAFS] Re: [OpenAFS-Doc] Forwarded documentation rant In-Reply-To: <878w8jclb5.fsf@windlord.stanford.edu> References: <201004191429.o3JETkGd016413@thirdoffive.cmf.nrl.navy.mil>,<878w8jclb5.fsf@windlord.stanford.edu> Message-ID: <8BF1A686A4943A4BB60A42B82FFFD31C01014C@EXCHANGE01.VAS.COYHILE.COM> I for one find for some things like the sorts of docs that are the admin gu= ide/admin ref/etc, that having printable copies works well. Maybe I'm jus= t a curmudgeon, though. (No need for comments from the peanut gallery on th= at one :)) ________________________________________ From: openafs-info-admin@openafs.org [openafs-info-admin@openafs.org] on be= half of Russ Allbery [rra@stanford.edu] Sent: Monday, April 19, 2010 3:08 PM To: openafs-info@openafs.org Subject: Re: [OpenAFS] Re: [OpenAFS-Doc] Forwarded documentation rant "Chas Williams (CONTRACTOR)" writes: > it is still there. btw, you cant reference by page numbers. this is > a very strange idea. different media is going to have different page > numbers. references inside the admin reference manual were lost though. > however, that documents has changed enough that it probably wasnt very > correct. POD is capable of including enough information that you could get them back, and most of the high-level references are still there. The low-level references (to specific sections of particular pieces of documentation) would need additional annotations. Some work on the generation scripts to get more of the references to hyperlink properly would be good, as would some investigation of currently available POD formatters to see which ones would give the best cross-referenced printable output. On the other hand, I'm not sure how large the audience is for that work any more. Printing things like this out has I think become a lot less common over the years. That's one of the reasons why our original focus was on turning the reference guide into man pages; on our UNIX-like platforms, that's a far more common documentation access method than printed or printable manuals. -- Russ Allbery (rra@stanford.edu) _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info= From chas@cmf.nrl.navy.mil Mon Apr 19 20:41:15 2010 From: chas@cmf.nrl.navy.mil (Chas Williams (CONTRACTOR)) Date: Mon, 19 Apr 2010 15:41:15 -0400 Subject: [OpenAFS] Re: [OpenAFS-Doc] Forwarded documentation rant In-Reply-To: <878w8jclb5.fsf@windlord.stanford.edu> Message-ID: <201004191941.o3JJfFRf027843@thirdoffive.cmf.nrl.navy.mil> In message <878w8jclb5.fsf@windlord.stanford.edu>,Russ Allbery writes: >POD is capable of including enough information that you could get them >back, and most of the high-level references are still there. The >low-level references (to specific sections of particular pieces of >documentation) would need additional annotations. yes, pod is but i dont believe any of the linkage tags where preserved when the documentation was converted over from the .html. i have dreams of re-doing the conversion to get the links and diff between the two trees to put the links back. >On the other hand, I'm not sure how large the audience is for that work >any more. Printing things like this out has I think become a lot less which is why i think the cross references between the man pages is somewhat useful. when formatted as html it makes is easier to go see the reference command -- just follow the link. however, i dont recall how much there was. this would sort of determine whether or not this would even be worth the effort. From rra@stanford.edu Mon Apr 19 21:14:46 2010 From: rra@stanford.edu (Russ Allbery) Date: Mon, 19 Apr 2010 13:14:46 -0700 Subject: [OpenAFS] Re: [OpenAFS-Doc] Forwarded documentation rant In-Reply-To: <201004191941.o3JJfFRf027843@thirdoffive.cmf.nrl.navy.mil> (Chas Williams's message of "Mon, 19 Apr 2010 15:41:15 -0400") References: <201004191941.o3JJfFRf027843@thirdoffive.cmf.nrl.navy.mil> Message-ID: <87mxwzb3nt.fsf@windlord.stanford.edu> "Chas Williams (CONTRACTOR)" writes: > which is why i think the cross references between the man pages is > somewhat useful. when formatted as html it makes is easier to go > see the reference command -- just follow the link. however, i dont > recall how much there was. this would sort of determine whether or > not this would even be worth the effort. That is all there in the current POD and conversion for anything that's marked with L<> properly. Nearly all of the SEE ALSO sections should be good. The inline text links are much more hit and miss, unfortunately. -- Russ Allbery (rra@stanford.edu) From christof.hanke@rzg.mpg.de Mon Apr 19 21:36:26 2010 From: christof.hanke@rzg.mpg.de (Christof Hanke) Date: Mon, 19 Apr 2010 22:36:26 +0200 Subject: [OpenAFS] SRPMs for the RPMs In-Reply-To: <20100419.171042.124521600.haba@habanero.pdc.kth.se> References: <20100419.152325.168973235.haba@habanero.pdc.kth.se> <20100419.171042.124521600.haba@habanero.pdc.kth.se> Message-ID: <201004192236.26880.christof.hanke@rzg.mpg.de> Am Montag, 19. April 2010 17:10:42 schrieb Harald Barth: > > the ideal situation is we'd just use the one srpm already available > > from openafs.org for the release. > Agreed, but there is some more work to do for this. > This would be preferable, but for example my RPM packaging skills are > not that good to write the prereqs depending on the distro and > version. The distros do have different names on the packages. So I > prefer to get the SRPM that gets produced alongside the RPM in the > rpmbuild process until we get to the unified RPM nirvana. > You get the srpm at http://download.opensuse.org/repositories/filesystems/openSUSE_11.2/src/openafs-1.4.12-6.6.src.rpm Christof From ktdreyer@ktdreyer.com Mon Apr 19 21:51:28 2010 From: ktdreyer@ktdreyer.com (Ken Dreyer) Date: Mon, 19 Apr 2010 14:51:28 -0600 Subject: [OpenAFS] Re: experience of SQLite on AFS In-Reply-To: <20100419115512.861a1fb3.adeason@sinenomine.net> References: <20100419115512.861a1fb3.adeason@sinenomine.net> Message-ID: --0016363b8f00077ed704849d2025 Content-Type: text/plain; charset=UTF-8 On Mon, Apr 19, 2010 at 10:55 AM, Andrew Deason wrote: > On Mon, 19 Apr 2010 09:41:06 -0600 > Ken Dreyer wrote: >> flock - Whole-file locking. This completely hung on Solaris when >> opening sqlite files on read-only mounts. Even if the SQLite >> operations were read-only (SELECT, etc), PHP hung. >> dot-lock - did not work, as SQLite wanted to write dot-files to our >> read-only mounts. > > Er, by 'read-only mounts' you do mean directories where you only have > read permissions, right? Not mounting RO volumes? I meant the latter. We need SQLite to be able to read from RO volumes, and read/write to RW volumes. With SQLITE_FIXED_LOCKING_STYLE=flockLockingStyle I can read and write to RW volumes, but any operation on an SQLite file in a RO volume hangs. At first I wondered if this was a problem with *all* flock() calls on RO volumes, but I wrote two test programs (C and PHP, attached) to do a simple shared lock with flock(), and these work on RO and RW volumes. This makes me think that the problem may be with SQLite's code, or PHP's use of SQLite. With these test results, I was hesitant to open a bug with OpenAFS yet. On Mon, Apr 19, 2010 at 10:01 AM, Derrick Brashear wrote: > can i suggest trying it on a directory where you have rlk and not merely rl? The ACLs were one of the first things I looked at, but "k" seemed to have no effect. I will try to build SQLite aside from PHP to see if I can narrow the problem further. I'll try to provide backtraces / cmdebug too, when I can pull them together. - Ken --0016363b8f00077ed704849d2025 Content-Type: text/x-csrc; charset=US-ASCII; name="lock.c" Content-Disposition: attachment; filename="lock.c" Content-Transfer-Encoding: base64 X-Attachment-Id: f_g87ptfj90 LyoKICogYnVpbHQgb24gU29sYXJpcyB3aXRoCiAqIGdjYyAtTC91c3IvdWNibGliLyAtUi91c3Iv dWNibGliLyAtZyBsb2NrLmMgLW8gbG9jayAtbHVjYiAKICovCiNpbmNsdWRlIDxzdGRpby5oPgoj aW5jbHVkZSA8L3Vzci91Y2JpbmNsdWRlL3N5cy9maWxlLmg+CgppbnQgbWFpbigpCnsKICAgIGlu dCBmOyAgLyogRmlsZSAqLwogICAgZnByaW50ZihzdGRlcnIsICJPcGVuaW5nIGZpbGUuLi4iKTsK ICAgIC8qIEEgZmlsZSBpbiBhbiBBRlMgdm9sdW1lLCBSVyBvciBSTyAqLwogICAgaWYoLTEgPT0g KGYgPSBvcGVuKCJsb2NrLnR4dCIsIE9fUkRPTkxZICkpKQogICAgeyAgIAogICAgICAgIGZwcmlu dGYoc3RkZXJyLCAiRmFpbGVkLlxuIik7CiAgICAgICAgcmV0dXJuKDEpOwogICAgfQogICAgZnBy aW50ZihzdGRlcnIsICJEb25lLlxuIik7CgogICAgZnByaW50ZihzdGRlcnIsICJTZXR0aW5nIGEg c2hhcmVkIGxvY2sgb24gdGhlIGZpbGUuLi4iKTsKICAgIGlmKC0xID09IGZsb2NrKGYsIExPQ0tf U0gpKQogICAgeyAgIAogICAgICAgIGZwcmludGYoc3RkZXJyLCAiRmFpbGVkLlxuIik7CiAgICAg ICAgcmV0dXJuKDEpOwogICAgfQogICAgZnByaW50ZihzdGRlcnIsICJEb25lLlxuIik7CiAgICBy ZXR1cm4gMDsKfQo= --0016363b8f00077ed704849d2025 Content-Type: application/octet-stream; name="lock.php" Content-Disposition: attachment; filename="lock.php" Content-Transfer-Encoding: base64 X-Attachment-Id: f_g87ptg9p1 PD9waHAKCi8vIEEgZmlsZSBpbiBhbiBBRlMgdm9sdW1lLCBSVyBvciBSTwokZnAgPSBmb3Blbign bG9jay50eHQnLCAncicpOwoKaWYgKGZsb2NrKCRmcCwgTE9DS19TSCkpIHsgLy8gZG8gYSBzaGFy ZWQgbG9jawogICAgZWNobyAiR290IHRoZSBsb2NrLlxuIjsKICAgIGZsb2NrKCRmcCwgTE9DS19V Tik7IC8vIHJlbGVhc2UgdGhlIGxvY2sKfSBlbHNlIHsKICAgIGVjaG8gIkNvdWxkbid0IGdldCB0 aGUgbG9jayFcbiI7Cn0KCmZjbG9zZSgkZnApOwoKLyogRU9GIGxvY2sucGhwICovCg== --0016363b8f00077ed704849d2025-- From adeason@sinenomine.net Mon Apr 19 23:41:03 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Mon, 19 Apr 2010 17:41:03 -0500 Subject: [OpenAFS] Re: experience of SQLite on AFS References: <20100419115512.861a1fb3.adeason@sinenomine.net> Message-ID: <20100419174103.e76249d5.adeason@sinenomine.net> On Mon, 19 Apr 2010 14:51:28 -0600 Ken Dreyer wrote: > The ACLs were one of the first things I looked at, but "k" seemed to > have no effect. I will try to build SQLite aside from PHP to see if I > can narrow the problem further. I'll try to provide backtraces / > cmdebug too, when I can pull them together. A truss would also at least help to see if it's our bug or theirs. My guess would be that it's ours, since the only difference in the cases you describe is RW vs RO. But it's possible sqlite is broken for RO-fs-with-flock or something. -- Andrew Deason adeason@sinenomine.net From tcreedon@easystreet.net Tue Apr 20 01:30:52 2010 From: tcreedon@easystreet.net (Ted Creedon) Date: Mon, 19 Apr 2010 17:30:52 -0700 Subject: [OpenAFS] Re: [OpenAFS-Doc] Forwarded documentation rant In-Reply-To: <87mxwzb3nt.fsf@windlord.stanford.edu> References: <201004191941.o3JJfFRf027843@thirdoffive.cmf.nrl.navy.mil> <87mxwzb3nt.fsf@windlord.stanford.edu> Message-ID: --000e0cd48308a102670484a03031 Content-Type: text/plain; charset=ISO-8859-1 When you get to progressive trifocals (after coding since 1962...) you will sympathize with those who are set in their ways. I completely understand why the newer generation prefers POD, etc.. It is less labor intensive to produce an acceptable result. There is a docbook 2 Latex that I intend to experiment with. I love permuted indicies. I also have a wiki with a gazillion handy hints. Memories fade too.. Tedc On Mon, Apr 19, 2010 at 1:14 PM, Russ Allbery wrote: > "Chas Williams (CONTRACTOR)" writes: > > > which is why i think the cross references between the man pages is > > somewhat useful. when formatted as html it makes is easier to go > > see the reference command -- just follow the link. however, i dont > > recall how much there was. this would sort of determine whether or > > not this would even be worth the effort. > > That is all there in the current POD and conversion for anything that's > marked with L<> properly. Nearly all of the SEE ALSO sections should be > good. The inline text links are much more hit and miss, unfortunately. > > -- > Russ Allbery (rra@stanford.edu) > > > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info > --000e0cd48308a102670484a03031 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable When you get to progressive trifocals (after coding since 1962...) you will= sympathize with those who are set in their ways.

I completely under= stand why the newer generation prefers POD, etc.. It is less labor intensiv= e to produce an acceptable result.

There is a docbook 2 Latex that I intend to experiment with.

I l= ove permuted indicies. I also have a wiki with a gazillion handy hints.
Memories fade too..

Tedc

On M= on, Apr 19, 2010 at 1:14 PM, Russ Allbery <rra@stanford.edu> wrote:
"Chas Williams (CONTRACTOR)" <chas@cmf.nrl.navy.mil> writes:

> which is why i think the cross references betw= een the man pages is
> somewhat useful. =A0when formatted as html it makes is easier to go > see the reference command -- just follow the link. =A0however, i dont<= br> > recall how much there was. =A0this would sort of determine whether or<= br> > not this would even be worth the effort.

That is all there in the current POD and conversion for anything that= 's
marked with L<> properly. =A0Nearly all of the SEE ALSO sections shou= ld be
good. =A0The inline text links are much more hit and miss, unfortunately.
--
Russ Allbery (= rra@stanford.edu) =A0 =A0 =A0 =A0 =A0 =A0 <http://www.eyrie.org/~eagle/> _______________________________________________

--000e0cd48308a102670484a03031-- From fcombernous@kezia.com Tue Apr 20 10:36:12 2010 From: fcombernous@kezia.com (Fabien COMBERNOUS) Date: Tue, 20 Apr 2010 11:36:12 +0200 Subject: [OpenAFS] OpenAFS algorithm In-Reply-To: <20100416.181622.166956551.haba@habanero.pdc.kth.se> References: <4BC86CED.8020001@kezia.com> <20100416.181622.166956551.haba@habanero.pdc.kth.se> Message-ID: <4BCD758C.9070702@kezia.com> Harald Barth wrote: >> My question is how to permit client in B to use server in B ? I >> didn't found any document explaining the algorithm used by OpenAFS >> to decide the server contacted by the client. >> > > The algoritm is very old and if your IP numbers do not reflect your > network topology it probably yields incorrect results. > > Have a look at man fs_setserverprefs and man fs_getserverprefs > > a lower value indicates a greater preference > > but first check that the clients really knows that there is more than one copy (something like this): > > $ fs where /afs/pdc.kth.se/home/ > File /afs/pdc.kth.se/home/ is on hosts kinilaw.pdc.kth.se morena.pdc.kth.se sculpin.pdc.kth.se houting.pdc.kth.se > I have two servers mpt and lyn. The two servers are file server and db server. The two servers hosts a RO copy of my volume. Only mpt have a RW copy. On a client near lyn, fs where give me only mpt, and fs gets also. How to add the other server lyn ? My file /var/db/openafs/etc/cellServDB knows the two servers . I'm user MacOSX as client and server. with OpenAFS 1.4 Best regards, -- *Fabien COMBERNOUS* /unix system engineer/ www.kezia.com *Tel: +33 (0) 467 992 986* Kezia Group From adeason@sinenomine.net Tue Apr 20 16:14:53 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Tue, 20 Apr 2010 10:14:53 -0500 Subject: [OpenAFS] Re: OpenAFS algorithm References: <4BC86CED.8020001@kezia.com> <20100416.181622.166956551.haba@habanero.pdc.kth.se> <4BCD758C.9070702@kezia.com> Message-ID: <20100420101453.5e546aa9.adeason@sinenomine.net> On Tue, 20 Apr 2010 11:36:12 +0200 Fabien COMBERNOUS wrote: > I have two servers mpt and lyn. The two servers are file server and db > server. The two servers hosts a RO copy of my volume. Only mpt have a > RW copy. > > On a client near lyn, fs where give me only mpt, and fs gets also. > How to add the other server lyn ? You need to access the RO volume, but for some reason, your client is accessing the RW (which only exists at mpt). One of the most common reasons this occurs is that you have an RW volume somewhere in the path to the volume mount point. For example, say you are looking at /afs/localcell/vol.foo/. If the /afs/localcell mountpoint is an RW mountpoint, /afs/localcell/vol.foo will give you RW data, even if /afs/localcell/vol.foo is a normal mountpoint and you have RO copies of vol.foo. Look at every path component to the mountpoint of the volume (look at /afs/, /afs/cell.name/, /afs/cell.name/path/to/vol, etc), and run 'fs exam ' on each one. Where do you stop getting volume names that look like 'foo.readonly'? -- Andrew Deason adeason@sinenomine.net From fcombernous@kezia.com Tue Apr 20 16:58:13 2010 From: fcombernous@kezia.com (Fabien COMBERNOUS) Date: Tue, 20 Apr 2010 17:58:13 +0200 Subject: [OpenAFS] OpenAFS algorithm In-Reply-To: <4BC86CED.8020001@kezia.com> References: <4BC86CED.8020001@kezia.com> Message-ID: <4BCDCF15.7040003@kezia.com> Fabien COMBERNOUS wrote: > Hi, > > We are testing OpenAFS. We have a new cell, hosted by two servers > located in two differents cities A and B. > Only on server (in A) have a RW volume, and all servers (in A and B) > have a RO copy of the volume. > > From an OpenAFS client located in B, i tried to access to data of the > cell. The time necessary to display the picture lets me to say that > the client contacted the remote server in A. > > My question is how to permit client in B to use server in B ? I didn't > found any document explaining the algorithm used by OpenAFS to decide > the server contacted by the client. > > Best regards, > here my solution provided on IRC by sxw and amiga4000. I needed to have a RO copy of volumes root.cell and root.afs on all my server. Now the command fs where give me a list of all the servers. Best regards, -- *Fabien COMBERNOUS* /unix system engineer/ www.kezia.com *Tel: +33 (0) 467 992 986* Kezia Group From haba@kth.se Tue Apr 20 18:29:45 2010 From: haba@kth.se (Harald Barth) Date: Tue, 20 Apr 2010 19:29:45 +0200 (CEST) Subject: [OpenAFS] OpenAFS algorithm In-Reply-To: <4BCDCF15.7040003@kezia.com> References: <4BC86CED.8020001@kezia.com> <4BCDCF15.7040003@kezia.com> Message-ID: <20100420.192945.153517178.haba@habanero.pdc.kth.se> > I needed to have a RO copy of volumes root.cell and root.afs on all my server. Oh, yes, (we have had that for so long that I have not thought any longer about the possibiliy of a cell that does not have such volumes at the root). Harald. From sam@mitre.org Tue Apr 20 19:13:09 2010 From: sam@mitre.org (Samuel Bayer) Date: Tue, 20 Apr 2010 14:13:09 -0400 Subject: [OpenAFS] openAFS 1.4.12 Kernel Panic on restart? (mac) Message-ID: <4BCDEEB5.1080702@mitre.org> --------------060400060803070805030706 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit I'm also having this problem, Mac Pro version 1,1 running 10.6.3. I ran % sudo /Library/OpenAFS/Tools/tools/decode-panic -i /Library/Logs/DiagnosticReports/Kernel_2010-04-19-175345_mac-admins-mac-pro.panic which I believe is what you were asking the previous correspondent on this thread, and retrieved the attached file from /var/db/openafs/logs. The attached panic probably has other kernel modules installed; I subsequently uninstalled all of them and still encountered the problem. The error arises when I do % sudo /Library/OpenAFS/Tools/root.client/usr/vice/etc/afs.rc stop either on the command line directly or indirectly as part of a shutdown. I encountered this problem with 1.4.12 (attached dumps) as well as 1.4.11. I did NOT encounter it with the 1.5.73-3 build; I'd send you the decoded panic for 1.4.11 as well, except I'm getting an error with the decode-panic script in 1.5.73 and I'm frankly bored with rebooting my Mac today. Hope this helps - Sam Bayer The MITRE Corporation sam@mitre.org --------------060400060803070805030706 Content-Type: text/plain; x-mac-type=0; x-mac-creator=0; name="crash.dump" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="crash.dump" Panic Date: Mon Apr 19 17:53:44 2010 Kernel Version: Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 OpenAFS Version: org.openafs.filesystems.afs(1.4.12) ============= add symbol table from file "/tmp/afsdebug7gSSUf/org.openafs.filesystems.afs.sym"? 0x21b449 : mov 0x8011d0,%eax 0x2a8ac2 : jmp 0x2a8ade 0x29e9a8 : mov %edi,%esp 0x81c60811 : mov 0xc0(%eax),%eax 0x2d6af6 : mov %eax,%edi 0x2d75e2 : mov %eax,%ebx 0x2e27d9 : mov %eax,%ebx 0x4ecbb9 : mov %eax,%esi 0x29f43d : mov %edi,%esp --------------060400060803070805030706 Content-Type: text/plain; x-mac-type=0; x-mac-creator=0; name="Kernel_2010-04-19-175345_mac-admins-mac-pro.panic" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Kernel_2010-04-19-175345_mac-admins-mac-pro.panic" Mon Apr 19 17:53:44 2010 panic(cpu 0 caller 0x2a8ac2): Kernel trap at 0x81c60811, type 14=page fault, registers: CR0: 0x80010033, CR2: 0x8167f0c4, CR3: 0x06e9e000, CR4: 0x000006e0 EAX: 0x8167f004, EBX: 0x0be99948, ECX: 0x72510000, EDX: 0x0c460cb0 CR2: 0x8167f0c4, EBP: 0x812bbc98, ESI: 0x0c58c378, EDI: 0x0b88b1f4 EFL: 0x00010282, EIP: 0x81c60811, CS: 0x00000008, DS: 0x7c2e0010 Error code: 0x00000000 Backtrace (CPU 0), Frame : Return Address (4 potential args on stack) 0x812bba58 : 0x21b449 (0x5ce420 0x812bba8c 0x2238a5 0x0) 0x812bbaa8 : 0x2a8ac2 (0x590478 0x81c60811 0xe 0x590642) 0x812bbb88 : 0x29e9a8 (0x812bbba0 0xa4000 0x812bbc98 0x81c60811) 0x812bbb98 : 0x81c60811 (0xe 0x2a0048 0x70 0x10) 0x812bbc98 : 0x2d6af6 (0xbe99948 0x812bbd0c 0xb88b1f4 0xb88b1f4) 0x812bbd28 : 0x2d75e2 (0x812bbe08 0x100 0x812bbe28 0x0) 0x812bbde8 : 0x2e27d9 (0x812bbe08 0xffffffff 0x812bbf38 0x258c9f) 0x812bbf78 : 0x4ecbb9 (0xbf1f7e0 0xb7a3ea8 0xb88b134 0x1) 0x812bbfc8 : 0x29f43d (0xb7a3ea4 0x0 0x10 0xb7a3ea4) Kernel Extensions in backtrace (with dependencies): org.openafs.filesystems.afs(1.4.12)@0x81bd2000->0x81c73fff BSD process name corresponding to current thread: umount Mac OS version: 10D573 Kernel version: Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 System model name: MacPro1,1 (Mac-F4208DC8) System uptime in nanoseconds: 317358318549 unloaded kexts: com.apple.driver.AppleFileSystemDriver 2.0 (addr 0x80702000, size 0x12288) - last unloaded 155716067503 loaded kexts: com.symantec.kext.SymAPComm 11.1f102 - last loaded 40733120047 com.vmware.kext.vmnet 2.0.7 com.vmware.kext.vmioplug 2.0.7 com.vmware.kext.vmci 2.0.7 com.vmware.kext.vmx86 2.0.7 org.openafs.filesystems.afs 1.4.12 com.symantec.kext.ips 1.3.1f6 com.symantec.kext.internetSecurity 1.3f32 com.apple.driver.AppleHWSensor 1.9.3d0 com.apple.filesystems.autofs 2.1.0 com.apple.driver.AudioAUUC 1.4 com.apple.Dont_Steal_Mac_OS_X 7.0.0 com.apple.iokit.CHUDUtils 201 com.apple.iokit.CHUDProf 214 com.apple.driver.AppleUpstreamUserClient 3.3.2 com.apple.GeForce 6.1.0 com.apple.driver.AudioIPCDriver 1.1.2 com.apple.driver.AppleHDA 1.8.4fc3 com.apple.driver.AppleIntel8254XEthernet 2.1.1b7 com.apple.driver.AppleIntelMeromProfile 19 com.apple.driver.AppleMCEDriver 1.1.9 com.apple.driver.ACPI_SMC_PlatformPlugin 4.1.1d0 com.apple.driver.AppleLPC 1.4.11 com.apple.iokit.SCSITaskUserClient 2.6.2 com.apple.BootCache 31 com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1 com.apple.iokit.IOAHCIBlockStorage 1.6.1 com.apple.driver.AppleFWOHCI 4.5.7 com.apple.driver.AppleUSBHub 3.9.6 com.apple.driver.AppleIntelPIIXATA 2.5.1 com.apple.driver.AppleAHCIPort 2.1.1 com.apple.driver.AppleEFINVRAM 1.3.0 com.apple.driver.AppleUSBEHCI 3.9.6 com.apple.driver.AppleUSBUHCI 3.9.6 com.apple.driver.AppleACPIButtons 1.3.2 com.apple.driver.AppleRTC 1.3.1 com.apple.driver.AppleHPET 1.5 com.apple.driver.AppleSMBIOS 1.5 com.apple.driver.AppleACPIEC 1.3.2 com.apple.driver.AppleAPIC 1.4 com.apple.driver.AppleIntelCPUPowerManagementClient 104.3.0 com.apple.security.sandbox 0 com.apple.security.quarantine 0 com.apple.nke.applicationfirewall 2.1.11 com.apple.driver.AppleIntelCPUPowerManagement 104.3.0 com.apple.driver.AppleProfileReadCounterAction 17 com.apple.driver.AppleProfileTimestampAction 10 com.apple.driver.AppleProfileThreadInfoAction 14 com.apple.driver.AppleProfileRegisterStateAction 10 com.apple.driver.AppleProfileKEventAction 10 com.apple.driver.AppleProfileCallstackAction 20 com.apple.iokit.IOSurface 74.0 com.apple.iokit.IOBluetoothSerialManager 2.3.1f4 com.apple.iokit.IOSerialFamily 10.0.3 com.apple.iokit.CHUDKernLib 207 com.apple.driver.DspFuncLib 1.8.4fc3 com.apple.iokit.IOAudioFamily 1.7.6fc2 com.apple.kext.OSvKernDSPLib 1.3 com.apple.nvidia.nv40hal 6.1.0 com.apple.NVDAResman 6.1.0 com.apple.iokit.IONDRVSupport 2.1 com.apple.iokit.IOFireWireIP 2.0.3 com.apple.iokit.IONetworkingFamily 1.9 com.apple.iokit.AppleProfileFamily 41 com.apple.driver.AppleHDAController 1.8.4fc3 com.apple.iokit.IOGraphicsFamily 2.1 com.apple.iokit.IOHDAFamily 1.8.4fc3 com.apple.driver.AppleSMC 3.0.1d2 com.apple.driver.IOPlatformPluginFamily 4.1.1d0 com.apple.iokit.IOUSBHIDDriver 3.9.6 com.apple.driver.AppleUSBMergeNub 3.9.6 com.apple.driver.AppleUSBComposite 3.9.0 com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.2 com.apple.iokit.IOBDStorageFamily 1.6 com.apple.iokit.IODVDStorageFamily 1.6 com.apple.iokit.IOCDStorageFamily 1.6 com.apple.driver.XsanFilter 402.1 com.apple.iokit.IOATAPIProtocolTransport 2.5.1 com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.2 com.apple.iokit.IOFireWireFamily 4.2.6 com.apple.iokit.IOUSBUserClient 3.9.6 com.apple.iokit.IOATAFamily 2.5.1 com.apple.iokit.IOAHCIFamily 2.0.3 com.apple.iokit.IOUSBFamily 3.9.6 com.apple.driver.AppleEFIRuntime 1.3.0 com.apple.iokit.IOHIDFamily 1.6.2 com.apple.iokit.IOSMBusFamily 1.1 com.apple.security.TMSafetyNet 6 com.apple.kext.AppleMatch 1.0.0d1 com.apple.driver.DiskImages 283 com.apple.iokit.IOStorageFamily 1.6 com.apple.driver.AppleACPIPlatform 1.3.2 com.apple.iokit.IOPCIFamily 2.6 com.apple.iokit.IOACPIFamily 1.3.0 --------------060400060803070805030706-- From hans@MPA-Garching.MPG.DE Wed Apr 21 12:28:20 2010 From: hans@MPA-Garching.MPG.DE (Hans-Werner Paulsen) Date: Wed, 21 Apr 2010 13:28:20 +0200 Subject: [OpenAFS] sqlite on AFS will not work, even with whole-file locking In-Reply-To: References: <1931138644.1895.1270750370350.JavaMail.root@thunderbeast.private.linuxbox.com> <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> Message-ID: <20100421112820.GA4623@ncq-5.MPA-Garching.MPG.DE> On Mon, Apr 12, 2010 at 12:34:23AM -0400, Derrick Brashear wrote: > On Sun, Apr 11, 2010 at 11:13 PM, Adam Megacz wrote: > > > > Brandon Simmons writes: > >> Thanks for the response. It seems like whole-file locking in sqlite > >> would be a good choice for me in any case, > > > >> In a situation where the whole-file locking scheme is used, would AF= S > >> be an acceptable choice? Would it be better than NFS? > > > > I had the same idea, and tried it. =A0It does not work. =A0Your datab= ases > > will get corrupted. =A0I never figured out why, although I did confir= m > > that sqlite was in fact requesting only whole-file locks. > > > > It would be nice if it worked, though. =A0There are a lot of applicat= ions > > out there where writes to the database are extremely rare, so > > invalidating all the clients' caches is not a problem. >=20 > do you happen to know what the corruption looked like (blocks of > zeroes, just not readable, something else) >=20 > --=20 > Derrick On 27 Oct 2008 I had a question about flock on AFS, because I did not understand how flock should work on AFS at all. May I repeat this questio= n: Hello, today I am totally confused how the flock(2) call should work on AFS files. Normally locking works in the following way: 1 fd =3D open("afs-file",O_RDWR) do something 2 flock(fd,LOCK_EX) do something with "afs-file" 3 flock(fd,LOCK_UN) do something 4 close(fd) When there are two processes (on different machines) executing that code, the (2) flock call has to update the local copy of the afs-file, otherwise locking is useless. And the (3) flock call has to sync the local copy with the fileserver. Writing a small test program I see that this synchronization isn't done. How can I use the flock(2) call on AFS files? Thank you for any help, --=20 Hans-Werner Paulsen hans@MPA-Garching.MPG.DE MPI f=FCr Astrophysik Tel 089-30000-2602 Karl-Schwarzschild-Str. 1 Fax 089-30000-2235=09 D-85741 Garching From sxw@inf.ed.ac.uk Wed Apr 21 12:49:39 2010 From: sxw@inf.ed.ac.uk (Simon Wilkinson) Date: Wed, 21 Apr 2010 12:49:39 +0100 Subject: [OpenAFS] sqlite on AFS will not work, even with whole-file locking In-Reply-To: <20100421112820.GA4623@ncq-5.MPA-Garching.MPG.DE> References: <1931138644.1895.1270750370350.JavaMail.root@thunderbeast.private.linuxbox.com> <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> <20100421112820.GA4623@ncq-5.MPA-Garching.MPG.DE> Message-ID: <0C30D72D-AFBB-4CEA-B707-9B32EBAA9319@inf.ed.ac.uk> > When there are two processes (on different machines) executing that > code, the (2) flock call has to update the local copy of the afs-file, > otherwise locking is useless. And the (3) flock call has to sync the > local copy with the fileserver. > Writing a small test program I see that this synchronization isn't > done. > How can I use the flock(2) call on AFS files? Are you saying that the locks don't make it to the fileserver (so two processes on different machines can flock() the same file). Or that the file isn't flushed to the server when it is unlocked, so the second machine doesn't see the changes that the first machine has made? Thanks, Simon. From hans@MPA-Garching.MPG.DE Wed Apr 21 13:11:51 2010 From: hans@MPA-Garching.MPG.DE (Hans-Werner Paulsen) Date: Wed, 21 Apr 2010 14:11:51 +0200 Subject: [OpenAFS] sqlite on AFS will not work, even with whole-file locking In-Reply-To: <0C30D72D-AFBB-4CEA-B707-9B32EBAA9319@inf.ed.ac.uk> References: <1931138644.1895.1270750370350.JavaMail.root@thunderbeast.private.linuxbox.com> <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> <20100421112820.GA4623@ncq-5.MPA-Garching.MPG.DE> <0C30D72D-AFBB-4CEA-B707-9B32EBAA9319@inf.ed.ac.uk> Message-ID: <20100421121151.GA4766@ncq-5.MPA-Garching.MPG.DE> On Wed, Apr 21, 2010 at 12:49:39PM +0100, Simon Wilkinson wrote: > >When there are two processes (on different machines) executing that > >code, the (2) flock call has to update the local copy of the afs-file, > >otherwise locking is useless. And the (3) flock call has to sync the > >local copy with the fileserver. > >Writing a small test program I see that this synchronization isn't =20 > >done. > >How can I use the flock(2) call on AFS files? >=20 > Are you saying that the locks don't make it to the fileserver (so two =20 > processes on different machines can flock() the same file). Or that =20 > the file isn't flushed to the server when it is unlocked, so the =20 > second machine doesn't see the changes that the first machine has made? >=20 The second one. To be honest, today I checked only, that the local copy (the cache) is not updated from the fileserver on "flock(fd,LOCK_EX)". HW --=20 Hans-Werner Paulsen hans@MPA-Garching.MPG.DE MPI f=FCr Astrophysik Tel 089-30000-2602 Karl-Schwarzschild-Str. 1 Fax 089-30000-2235=09 D-85741 Garching From shadow@gmail.com Wed Apr 21 13:46:54 2010 From: shadow@gmail.com (Derrick Brashear) Date: Wed, 21 Apr 2010 08:46:54 -0400 Subject: [OpenAFS] sqlite on AFS will not work, even with whole-file locking In-Reply-To: <20100421121151.GA4766@ncq-5.MPA-Garching.MPG.DE> References: <1931138644.1895.1270750370350.JavaMail.root@thunderbeast.private.linuxbox.com> <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> <20100421112820.GA4623@ncq-5.MPA-Garching.MPG.DE> <0C30D72D-AFBB-4CEA-B707-9B32EBAA9319@inf.ed.ac.uk> <20100421121151.GA4766@ncq-5.MPA-Garching.MPG.DE> Message-ID: On Wed, Apr 21, 2010 at 8:11 AM, Hans-Werner Paulsen wrote: > On Wed, Apr 21, 2010 at 12:49:39PM +0100, Simon Wilkinson wrote: >> >When there are two processes (on different machines) executing that >> >code, the (2) flock call has to update the local copy of the afs-file, >> >otherwise locking is useless. And the (3) flock call has to sync the >> >local copy with the fileserver. >> >Writing a small test program I see that this synchronization isn't >> >done. >> >How can I use the flock(2) call on AFS files? >> >> Are you saying that the locks don't make it to the fileserver (so two >> processes on different machines can flock() the same file). Or that >> the file isn't flushed to the server when it is unlocked, so the >> second machine doesn't see the changes that the first machine has made? >> > The second one. To be honest, today I checked only, that the local copy > (the cache) is not updated from the fileserver on "flock(fd,LOCK_EX)". if you have a valid callback, the file better be up to date. uh.... -- Derrick From senseiwa@gmail.com Wed Apr 21 14:06:22 2010 From: senseiwa@gmail.com (Sensei) Date: Wed, 21 Apr 2010 15:06:22 +0200 Subject: [OpenAFS] Cache hot-swap Message-ID: <2F375178-DDB6-4783-A9A8-D985CDF73671@gmail.com> Howdy! I am experimenting with memcache clients. My question is, is it possible to hot-swap cache settings? I'd really = like to have my AFS daemon up and running, but with a consistent amount = of cache when needed. Thanks! Sensei= From hans@MPA-Garching.MPG.DE Wed Apr 21 14:26:56 2010 From: hans@MPA-Garching.MPG.DE (Hans-Werner Paulsen) Date: Wed, 21 Apr 2010 15:26:56 +0200 Subject: [OpenAFS] sqlite on AFS will not work, even with whole-file locking In-Reply-To: References: <1931138644.1895.1270750370350.JavaMail.root@thunderbeast.private.linuxbox.com> <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> <20100421112820.GA4623@ncq-5.MPA-Garching.MPG.DE> <0C30D72D-AFBB-4CEA-B707-9B32EBAA9319@inf.ed.ac.uk> <20100421121151.GA4766@ncq-5.MPA-Garching.MPG.DE> Message-ID: <20100421132656.GA5057@ncq-5.MPA-Garching.MPG.DE> On Wed, Apr 21, 2010 at 08:46:54AM -0400, Derrick Brashear wrote: > if you have a valid callback, the file better be up to date. uh.... Hm, I do not understand. I have the following code on one client: (1) fd =3D open("afs-file",O_RDWR) (2) flock(fd,LOCK_EX) ... When the file is modified on the fileserver after (1) and before (2) the copy on the client is NOT up to date (the file is opened O_RDWR). HW --=20 Hans-Werner Paulsen hans@MPA-Garching.MPG.DE MPI f=FCr Astrophysik Tel 089-30000-2602 Karl-Schwarzschild-Str. 1 Fax 089-30000-2235=09 D-85741 Garching From arne.wiebalck@cern.ch Wed Apr 21 14:41:01 2010 From: arne.wiebalck@cern.ch (Arne Wiebalck) Date: Wed, 21 Apr 2010 15:41:01 +0200 Subject: [OpenAFS] Why does 'fs rmm' not resolve symlinks? Message-ID: <4BCF006D.50207@cern.ch> --------------ms050608010207020204030108 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear list, recently I noticed $ mkdir a $ mkdir a/b $ ln -s a/b l $ fs mkm a/b/m volume $ fs lsm a/b/m 'a/b/m' is a mount point for volume '#volume' $ fs lsm l/m 'l/m' is a mount point for volume '#volume' $ fs rmm l/m fs:'l/m': Not a directory $ fs rmm a/b/m $ Looking into the code of fs I see that 'lsm' resolves symlinks before the stat pioctl, while 'rmm' does not. Is there any particular reason for this? TIA, Arne --------------ms050608010207020204030108 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIVbDCC Bi4wggUWoAMCAQICCmEPqkwAAAAAAAMwDQYJKoZIhvcNAQEFBQAwQTESMBAGCgmSJomT8ixk ARkWAmNoMRQwEgYKCZImiZPyLGQBGRYEY2VybjEVMBMGA1UEAxMMQ0VSTiBSb290IENBMB4X DTA2MTAwMzA5MzYxM1oXDTE2MTAwMzA5NDYxM1owWTESMBAGCgmSJomT8ixkARkWAmNoMRQw EgYKCZImiZPyLGQBGRYEY2VybjEtMCsGA1UEAxMkQ0VSTiBUcnVzdGVkIENlcnRpZmljYXRp b24gQXV0aG9yaXR5MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwdFGqthhWlgU OSZ6C6hReNEVGzbjf2IQgxo7/rOfOQHZH3krQPQ37fqFroEr46PrruymZ/U+QAzmESZQ4Z+n CfBhm7cEi0TIhihHd4cEPaPxawGRT9Ck7BBk9za8TUljF6c/JodnIcmIrpbazEbSAS1KEXwE THDsTrQ7lJ+6SzDP4/oOwrHrgJx+tKsmgOsFSbBEK4OYx1UYQpYS9OJQk2Sc0q4a/SCSu+xb N8ppmgV3WFytN8NW20n3NpCCWYPzo9rXmPRA7a/c6mf+RV5gPCnUqeW6KUvix5kz9+X8/4SQ V/fU12OPdRvtkqcC+PpiePK7bjMLQJEYwvchJrSzAwIDAQABo4IDDjCCAwowDwYDVR0TAQH/ BAUwAwEB/zAdBgNVHQ4EFgQUmMyS0EYwNoyw7ZgNclGpR0zdviEwCwYDVR0PBAQDAgGGMBAG CSsGAQQBgjcVAQQDAgECMCMGCSsGAQQBgjcVAgQWBBT/RljlvgfrVK8GmAaYe+TbiXbJ7DBR BgNVHSAESjBIMEYGCisGAQQBYAoCAQEwODA2BggrBgEFBQcCARYqaHR0cDovL2NhLmNlcm4u Y2gvY2EvY3JsL3BvbGljeS9jcC1jcHMucGRmMBkGCSsGAQQBgjcUAgQMHgoAUwB1AGIAQwBB MB8GA1UdIwQYMBaAFJgK9+w+7FnWHa2ZvLUBPt7spudQMIH8BgNVHR8EgfQwgfEwge6ggeug geiGLWh0dHA6Ly9jYS5jZXJuLmNoL2NhL2NybC9DRVJOJTIwUm9vdCUyMENBLmNybIaBtmxk YXA6Ly8vQ049Q0VSTiUyMFJvb3QlMjBDQSxDTj1jZXJucm9vdGNhLENOPUNEUCxDTj1QdWJs aWMlMjBLZXklMjBTZXJ2aWNlcyxDTj1TZXJ2aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPWNl cm4sREM9Y2g/Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENsYXNzPWNS TERpc3RyaWJ1dGlvblBvaW50MIIBBAYIKwYBBQUHAQEEgfcwgfQwRAYIKwYBBQUHMAKGOGh0 dHA6Ly9jYS5jZXJuLmNoL2NhL2NybC9jZXJucm9vdGNhX0NFUk4lMjBSb290JTIwQ0EuY3J0 MIGrBggrBgEFBQcwAoaBnmxkYXA6Ly8vQ049Q0VSTiUyMFJvb3QlMjBDQSxDTj1BSUEsQ049 UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixE Qz1jZXJuLERDPWNoP2NBQ2VydGlmaWNhdGU/YmFzZT9vYmplY3RDbGFzcz1jZXJ0aWZpY2F0 aW9uQXV0aG9yaXR5MA0GCSqGSIb3DQEBBQUAA4IBAQAfEzvOeYohKndmJqnVdiCqZ38tSBxO OPsKUHW4UY1jBfYMXbnZ9keFQFlK/g5X4aZPNBEHXw0eKpQVsMhEPWQrvx8T/f7GwtU+JNQh kgK9tnezmHxYzWgEC9MXZhfYzFSwMIF6kSKllmUTnN35uF1EnT8+64daje+yEVcpmM34p8Fw 125/WpKnRmwNp0YkUk6uMti6Y6vOTHttzIN5P6elGoat8sadMqrVnaMNzG8hGUvSkYivYBs7 msAPuwmXgLvIkXWPW+MDFs+x5Kzx75ZHv3c2WoKgUxL5KZH9QqiR7t8P6YBfYW6SpzyGRi4Q HN/iOLhXZ06R6aPljLEOn41JMIIHmTCCBoGgAwIBAgIKfTgEqwACAABADjANBgkqhkiG9w0B AQUFADBZMRIwEAYKCZImiZPyLGQBGRYCY2gxFDASBgoJkiaJk/IsZAEZFgRjZXJuMS0wKwYD VQQDEyRDRVJOIFRydXN0ZWQgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwHhcNMDkwNjAzMTAx ODA5WhcNMTAwNjAzMTAxODA5WjCBjjESMBAGCgmSJomT8ixkARkWAmNoMRQwEgYKCZImiZPy LGQBGRYEY2VybjEWMBQGA1UECxMNT3JnYW5pYyBVbml0czEOMAwGA1UECxMFVXNlcnMxETAP BgNVBAMTCHdpZWJhbGNrMQ8wDQYDVQQDEwY1NTg1MTAxFjAUBgNVBAMTDUFybmUgV2llYmFs Y2swggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDLbot5pSxt1GsIUMKrMBPt7tTr X322PwR4gLovv/umKlimFsSQ3Wyk4nxRatyD+AxzSSGwZqxnzcf+janFAUSI3CTx3wAabhtU ol50Ub2yRTF7zefei2iEFeX06DUKrCxB0+tUc6ZhdS88PDwB4XmZmQyjIvfV1Yby8vb+kYGe yvSWx/lbvTHdEv6m0WREznr5xfAQj7fa2rd7u/VuQdmcuFFXmeoIJidWgvVTmT1pIvYnbsOS 2ohQWhgVe0Bs3xTDkUIPaDFSy1xuOquMNuzsnf9rKa3VbKzLm4ciZ9X+i+zFPj9NBPoxe57Q l3v1VRI7/7ooHsxRczVoWOo/rULVAgMBAAGjggQrMIIEJzAdBgNVHQ4EFgQUiKnO/Fk5JrYr a3kqpCVfIYBwflowHwYDVR0jBBgwFoAUmMyS0EYwNoyw7ZgNclGpR0zdviEwggE0BgNVHR8E ggErMIIBJzCCASOgggEfoIIBG4ZHaHR0cDovL2NhLmNlcm4uY2gvY2EvY3JsL0NFUk4lMjBU cnVzdGVkJTIwQ2VydGlmaWNhdGlvbiUyMEF1dGhvcml0eS5jcmyGgc9sZGFwOi8vL0NOPUNF Uk4lMjBUcnVzdGVkJTIwQ2VydGlmaWNhdGlvbiUyMEF1dGhvcml0eSxDTj1jZXJucGtpMDEs Q049Q0RQLENOPVB1YmxpYyUyMEtleSUyMFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZp Z3VyYXRpb24sREM9Y2VybixEQz1jaD9jZXJ0aWZpY2F0ZVJldm9jYXRpb25MaXN0P2Jhc2U/ b2JqZWN0Q2xhc3M9Y1JMRGlzdHJpYnV0aW9uUG9pbnQwggFEBggrBgEFBQcBAQSCATYwggEy MGgGCCsGAQUFBzAChlxodHRwOi8vY2EuY2Vybi5jaC9jYS9jcmwvY2VybnBraTAxLmNlcm4u Y2hfQ0VSTiUyMFRydXN0ZWQlMjBDZXJ0aWZpY2F0aW9uJTIwQXV0aG9yaXR5KDIpLmNydDCB xQYIKwYBBQUHMAKGgbhsZGFwOi8vL0NOPUNFUk4lMjBUcnVzdGVkJTIwQ2VydGlmaWNhdGlv biUyMEF1dGhvcml0eSxDTj1BSUEsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2Vy dmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1jZXJuLERDPWNoP2NBQ2VydGlmaWNhdGU/YmFz ZT9vYmplY3RDbGFzcz1jZXJ0aWZpY2F0aW9uQXV0aG9yaXR5MAwGA1UdEwEB/wQCMAAwDgYD VR0PAQH/BAQDAgWgMD0GCSsGAQQBgjcVBwQwMC4GJisGAQQBgjcVCIO90AmC7Y0Nhu2LK4He 9TeFgNBiHoW/ugOExMxMAgFkAgEJMCkGA1UdJQQiMCAGCCsGAQUFBwMCBggrBgEFBQcDBAYK KwYBBAGCNwoDBDAXBgNVHSAEEDAOMAwGCisGAQQBYAoCAQEwNQYJKwYBBAGCNxUKBCgwJjAK BggrBgEFBQcDAjAKBggrBgEFBQcDBDAMBgorBgEEAYI3CgMEMEcGA1UdEQRAMD6gJQYKKwYB BAGCNxQCA6AXDBVhcm5lLndpZWJhbGNrQGNlcm4uY2iBFUFybmUuV2llYmFsY2tAY2Vybi5j aDBEBgkqhkiG9w0BCQ8ENzA1MA4GCCqGSIb3DQMCAgIAgDAOBggqhkiG9w0DBAICAIAwBwYF Kw4DAgcwCgYIKoZIhvcNAwcwDQYJKoZIhvcNAQEFBQADggEBAHNiMqTp0rh8wbpqROptfTni ZOf64kj3SF9oBrf7TPBQWA7ij8LsqhTxyh78M0G+HzfvPfI2g41fifNhT0vQf6z6ZPMKNeKE H+1OJXriKAHuN4hl+jvLY1nrNvYpAZ7g03xpI7XdjOZWc/B0F6U4iUd99iSuTYzeTkQA8Gx1 YM49dSytlDG88WYqPucTvHR1Y/bpEq+q16pyX2IZ6cX0/XGr+eA5NtJBvGheO+4IXOfTpZJp cjNxxcPi8LjtTE+snXGzDyVYrZe//MHa3IZUfapTM6i4idrKbUcFGGzmS/V2tTXg0UD4nDFj cxtMYKKL1nwt9Npdn0Z4wkiNzJvbqc0wggeZMIIGgaADAgECAgp9OASrAAIAAEAOMA0GCSqG SIb3DQEBBQUAMFkxEjAQBgoJkiaJk/IsZAEZFgJjaDEUMBIGCgmSJomT8ixkARkWBGNlcm4x LTArBgNVBAMTJENFUk4gVHJ1c3RlZCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wOTA2 MDMxMDE4MDlaFw0xMDA2MDMxMDE4MDlaMIGOMRIwEAYKCZImiZPyLGQBGRYCY2gxFDASBgoJ kiaJk/IsZAEZFgRjZXJuMRYwFAYDVQQLEw1PcmdhbmljIFVuaXRzMQ4wDAYDVQQLEwVVc2Vy czERMA8GA1UEAxMId2llYmFsY2sxDzANBgNVBAMTBjU1ODUxMDEWMBQGA1UEAxMNQXJuZSBX aWViYWxjazCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMtui3mlLG3UawhQwqsw E+3u1OtffbY/BHiAui+/+6YqWKYWxJDdbKTifFFq3IP4DHNJIbBmrGfNx/6NqcUBRIjcJPHf ABpuG1SiXnRRvbJFMXvN596LaIQV5fToNQqsLEHT61RzpmF1Lzw8PAHheZmZDKMi99XVhvLy 9v6RgZ7K9JbH+Vu9Md0S/qbRZETOevnF8BCPt9rat3u79W5B2Zy4UVeZ6ggmJ1aC9VOZPWki 9iduw5LaiFBaGBV7QGzfFMORQg9oMVLLXG46q4w27Oyd/2sprdVsrMubhyJn1f6L7MU+P00E +jF7ntCXe/VVEjv/uigezFFzNWhY6j+tQtUCAwEAAaOCBCswggQnMB0GA1UdDgQWBBSIqc78 WTkmtitreSqkJV8hgHB+WjAfBgNVHSMEGDAWgBSYzJLQRjA2jLDtmA1yUalHTN2+ITCCATQG A1UdHwSCASswggEnMIIBI6CCAR+gggEbhkdodHRwOi8vY2EuY2Vybi5jaC9jYS9jcmwvQ0VS TiUyMFRydXN0ZWQlMjBDZXJ0aWZpY2F0aW9uJTIwQXV0aG9yaXR5LmNybIaBz2xkYXA6Ly8v Q049Q0VSTiUyMFRydXN0ZWQlMjBDZXJ0aWZpY2F0aW9uJTIwQXV0aG9yaXR5LENOPWNlcm5w a2kwMSxDTj1DRFAsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049 Q29uZmlndXJhdGlvbixEQz1jZXJuLERDPWNoP2NlcnRpZmljYXRlUmV2b2NhdGlvbkxpc3Q/ YmFzZT9vYmplY3RDbGFzcz1jUkxEaXN0cmlidXRpb25Qb2ludDCCAUQGCCsGAQUFBwEBBIIB NjCCATIwaAYIKwYBBQUHMAKGXGh0dHA6Ly9jYS5jZXJuLmNoL2NhL2NybC9jZXJucGtpMDEu Y2Vybi5jaF9DRVJOJTIwVHJ1c3RlZCUyMENlcnRpZmljYXRpb24lMjBBdXRob3JpdHkoMiku Y3J0MIHFBggrBgEFBQcwAoaBuGxkYXA6Ly8vQ049Q0VSTiUyMFRydXN0ZWQlMjBDZXJ0aWZp Y2F0aW9uJTIwQXV0aG9yaXR5LENOPUFJQSxDTj1QdWJsaWMlMjBLZXklMjBTZXJ2aWNlcyxD Tj1TZXJ2aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPWNlcm4sREM9Y2g/Y0FDZXJ0aWZpY2F0 ZT9iYXNlP29iamVjdENsYXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkwDAYDVR0TAQH/BAIw ADAOBgNVHQ8BAf8EBAMCBaAwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIg73QCYLtjQ2G 7Ysrgd71N4WA0GIehb+6A4TEzEwCAWQCAQkwKQYDVR0lBCIwIAYIKwYBBQUHAwIGCCsGAQUF BwMEBgorBgEEAYI3CgMEMBcGA1UdIAQQMA4wDAYKKwYBBAFgCgIBATA1BgkrBgEEAYI3FQoE KDAmMAoGCCsGAQUFBwMCMAoGCCsGAQUFBwMEMAwGCisGAQQBgjcKAwQwRwYDVR0RBEAwPqAl BgorBgEEAYI3FAIDoBcMFWFybmUud2llYmFsY2tAY2Vybi5jaIEVQXJuZS5XaWViYWxja0Bj ZXJuLmNoMEQGCSqGSIb3DQEJDwQ3MDUwDgYIKoZIhvcNAwICAgCAMA4GCCqGSIb3DQMEAgIA gDAHBgUrDgMCBzAKBggqhkiG9w0DBzANBgkqhkiG9w0BAQUFAAOCAQEAc2IypOnSuHzBumpE 6m19OeJk5/riSPdIX2gGt/tM8FBYDuKPwuyqFPHKHvwzQb4fN+898jaDjV+J82FPS9B/rPpk 8wo14oQf7U4leuIoAe43iGX6O8tjWes29ikBnuDTfGkjtd2M5lZz8HQXpTiJR332JK5NjN5O RADwbHVgzj11LK2UMbzxZio+5xO8dHVj9ukSr6rXqnJfYhnpxfT9cav54Dk20kG8aF477ghc 59OlkmlyM3HFw+LwuO1MT6ydcbMPJVitl7/8wdrchlR9qlMzqLiJ2sptRwUYbOZL9Xa1NeDR QPicMWNzG0xgoovWfC302l2fRnjCSI3Mm9upzTGCA0IwggM+AgEBMGcwWTESMBAGCgmSJomT 8ixkARkWAmNoMRQwEgYKCZImiZPyLGQBGRYEY2VybjEtMCsGA1UEAxMkQ0VSTiBUcnVzdGVk IENlcnRpZmljYXRpb24gQXV0aG9yaXR5Agp9OASrAAIAAEAOMAkGBSsOAwIaBQCgggGwMBgG CSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEwMDQyMTEzNDEwMVow IwYJKoZIhvcNAQkEMRYEFOR7g52EA/7LkuluiFGg1bly4NMqMF8GCSqGSIb3DQEJDzFSMFAw CwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIB QDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDB2BgkrBgEEAYI3EAQxaTBnMFkxEjAQBgoJkiaJ k/IsZAEZFgJjaDEUMBIGCgmSJomT8ixkARkWBGNlcm4xLTArBgNVBAMTJENFUk4gVHJ1c3Rl ZCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eQIKfTgEqwACAABADjB4BgsqhkiG9w0BCRACCzFp oGcwWTESMBAGCgmSJomT8ixkARkWAmNoMRQwEgYKCZImiZPyLGQBGRYEY2VybjEtMCsGA1UE AxMkQ0VSTiBUcnVzdGVkIENlcnRpZmljYXRpb24gQXV0aG9yaXR5Agp9OASrAAIAAEAOMA0G CSqGSIb3DQEBAQUABIIBABAt4MFmjr3cSnJkOS2/g1k9jfyFAfNMT9b0svl2imW2/z74v5wh p0EOow+l7daO/9t7LZniFLxtBJftQ6HRWWWQfbxBX6d6eEFqsJh+Ju6OcRN0NdeMesJdWumK KixpbDcdSXza2TweJ0qTa9jaBHX5AjYCUQ/Uf++MMMSwTKceLm2P69GFvD4bMLdJQhqc4U6C dpxw1UKlWmlTkI/xyWus9yCYJ5i7Ht3YZ7uSmDiAnZ932beQMg+8uyTs45elFXUFsTToDQyO rqptjuncXoLeLGVsJLnDXf2W8rVvWZOISvbfKVa7e9Pp14VhwgNqvllIebpGBn97R5a169t+ e4wAAAAAAAA= --------------ms050608010207020204030108-- From shadow@gmail.com Wed Apr 21 14:48:27 2010 From: shadow@gmail.com (Derrick Brashear) Date: Wed, 21 Apr 2010 09:48:27 -0400 Subject: [OpenAFS] sqlite on AFS will not work, even with whole-file locking In-Reply-To: <20100421132656.GA5057@ncq-5.MPA-Garching.MPG.DE> References: <1931138644.1895.1270750370350.JavaMail.root@thunderbeast.private.linuxbox.com> <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> <20100421112820.GA4623@ncq-5.MPA-Garching.MPG.DE> <0C30D72D-AFBB-4CEA-B707-9B32EBAA9319@inf.ed.ac.uk> <20100421121151.GA4766@ncq-5.MPA-Garching.MPG.DE> <20100421132656.GA5057@ncq-5.MPA-Garching.MPG.DE> Message-ID: On Wed, Apr 21, 2010 at 9:26 AM, Hans-Werner Paulsen wrote: > On Wed, Apr 21, 2010 at 08:46:54AM -0400, Derrick Brashear wrote: >> if you have a valid callback, the file better be up to date. uh.... > Hm, I do not understand. I have the following code on one client: > (1) fd = open("afs-file",O_RDWR) > (2) flock(fd,LOCK_EX) > ... > When the file is modified on the fileserver after (1) and before (2) > the copy on the client is NOT up to date (the file is opened O_RDWR). if you opened it O_RDWR on this client, it better have a valid callback. if it's modified and you still have it open, the callback is broken. if the client doesn't refetch, it's a bug, and it has nothing to do with locking particularly. From adeason@sinenomine.net Wed Apr 21 15:19:57 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Wed, 21 Apr 2010 09:19:57 -0500 Subject: [OpenAFS] Re: Cache hot-swap References: <2F375178-DDB6-4783-A9A8-D985CDF73671@gmail.com> Message-ID: <20100421091957.a06a89a2.adeason@sinenomine.net> On Wed, 21 Apr 2010 15:06:22 +0200 Sensei wrote: > My question is, is it possible to hot-swap cache settings? I'd really > like to have my AFS daemon up and running, but with a consistent > amount of cache when needed. Most cache settings cannot be changed after startup. You can alter the size of the cache with 'fs setcachesize', though. Note that many cache settings are usually auto-tuned depending on the startup cache size, and they will not be readjusted when you change the cache size via 'fs setcachesize'. -- Andrew Deason adeason@sinenomine.net From adeason@sinenomine.net Wed Apr 21 15:22:33 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Wed, 21 Apr 2010 09:22:33 -0500 Subject: [OpenAFS] Re: Why does 'fs rmm' not resolve symlinks? References: <4BCF006D.50207@cern.ch> Message-ID: <20100421092233.f5ec17d3.adeason@sinenomine.net> On Wed, 21 Apr 2010 15:41:01 +0200 Arne Wiebalck wrote: > Looking into the code of fs I see that 'lsm' resolves > symlinks before the stat pioctl, while 'rmm' does not. > Is there any particular reason for this? You would rather it remove the target of the symlink? 'rm' and 'rmdir' don't work like that, either. $ mkdir foo.dir $ ln -s foo.dir foo.link $ rmdir foo.link rmdir: foo.link: Not a directory $ -- Andrew Deason adeason@sinenomine.net From sxw@inf.ed.ac.uk Wed Apr 21 15:30:30 2010 From: sxw@inf.ed.ac.uk (Simon Wilkinson) Date: Wed, 21 Apr 2010 15:30:30 +0100 Subject: [OpenAFS] sqlite on AFS will not work, even with whole-file locking In-Reply-To: <20100421132656.GA5057@ncq-5.MPA-Garching.MPG.DE> References: <1931138644.1895.1270750370350.JavaMail.root@thunderbeast.private.linuxbox.com> <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> <20100421112820.GA4623@ncq-5.MPA-Garching.MPG.DE> <0C30D72D-AFBB-4CEA-B707-9B32EBAA9319@inf.ed.ac.uk> <20100421121151.GA4766@ncq-5.MPA-Garching.MPG.DE> <20100421132656.GA5057@ncq-5.MPA-Garching.MPG.DE> Message-ID: <7DC84662-A1E8-4C2C-976C-FB7B89AFDAA0@inf.ed.ac.uk> On 21 Apr 2010, at 14:26, Hans-Werner Paulsen wrote: > On Wed, Apr 21, 2010 at 08:46:54AM -0400, Derrick Brashear wrote: >> if you have a valid callback, the file better be up to date. uh.... > Hm, I do not understand. I have the following code on one client: > (1) fd = open("afs-file",O_RDWR) > (2) flock(fd,LOCK_EX) > ... > When the file is modified on the fileserver after (1) and before (2) > the copy on the client is NOT up to date (the file is opened O_RDWR). I strongly suspect that the copy on the client is up to date, at least according to the server. However, it may well be out of data according to the machine which made the modification. That machine only writes its changes back to the server on receipt of a fflush or close (or when it's cache fills, and it needs to shed some dirty chunks). So, if there is a problem here, it's going to be related to the fact that we aren't flushing when a lock is released, rather than our behaviour on obtaining a lock. Perhaps you could verify that case? Cheers, Simon. From matt@linuxbox.com Wed Apr 21 16:34:52 2010 From: matt@linuxbox.com (Matt W. Benjamin) Date: Wed, 21 Apr 2010 11:34:52 -0400 (EDT) Subject: [OpenAFS] sqlite on AFS will not work, even with whole-file locking In-Reply-To: <7DC84662-A1E8-4C2C-976C-FB7B89AFDAA0@inf.ed.ac.uk> Message-ID: <1582954080.754.1271864092218.JavaMail.root@thunderbeast.private.linuxbox.com> If the CM omits to flush in this case, that's a plausible result. Viced will BCB when the lock is released, but if the changed data hasn't been written back, the cooperating clients lose. Matt ----- "Simon Wilkinson" wrote: > > I strongly suspect that the copy on the client is up to date, at least > > according to the server. However, it may well be out of data according > > to the machine which made the modification. That machine only writes > > its changes back to the server on receipt of a fflush or close (or > when it's cache fills, and it needs to shed some dirty chunks). > > So, if there is a problem here, it's going to be related to the fact > > that we aren't flushing when a lock is released, rather than our > behaviour on obtaining a lock. Perhaps you could verify that case? > > Cheers, > > Simon. > > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info -- Matt Benjamin The Linux Box 206 South Fifth Ave. Suite 150 Ann Arbor, MI 48104 http://linuxbox.com tel. 734-761-4689 fax. 734-769-8938 cel. 734-216-5309 From arne.wiebalck@cern.ch Wed Apr 21 16:50:15 2010 From: arne.wiebalck@cern.ch (Arne Wiebalck) Date: Wed, 21 Apr 2010 17:50:15 +0200 Subject: [OpenAFS] Re: Why does 'fs rmm' not resolve symlinks? In-Reply-To: <20100421092233.f5ec17d3.adeason@sinenomine.net> References: <4BCF006D.50207@cern.ch> <20100421092233.f5ec17d3.adeason@sinenomine.net> Message-ID: <4BCF1EB7.60203@cern.ch> --------------ms090805020807010902010603 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Andrew Deason wrote: > On Wed, 21 Apr 2010 15:41:01 +0200 > Arne Wiebalck wrote: > >> Looking into the code of fs I see that 'lsm' resolves >> symlinks before the stat pioctl, while 'rmm' does not. >> Is there any particular reason for this? > > You would rather it remove the target of the symlink? 'rm' and 'rmdir' > don't work like that, either. > > $ mkdir foo.dir > $ ln -s foo.dir foo.link > $ rmdir foo.link > rmdir: foo.link: Not a directory > $ True, but 'ls -ld' or 'file' (as 'fs lsm' equivalents) would tell me that "foo.link" is not a dir and hence give me a hint why the operation fails. 'fs lsm' says it's a mountpoint for the link and the target. --------------ms090805020807010902010603 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIVbDCC Bi4wggUWoAMCAQICCmEPqkwAAAAAAAMwDQYJKoZIhvcNAQEFBQAwQTESMBAGCgmSJomT8ixk ARkWAmNoMRQwEgYKCZImiZPyLGQBGRYEY2VybjEVMBMGA1UEAxMMQ0VSTiBSb290IENBMB4X DTA2MTAwMzA5MzYxM1oXDTE2MTAwMzA5NDYxM1owWTESMBAGCgmSJomT8ixkARkWAmNoMRQw EgYKCZImiZPyLGQBGRYEY2VybjEtMCsGA1UEAxMkQ0VSTiBUcnVzdGVkIENlcnRpZmljYXRp b24gQXV0aG9yaXR5MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwdFGqthhWlgU OSZ6C6hReNEVGzbjf2IQgxo7/rOfOQHZH3krQPQ37fqFroEr46PrruymZ/U+QAzmESZQ4Z+n CfBhm7cEi0TIhihHd4cEPaPxawGRT9Ck7BBk9za8TUljF6c/JodnIcmIrpbazEbSAS1KEXwE THDsTrQ7lJ+6SzDP4/oOwrHrgJx+tKsmgOsFSbBEK4OYx1UYQpYS9OJQk2Sc0q4a/SCSu+xb N8ppmgV3WFytN8NW20n3NpCCWYPzo9rXmPRA7a/c6mf+RV5gPCnUqeW6KUvix5kz9+X8/4SQ V/fU12OPdRvtkqcC+PpiePK7bjMLQJEYwvchJrSzAwIDAQABo4IDDjCCAwowDwYDVR0TAQH/ BAUwAwEB/zAdBgNVHQ4EFgQUmMyS0EYwNoyw7ZgNclGpR0zdviEwCwYDVR0PBAQDAgGGMBAG CSsGAQQBgjcVAQQDAgECMCMGCSsGAQQBgjcVAgQWBBT/RljlvgfrVK8GmAaYe+TbiXbJ7DBR BgNVHSAESjBIMEYGCisGAQQBYAoCAQEwODA2BggrBgEFBQcCARYqaHR0cDovL2NhLmNlcm4u Y2gvY2EvY3JsL3BvbGljeS9jcC1jcHMucGRmMBkGCSsGAQQBgjcUAgQMHgoAUwB1AGIAQwBB MB8GA1UdIwQYMBaAFJgK9+w+7FnWHa2ZvLUBPt7spudQMIH8BgNVHR8EgfQwgfEwge6ggeug geiGLWh0dHA6Ly9jYS5jZXJuLmNoL2NhL2NybC9DRVJOJTIwUm9vdCUyMENBLmNybIaBtmxk YXA6Ly8vQ049Q0VSTiUyMFJvb3QlMjBDQSxDTj1jZXJucm9vdGNhLENOPUNEUCxDTj1QdWJs aWMlMjBLZXklMjBTZXJ2aWNlcyxDTj1TZXJ2aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPWNl cm4sREM9Y2g/Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENsYXNzPWNS TERpc3RyaWJ1dGlvblBvaW50MIIBBAYIKwYBBQUHAQEEgfcwgfQwRAYIKwYBBQUHMAKGOGh0 dHA6Ly9jYS5jZXJuLmNoL2NhL2NybC9jZXJucm9vdGNhX0NFUk4lMjBSb290JTIwQ0EuY3J0 MIGrBggrBgEFBQcwAoaBnmxkYXA6Ly8vQ049Q0VSTiUyMFJvb3QlMjBDQSxDTj1BSUEsQ049 UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixE Qz1jZXJuLERDPWNoP2NBQ2VydGlmaWNhdGU/YmFzZT9vYmplY3RDbGFzcz1jZXJ0aWZpY2F0 aW9uQXV0aG9yaXR5MA0GCSqGSIb3DQEBBQUAA4IBAQAfEzvOeYohKndmJqnVdiCqZ38tSBxO OPsKUHW4UY1jBfYMXbnZ9keFQFlK/g5X4aZPNBEHXw0eKpQVsMhEPWQrvx8T/f7GwtU+JNQh kgK9tnezmHxYzWgEC9MXZhfYzFSwMIF6kSKllmUTnN35uF1EnT8+64daje+yEVcpmM34p8Fw 125/WpKnRmwNp0YkUk6uMti6Y6vOTHttzIN5P6elGoat8sadMqrVnaMNzG8hGUvSkYivYBs7 msAPuwmXgLvIkXWPW+MDFs+x5Kzx75ZHv3c2WoKgUxL5KZH9QqiR7t8P6YBfYW6SpzyGRi4Q HN/iOLhXZ06R6aPljLEOn41JMIIHmTCCBoGgAwIBAgIKfTgEqwACAABADjANBgkqhkiG9w0B AQUFADBZMRIwEAYKCZImiZPyLGQBGRYCY2gxFDASBgoJkiaJk/IsZAEZFgRjZXJuMS0wKwYD VQQDEyRDRVJOIFRydXN0ZWQgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwHhcNMDkwNjAzMTAx ODA5WhcNMTAwNjAzMTAxODA5WjCBjjESMBAGCgmSJomT8ixkARkWAmNoMRQwEgYKCZImiZPy LGQBGRYEY2VybjEWMBQGA1UECxMNT3JnYW5pYyBVbml0czEOMAwGA1UECxMFVXNlcnMxETAP BgNVBAMTCHdpZWJhbGNrMQ8wDQYDVQQDEwY1NTg1MTAxFjAUBgNVBAMTDUFybmUgV2llYmFs Y2swggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDLbot5pSxt1GsIUMKrMBPt7tTr X322PwR4gLovv/umKlimFsSQ3Wyk4nxRatyD+AxzSSGwZqxnzcf+janFAUSI3CTx3wAabhtU ol50Ub2yRTF7zefei2iEFeX06DUKrCxB0+tUc6ZhdS88PDwB4XmZmQyjIvfV1Yby8vb+kYGe yvSWx/lbvTHdEv6m0WREznr5xfAQj7fa2rd7u/VuQdmcuFFXmeoIJidWgvVTmT1pIvYnbsOS 2ohQWhgVe0Bs3xTDkUIPaDFSy1xuOquMNuzsnf9rKa3VbKzLm4ciZ9X+i+zFPj9NBPoxe57Q l3v1VRI7/7ooHsxRczVoWOo/rULVAgMBAAGjggQrMIIEJzAdBgNVHQ4EFgQUiKnO/Fk5JrYr a3kqpCVfIYBwflowHwYDVR0jBBgwFoAUmMyS0EYwNoyw7ZgNclGpR0zdviEwggE0BgNVHR8E ggErMIIBJzCCASOgggEfoIIBG4ZHaHR0cDovL2NhLmNlcm4uY2gvY2EvY3JsL0NFUk4lMjBU cnVzdGVkJTIwQ2VydGlmaWNhdGlvbiUyMEF1dGhvcml0eS5jcmyGgc9sZGFwOi8vL0NOPUNF Uk4lMjBUcnVzdGVkJTIwQ2VydGlmaWNhdGlvbiUyMEF1dGhvcml0eSxDTj1jZXJucGtpMDEs Q049Q0RQLENOPVB1YmxpYyUyMEtleSUyMFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZp Z3VyYXRpb24sREM9Y2VybixEQz1jaD9jZXJ0aWZpY2F0ZVJldm9jYXRpb25MaXN0P2Jhc2U/ b2JqZWN0Q2xhc3M9Y1JMRGlzdHJpYnV0aW9uUG9pbnQwggFEBggrBgEFBQcBAQSCATYwggEy MGgGCCsGAQUFBzAChlxodHRwOi8vY2EuY2Vybi5jaC9jYS9jcmwvY2VybnBraTAxLmNlcm4u Y2hfQ0VSTiUyMFRydXN0ZWQlMjBDZXJ0aWZpY2F0aW9uJTIwQXV0aG9yaXR5KDIpLmNydDCB xQYIKwYBBQUHMAKGgbhsZGFwOi8vL0NOPUNFUk4lMjBUcnVzdGVkJTIwQ2VydGlmaWNhdGlv biUyMEF1dGhvcml0eSxDTj1BSUEsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2Vy dmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1jZXJuLERDPWNoP2NBQ2VydGlmaWNhdGU/YmFz ZT9vYmplY3RDbGFzcz1jZXJ0aWZpY2F0aW9uQXV0aG9yaXR5MAwGA1UdEwEB/wQCMAAwDgYD VR0PAQH/BAQDAgWgMD0GCSsGAQQBgjcVBwQwMC4GJisGAQQBgjcVCIO90AmC7Y0Nhu2LK4He 9TeFgNBiHoW/ugOExMxMAgFkAgEJMCkGA1UdJQQiMCAGCCsGAQUFBwMCBggrBgEFBQcDBAYK KwYBBAGCNwoDBDAXBgNVHSAEEDAOMAwGCisGAQQBYAoCAQEwNQYJKwYBBAGCNxUKBCgwJjAK BggrBgEFBQcDAjAKBggrBgEFBQcDBDAMBgorBgEEAYI3CgMEMEcGA1UdEQRAMD6gJQYKKwYB BAGCNxQCA6AXDBVhcm5lLndpZWJhbGNrQGNlcm4uY2iBFUFybmUuV2llYmFsY2tAY2Vybi5j aDBEBgkqhkiG9w0BCQ8ENzA1MA4GCCqGSIb3DQMCAgIAgDAOBggqhkiG9w0DBAICAIAwBwYF Kw4DAgcwCgYIKoZIhvcNAwcwDQYJKoZIhvcNAQEFBQADggEBAHNiMqTp0rh8wbpqROptfTni ZOf64kj3SF9oBrf7TPBQWA7ij8LsqhTxyh78M0G+HzfvPfI2g41fifNhT0vQf6z6ZPMKNeKE H+1OJXriKAHuN4hl+jvLY1nrNvYpAZ7g03xpI7XdjOZWc/B0F6U4iUd99iSuTYzeTkQA8Gx1 YM49dSytlDG88WYqPucTvHR1Y/bpEq+q16pyX2IZ6cX0/XGr+eA5NtJBvGheO+4IXOfTpZJp cjNxxcPi8LjtTE+snXGzDyVYrZe//MHa3IZUfapTM6i4idrKbUcFGGzmS/V2tTXg0UD4nDFj cxtMYKKL1nwt9Npdn0Z4wkiNzJvbqc0wggeZMIIGgaADAgECAgp9OASrAAIAAEAOMA0GCSqG SIb3DQEBBQUAMFkxEjAQBgoJkiaJk/IsZAEZFgJjaDEUMBIGCgmSJomT8ixkARkWBGNlcm4x LTArBgNVBAMTJENFUk4gVHJ1c3RlZCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wOTA2 MDMxMDE4MDlaFw0xMDA2MDMxMDE4MDlaMIGOMRIwEAYKCZImiZPyLGQBGRYCY2gxFDASBgoJ kiaJk/IsZAEZFgRjZXJuMRYwFAYDVQQLEw1PcmdhbmljIFVuaXRzMQ4wDAYDVQQLEwVVc2Vy czERMA8GA1UEAxMId2llYmFsY2sxDzANBgNVBAMTBjU1ODUxMDEWMBQGA1UEAxMNQXJuZSBX aWViYWxjazCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMtui3mlLG3UawhQwqsw E+3u1OtffbY/BHiAui+/+6YqWKYWxJDdbKTifFFq3IP4DHNJIbBmrGfNx/6NqcUBRIjcJPHf ABpuG1SiXnRRvbJFMXvN596LaIQV5fToNQqsLEHT61RzpmF1Lzw8PAHheZmZDKMi99XVhvLy 9v6RgZ7K9JbH+Vu9Md0S/qbRZETOevnF8BCPt9rat3u79W5B2Zy4UVeZ6ggmJ1aC9VOZPWki 9iduw5LaiFBaGBV7QGzfFMORQg9oMVLLXG46q4w27Oyd/2sprdVsrMubhyJn1f6L7MU+P00E +jF7ntCXe/VVEjv/uigezFFzNWhY6j+tQtUCAwEAAaOCBCswggQnMB0GA1UdDgQWBBSIqc78 WTkmtitreSqkJV8hgHB+WjAfBgNVHSMEGDAWgBSYzJLQRjA2jLDtmA1yUalHTN2+ITCCATQG A1UdHwSCASswggEnMIIBI6CCAR+gggEbhkdodHRwOi8vY2EuY2Vybi5jaC9jYS9jcmwvQ0VS TiUyMFRydXN0ZWQlMjBDZXJ0aWZpY2F0aW9uJTIwQXV0aG9yaXR5LmNybIaBz2xkYXA6Ly8v Q049Q0VSTiUyMFRydXN0ZWQlMjBDZXJ0aWZpY2F0aW9uJTIwQXV0aG9yaXR5LENOPWNlcm5w a2kwMSxDTj1DRFAsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049 Q29uZmlndXJhdGlvbixEQz1jZXJuLERDPWNoP2NlcnRpZmljYXRlUmV2b2NhdGlvbkxpc3Q/ YmFzZT9vYmplY3RDbGFzcz1jUkxEaXN0cmlidXRpb25Qb2ludDCCAUQGCCsGAQUFBwEBBIIB NjCCATIwaAYIKwYBBQUHMAKGXGh0dHA6Ly9jYS5jZXJuLmNoL2NhL2NybC9jZXJucGtpMDEu Y2Vybi5jaF9DRVJOJTIwVHJ1c3RlZCUyMENlcnRpZmljYXRpb24lMjBBdXRob3JpdHkoMiku Y3J0MIHFBggrBgEFBQcwAoaBuGxkYXA6Ly8vQ049Q0VSTiUyMFRydXN0ZWQlMjBDZXJ0aWZp Y2F0aW9uJTIwQXV0aG9yaXR5LENOPUFJQSxDTj1QdWJsaWMlMjBLZXklMjBTZXJ2aWNlcyxD Tj1TZXJ2aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPWNlcm4sREM9Y2g/Y0FDZXJ0aWZpY2F0 ZT9iYXNlP29iamVjdENsYXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkwDAYDVR0TAQH/BAIw ADAOBgNVHQ8BAf8EBAMCBaAwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIg73QCYLtjQ2G 7Ysrgd71N4WA0GIehb+6A4TEzEwCAWQCAQkwKQYDVR0lBCIwIAYIKwYBBQUHAwIGCCsGAQUF BwMEBgorBgEEAYI3CgMEMBcGA1UdIAQQMA4wDAYKKwYBBAFgCgIBATA1BgkrBgEEAYI3FQoE KDAmMAoGCCsGAQUFBwMCMAoGCCsGAQUFBwMEMAwGCisGAQQBgjcKAwQwRwYDVR0RBEAwPqAl BgorBgEEAYI3FAIDoBcMFWFybmUud2llYmFsY2tAY2Vybi5jaIEVQXJuZS5XaWViYWxja0Bj ZXJuLmNoMEQGCSqGSIb3DQEJDwQ3MDUwDgYIKoZIhvcNAwICAgCAMA4GCCqGSIb3DQMEAgIA gDAHBgUrDgMCBzAKBggqhkiG9w0DBzANBgkqhkiG9w0BAQUFAAOCAQEAc2IypOnSuHzBumpE 6m19OeJk5/riSPdIX2gGt/tM8FBYDuKPwuyqFPHKHvwzQb4fN+898jaDjV+J82FPS9B/rPpk 8wo14oQf7U4leuIoAe43iGX6O8tjWes29ikBnuDTfGkjtd2M5lZz8HQXpTiJR332JK5NjN5O RADwbHVgzj11LK2UMbzxZio+5xO8dHVj9ukSr6rXqnJfYhnpxfT9cav54Dk20kG8aF477ghc 59OlkmlyM3HFw+LwuO1MT6ydcbMPJVitl7/8wdrchlR9qlMzqLiJ2sptRwUYbOZL9Xa1NeDR QPicMWNzG0xgoovWfC302l2fRnjCSI3Mm9upzTGCA0IwggM+AgEBMGcwWTESMBAGCgmSJomT 8ixkARkWAmNoMRQwEgYKCZImiZPyLGQBGRYEY2VybjEtMCsGA1UEAxMkQ0VSTiBUcnVzdGVk IENlcnRpZmljYXRpb24gQXV0aG9yaXR5Agp9OASrAAIAAEAOMAkGBSsOAwIaBQCgggGwMBgG CSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEwMDQyMTE1NTAxNVow IwYJKoZIhvcNAQkEMRYEFIWoXzn2i/O3CoxfeAffxcp8dvHPMF8GCSqGSIb3DQEJDzFSMFAw CwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIB QDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDB2BgkrBgEEAYI3EAQxaTBnMFkxEjAQBgoJkiaJ k/IsZAEZFgJjaDEUMBIGCgmSJomT8ixkARkWBGNlcm4xLTArBgNVBAMTJENFUk4gVHJ1c3Rl ZCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eQIKfTgEqwACAABADjB4BgsqhkiG9w0BCRACCzFp oGcwWTESMBAGCgmSJomT8ixkARkWAmNoMRQwEgYKCZImiZPyLGQBGRYEY2VybjEtMCsGA1UE AxMkQ0VSTiBUcnVzdGVkIENlcnRpZmljYXRpb24gQXV0aG9yaXR5Agp9OASrAAIAAEAOMA0G CSqGSIb3DQEBAQUABIIBADFG4Iwsbvm9D3QIgHE7IYg6FlFQ1jnCPIhwKqWD2Itkl5HdLPyd wr3o8TKIlncSeZZEkh4ZP/F1on7fu+Mjpyx9BcbiKn67+x0fJ+uY+CadKKhuDswMXEi8RNGR /c6S3A8j0I4Gv0i9bSlVkVS9OeGASHWshHb/SvtSgNTynPp1zj4Yo3TMz3OcfmWJmIerfUY6 v6nZs5lDlnvTZSewjfi+iaNscto5Sip48ei1SIdursYuzec4GNwQZkAfhYmsyoZfXFLbKSrQ Z3vfUPjpcKZKr1zWNEcdm4CPCs8cElTs3NDV7elV0qkXPAPXji/kXCM75S6fZHGQL/D10Ecb k9AAAAAAAAA= --------------ms090805020807010902010603-- From adeason@sinenomine.net Wed Apr 21 17:00:51 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Wed, 21 Apr 2010 11:00:51 -0500 Subject: [OpenAFS] Re: Why does 'fs rmm' not resolve symlinks? References: <4BCF006D.50207@cern.ch> <20100421092233.f5ec17d3.adeason@sinenomine.net> Message-ID: <20100421110051.f618b725.adeason@sinenomine.net> On Wed, 21 Apr 2010 09:22:33 -0500 Andrew Deason wrote: > On Wed, 21 Apr 2010 15:41:01 +0200 > Arne Wiebalck wrote: > > > Looking into the code of fs I see that 'lsm' resolves > > symlinks before the stat pioctl, while 'rmm' does not. > > Is there any particular reason for this? > > You would rather it remove the target of the symlink? 'rm' and 'rmdir' > don't work like that, either. Actually, I'm sorry, I realize I misread your original post. I thought you were running 'fs rmm' where the last component was a symlink, but you ran it where one of the intermediary components was a symlink. This is possibly some odd quirk of the code to not resolve the mountpoint when trying to remove it, but I'll need to look. -- Andrew Deason adeason@sinenomine.net From jcowart@stanford.edu Thu Apr 22 05:40:31 2010 From: jcowart@stanford.edu (Jason R Cowart) Date: Wed, 21 Apr 2010 21:40:31 -0700 (PDT) Subject: [OpenAFS] unable to obtain tokens after upgrading to OS X 10.6.3 In-Reply-To: <1817608363.963571271911177029.JavaMail.root@zm02.stanford.edu> Message-ID: <104433500.963681271911231254.JavaMail.root@zm02.stanford.edu> We've had a couple of OS X users report they've been unable to obtain an AFS token after updating to OS X 10.6.3. Here's an output of attempting to obtain a token: Macintosh:~ ernestl$ aklog -d Authenticating to cell ir.stanford.edu (server afsdb1.stanford.edu). Trying to authenticate to user's realm stanford.edu. Getting tickets: afs/ir.stanford.edu@stanford.edu Using Kerberos V5 ticket natively About to resolve name ernestl to id in cell ir.stanford.edu. Id 41904 Set username to AFS ID 41904 Setting tokens. AFS ID 41904 / @ stanford.edu aklog: unable to obtain tokens for cell ir.stanford.edu (status: 11862788). Reinstalling and even upgrading the client to the 1.4.12 release (they'd been using 1.4.11) hasn't helped. The only thing I can find on the status code is: 11862788 (ktc).4 = a pioctl failed Thanks in advance for any advice anyone can offer on next steps. Jason Cowart From hans@MPA-Garching.MPG.DE Thu Apr 22 08:42:45 2010 From: hans@MPA-Garching.MPG.DE (Hans-Werner Paulsen) Date: Thu, 22 Apr 2010 09:42:45 +0200 Subject: [OpenAFS] sqlite on AFS will not work, even with whole-file locking In-Reply-To: References: <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> <20100421112820.GA4623@ncq-5.MPA-Garching.MPG.DE> <0C30D72D-AFBB-4CEA-B707-9B32EBAA9319@inf.ed.ac.uk> <20100421121151.GA4766@ncq-5.MPA-Garching.MPG.DE> <20100421132656.GA5057@ncq-5.MPA-Garching.MPG.DE> Message-ID: <20100422074242.GA3907@ncq-5.MPA-Garching.MPG.DE> On Wed, Apr 21, 2010 at 09:48:27AM -0400, Derrick Brashear wrote: > if you opened it O_RDWR on this client, it better have a valid callback. >=20 > if it's modified and you still have it open, the callback is broken. > if the client doesn't refetch, it's a bug, and it has nothing to do > with locking particularly. I do not know the exact semantics of the AFS filesystem, and therefore I do not know that it is a bug. Is it really a bug? Running the following program on machine A fd =3D open("xxx",O_RDONLY); while (1) { ret =3D fstat(fd,&buf); printf("size: %d mtime: %s",(int)buf.st_size,ctime(&(buf.st_mtime)))= ; sleep(1); } and modifying "xxx" on machine B (e.g. echo "J" >>xxx) reports me the up-to-date information on machine A. But, when I open the file with fd =3D open("xxx",O_RDWR); the stat-information is never updated. This is on i386_linux26 with 1.4.12, but I have seen this behavior foreve= r. Best regards, HW --=20 Hans-Werner Paulsen hans@MPA-Garching.MPG.DE MPI f=FCr Astrophysik Tel 089-30000-2602 Karl-Schwarzschild-Str. 1 Fax 089-30000-2235=09 D-85741 Garching From sxw@inf.ed.ac.uk Thu Apr 22 11:19:57 2010 From: sxw@inf.ed.ac.uk (Simon Wilkinson) Date: Thu, 22 Apr 2010 11:19:57 +0100 Subject: [OpenAFS] sqlite on AFS will not work, even with whole-file locking In-Reply-To: <20100422074242.GA3907@ncq-5.MPA-Garching.MPG.DE> References: <1857482657.1897.1270750692978.JavaMail.root@thunderbeast.private.linuxbox.com> <20100421112820.GA4623@ncq-5.MPA-Garching.MPG.DE> <0C30D72D-AFBB-4CEA-B707-9B32EBAA9319@inf.ed.ac.uk> <20100421121151.GA4766@ncq-5.MPA-Garching.MPG.DE> <20100421132656.GA5057@ncq-5.MPA-Garching.MPG.DE> <20100422074242.GA3907@ncq-5.MPA-Garching.MPG.DE> Message-ID: <00655E0E-9CC4-48AB-8F54-43E79BD6C198@inf.ed.ac.uk> On 22 Apr 2010, at 08:42, Hans-Werner Paulsen wrote: > I do not know the exact semantics of the AFS filesystem, and > therefore I > do not know that it is a bug. Is it really a bug? > Running the following program on machine A > > fd = open("xxx",O_RDONLY); > while (1) { > ret = fstat(fd,&buf); > printf("size: %d mtime: %s", > (int)buf.st_size,ctime(&(buf.st_mtime))); > sleep(1); > } > > and modifying "xxx" on machine B (e.g. echo "J" >>xxx) reports me the > up-to-date information on machine A. > But, when I open the file with > fd = open("xxx",O_RDWR); > the stat-information is never updated. > This is on i386_linux26 with 1.4.12, but I have seen this behavior > forever. Okay, I understand now. And you're right, this is somewhat strange behaviour, which has been there for years. And it won't help in the cooperative locking case, sadly. When a file is opened RW, and is marked as being dirty, the Unix cache manager stores all of that files details locally - it won't update stat information in response to callback breaks, nor will it flush pages that are already in memory, or invalidate chunks on disk. It does this in an attempt to prevent locally made changes from being overwritten by those on the server (because AFS is write-on-close, and our conflict resolution strategy is last-closer-wins). The fact that just opening the file is sufficient to mark it as dirty seems like a bug to me (it's not clear from a quick glance at the code why this is happening, although I wonder if it's related to an attempt to set the atime). In theory this behaviour would be mitigated, for the cooperating processes case at least, by flushing every time we unlock. I haven't yet checked whether we do so, or whether simply doing so is enough to clear the dirty flag, but it should be. S. From hans@MPA-Garching.MPG.DE Thu Apr 22 12:15:34 2010 From: hans@MPA-Garching.MPG.DE (Hans-Werner Paulsen) Date: Thu, 22 Apr 2010 13:15:34 +0200 Subject: [OpenAFS] sqlite on AFS will not work, even with whole-file locking In-Reply-To: <00655E0E-9CC4-48AB-8F54-43E79BD6C198@inf.ed.ac.uk> References: <20100421112820.GA4623@ncq-5.MPA-Garching.MPG.DE> <0C30D72D-AFBB-4CEA-B707-9B32EBAA9319@inf.ed.ac.uk> <20100421121151.GA4766@ncq-5.MPA-Garching.MPG.DE> <20100421132656.GA5057@ncq-5.MPA-Garching.MPG.DE> <20100422074242.GA3907@ncq-5.MPA-Garching.MPG.DE> <00655E0E-9CC4-48AB-8F54-43E79BD6C198@inf.ed.ac.uk> Message-ID: <20100422111534.GA7244@ncq-5.MPA-Garching.MPG.DE> On Thu, Apr 22, 2010 at 11:19:57AM +0100, Simon Wilkinson wrote: > Okay, I understand now. And you're right, this is somewhat strange =20 > behaviour, which has been there for years. And it won't help in the =20 > cooperative locking case, sadly. >=20 > When a file is opened RW, and is marked as being dirty, the Unix cache = =20 > manager stores all of that files details locally - it won't update =20 > stat information in response to callback breaks, nor will it flush =20 > pages that are already in memory, or invalidate chunks on disk. It =20 > does this in an attempt to prevent locally made changes from being =20 > overwritten by those on the server (because AFS is write-on-close, and = =20 > our conflict resolution strategy is last-closer-wins). If you are using "flock" to coordinate access to AFS files from programs running on different machines, it is necessary to get an up-to-date copy from the fileserver as last step of the "lock" call. And you have to flush the local cache to the fileserver before you "unlock" the file. When this is the first step of the flock(LOCK_UN) call, existing programs using "flock" should work without modifications. Best regards, HW --=20 Hans-Werner Paulsen hans@MPA-Garching.MPG.DE MPI f=FCr Astrophysik Tel 089-30000-2602 Karl-Schwarzschild-Str. 1 Fax 089-30000-2235=09 D-85741 Garching From adeason@sinenomine.net Thu Apr 22 16:14:44 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Thu, 22 Apr 2010 10:14:44 -0500 Subject: [OpenAFS] Re: Why does 'fs rmm' not resolve symlinks? References: <4BCF006D.50207@cern.ch> <20100421092233.f5ec17d3.adeason@sinenomine.net> <20100421110051.f618b725.adeason@sinenomine.net> Message-ID: <20100422101444.4feb65e3.adeason@sinenomine.net> On Wed, 21 Apr 2010 11:00:51 -0500 Andrew Deason wrote: > This is possibly some odd quirk of the code to not resolve the > mountpoint when trying to remove it, but I'll need to look. 'fs rmm' just explicitly doesn't resolve symlinks. I don't know why; it's the only 'fs' command to do so. My original thought had something to do with avoiding resolving the final to-be-removed mountpoint, but that doesn't make sense, since the directory-portion and mountpoint-portion are separate arguments. Either this is a bug or there's some corner case where not resolving symlinks is desirable that I'm not seeing. A fix is in . -- Andrew Deason adeason@sinenomine.net From jasonmc@sei.cmu.edu Thu Apr 22 17:49:14 2010 From: jasonmc@sei.cmu.edu (Jason D. McCormick) Date: Thu, 22 Apr 2010 12:49:14 -0400 Subject: [OpenAFS] OpenAFS + Windows 7 (x64) Message-ID: <81BFFE1EFAD6894D9992C1B6D2A255B5D03C52BCA2@EXCHANGE.sei.cmu.edu> We're trying to deploy new workstations based on Windows 7 using OpenAFS (1.5.73) and Kerberos for Windows. I was curious how/if people are getting= a working configuration for this setup. We're encountering two major proble= ms that I was hoping someone on the list had already encountered and could hel= p out with. #1 - \\AFS UNC name doesn't function when making network transitions, notab= ly when using the Cisco VPN client but it also appears to die at other random unrepeatable intervals (although this is during testing work). It appears that while on certain network configurations (e.g. wired physically to the network) the \\AFS appears to work and is bound to the AFS loopback adapter (10.254.254.254). However unplugging the network and/or opening the VPN appear to cause some sort of network state transition that kills off the mappings. I found a reference to a similar problem () wher= e Jeff said the bug is in Windows. Does anyone know if there's a workaround = or hotfix since then? #2 - The Windows team is using folder redirection within profiles, but only selectively (e.g. Documents, Desktop, AppData). However something within t= he synchronization service seems to think that \\AFS should somehow be availab= le offline. We keep seeing explorer.exe routinely consume 50% or more of the = CPU and it appears to be continuously trying to open C:\Windows\CSC\v2.0.6\namespace\afs even though we don't have the filesyste= m marked as being available offline. Am I correct in understanding from the thread above () that this is also part of the SMB bug? If there's an implementation guide for Win7 I'm missing, please point it out. Thanks. -- Jason McCormick Unix Team Lead, Systems Group, IT Software Engineering Institute, Carnegie Mellon Univ. E: jasonmc@sei.cmu.edu From l.schimmer@cgv.tugraz.at Thu Apr 22 18:20:35 2010 From: l.schimmer@cgv.tugraz.at (Lars Schimmer) Date: Thu, 22 Apr 2010 19:20:35 +0200 Subject: [OpenAFS] OpenAFS + Windows 7 (x64) In-Reply-To: <81BFFE1EFAD6894D9992C1B6D2A255B5D03C52BCA2@EXCHANGE.sei.cmu.edu> References: <81BFFE1EFAD6894D9992C1B6D2A255B5D03C52BCA2@EXCHANGE.sei.cmu.edu> Message-ID: <4BD08563.4000307@cgv.tugraz.at> On 22.04.2010 18:49, Jason D. McCormick wrote: > We're trying to deploy new workstations based on Windows 7 using OpenAF= S > (1.5.73) and Kerberos for Windows. I was curious how/if people are get= ting a > working configuration for this setup. We're encountering two major pr= oblems > that I was hoping someone on the list had already encountered and could= help > out with. >=20 > #1 - \\AFS UNC name doesn't function when making network transitions, n= otably > when using the Cisco VPN client but it also appears to die at other ran= dom > unrepeatable intervals (although this is during testing work). It appe= ars > that while on certain network configurations (e.g. wired physically to = the > network) the \\AFS appears to work and is bound to the AFS loopback ada= pter > (10.254.254.254). However unplugging the network and/or opening the VP= N > appear to cause some sort of network state transition that kills off th= e > mappings. I found a reference to a similar problem > () = where > Jeff said the bug is in Windows. Does anyone know if there's a workaro= und or > hotfix since then? Looks like thats the bug. Til yet no bugfix nor workaround. For luck my Win7 x86 Laptop has not shown any sign of that bug: sleepmode, hybernate, adding/removing network interfaces does not prohibite the use of OpenAFS via \\AFS\... Other workstations/laptops at our site do have that bug. But I haven=B4t found the reason why it works on my laptop and not on the others. > If there's an implementation guide for Win7 I'm missing, please point > it out. Thanks. Not that I know of any trick. > -- > Jason McCormick > Unix Team Lead, Systems Group, IT > Software Engineering Institute, Carnegie Mellon Univ. > E: jasonmc@sei.cmu.edu MfG, Lars Schimmer --=20 ------------------------------------------------------------- TU Graz, Institut f=FCr ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer@cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 From jasonmc@cert.org Thu Apr 22 18:40:10 2010 From: jasonmc@cert.org (Jason D. McCormick) Date: Thu, 22 Apr 2010 13:40:10 -0400 Subject: [OpenAFS] OpenAFS + Windows 7 (x64) In-Reply-To: <4BD08563.4000307@cgv.tugraz.at> References: <81BFFE1EFAD6894D9992C1B6D2A255B5D03C52BCA2@EXCHANGE.sei.cmu.edu> <4BD08563.4000307@cgv.tugraz.at> Message-ID: <0d4101cae242$db113f60$9133be20$@org> This is a multi-part message in MIME format. ------=_NextPart_000_0D3D_01CAE221.53A2B250 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > Looks like thats the bug. > Til yet no bugfix nor workaround. > For luck my Win7 x86 Laptop has not shown any sign of that bug: > sleepmode, hybernate, adding/removing network interfaces does not > prohibite the use of OpenAFS via \\AFS\... > Other workstations/laptops at our site do have that bug. But I = haven=B4t > found the reason why it works on my laptop and not on the others. Ours seems to be generally when dealing with VPN software. We're = continuing to poke. Anyone know if there ever was a bug opened with Microsoft that = we could follow-up with through our Microsoft channels? > > If there's an implementation guide for Win7 I'm missing, please = point > > it out. Thanks. >=20 > Not that I know of any trick. We're having some weird problems gettings KfW/NIM to import/use = credentials out of the MSLSA cache as well. I thought maybe someone had documented = a Win7 + KfW + OpenAFS guide somewhere. We seem to be hitting every odd snag = in the world. - Jason ------=_NextPart_000_0D3D_01CAE221.53A2B250 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIVEzCCBDow ggMioAMCAQICAQUwDQYJKoZIhvcNAQEFBQAwTTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4g R292ZXJubWVudDEMMAoGA1UECxMDRUNBMRYwFAYDVQQDEw1FQ0EgUm9vdCBDQSAyMB4XDTA4MDQw NDE0MjQ0OVoXDTI4MDMzMDE0MjQ0OVowTTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4gR292 ZXJubWVudDEMMAoGA1UECxMDRUNBMRYwFAYDVQQDEw1FQ0EgUm9vdCBDQSAyMIIBIjANBgkqhkiG 9w0BAQEFAAOCAQ8AMIIBCgKCAQEAs5DYHu+a7W5HsUZhRo2jVgicSjLHRfLSpKRmvn49l4Dv6ddr 6eDAO43i+BL6EzWkzVqGi7DQLzSM9wXth2+nMBfQFsZYRr2V+VYaiNROHn5YHxuicxWdXosGJBN2 PJ9gYq2wtfTgJMFT99kcNx3mPPD60/H5oZjxN4XYzwJg8KA4lEtRKAnCF/xApGF5DrSMGyCCYvXk mtYpijb6H4HAoRExS/5W/di/UZMnWdr1gz5EpN/VIGfrnwCn+94xtmMxHD33HGwJjX/0upyofB8B xoBtAQHYN6j+LX0rwsvW6Zy6lI12Ft7MgXUEe0F3FWUVyawAtr/rHNy5jWQt/zXbxQIDAQABo4IB IzCCAR8wHQYDVR0OBBYEFO3kh9AnxFDmhDr3zPfrOkn8Uk4hMA4GA1UdDwEB/wQEAwIBhjAPBgNV HRMBAf8EBTADAQH/MIHcBggrBgEFBQcBCwSBzzCBzDBDBggrBgEFBQcwBYY3aHR0cDovL2NybC5n ZHMuZGlzYS5taWwvZ2V0SXNzdWVkQnk/RUNBJTIwUm9vdCUyMENBJTIwMjCBhAYIKwYBBQUHMAWG eGxkYXA6Ly9jcmwuZ2RzLmRpc2EubWlsL2NuJTNkRUNBJTIwUm9vdCUyMENBJTIwMiUyY291JTNk RUNBJTJjbyUzZFUuUy4lMjBHb3Zlcm5tZW50JTJjYyUzZFVTP2Nyb3NzQ2VydGlmaWNhdGVQYWly O2JpbmFyeTANBgkqhkiG9w0BAQUFAAOCAQEASswb54WIkyPZub7PuvE1lMFLPBNwXYMuTn7BVg8t wX4fDend/gKZfGDjhqq5hiPDF37HEQ/j0EJWoxzzcI+xiJG1vA6JJWbIP182Kg4+tmdAjD1A36di 4DgY+iRtLSPTwLh0XpVEVHohlw9azcP8lT0iIhXdGGBdhTepTfeB/L1KpliMT7/HZaH/4tM0SBoX ATLyhPPeBbJkSZg3zSH1qIFbZMXafFiwYWEfrcCt7TS2lKvHnOxllymFlJQzxDUkiz3N/Dcqu/qk thuQ8pVXF0jg76mdrQDisWTZZ3kRg7ma6AsyNs4gZ+N6bUvqXlPlLzBB3fjlVJ2p12nGddlFRzCC BW4wggRWoAMCAQICD3GamXt44tgVo7bMgf5ZSDANBgkqhkiG9w0BAQUFADCBmTELMAkGA1UEBhMC VVMxGDAWBgNVBAoTD1UuUy4gR292ZXJubWVudDEMMAoGA1UECxMDRUNBMSIwIAYDVQQLExlDZXJ0 aWZpY2F0aW9uIEF1dGhvcml0aWVzMT4wPAYDVQQDEzVWZXJpU2lnbiBDbGllbnQgRXh0ZXJuYWwg Q2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHMjAeFw0wOTExMTkwMDAwMDBaFw0xMjEyMDkyMzU5 NTlaMIGNMQswCQYDVQQGEwJVUzEYMBYGA1UEChMPVS5TLiBHb3Zlcm5tZW50MQwwCgYDVQQLEwNF Q0ExFzAVBgNVBAsTDlZlcmlTaWduLCBJbmMuMSMwIQYDVQQLFBpDYXJuZWdpZSBNZWxsb24gVW5p dmVyc2l0eTEYMBYGA1UEAxMPSmFzb24gTWNDb3JtaWNrMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A MIIBCgKCAQEAwcZLyvKFiy5uWjvy6P3EgG5kUcNKW0TTb/IZt1y9reHhqM26bTAAiKJ5qR0irjgR GGLK6SC//tjIIvBTqXxkrluXr1e2dMPJqR3i3dQ/C/yH/2sPNdAvPHbJhL4FlUMk7HFrstB+hjQW kIYnX+6J0YMEtgYm+o8NMYPSf9R49hkhJpFAQAMbex3xlqYmzjTxdiyILYwFnW6Z76JRzG4Ntr+X ySkX1+1JvC7MDblwU08hZbmKVjjdj6jnwrSpEypPeP9UuimJGzw5UGPoxUHVHWIZAQUhQET99Xqp 8LFNf+xWF2nL+JzJnle62u69Ob0o5VWL363W9eTzNO5q1CC2QwIDAQABo4IBuzCCAbcwUQYDVR0f BEowSDBGoESgQoZAaHR0cDovL2VjYS1jbGllbnQtY3JsLnZlcmlzaWduLmNvbS9WZXJpU2lnbkVD QTIwNDgvTGF0ZXN0Q1JMLmNybDAOBgNVHQ8BAf8EBAMCBsAwHQYDVR0OBBYEFEzwN9mpwRVJWp3k 54qWbxd/jdTRMB8GA1UdIwQYMBaAFA1PwsXaE5AiF91QXAr0IUv8cigaMB4GA1UdEQQXMBWBE2ph c29ubWNAc2VpLmNtdS5lZHUwgYAGCCsGAQUFBwEBBHQwcjA/BggrBgEFBQcwAoYzaHR0cHM6Ly9l Y2EyMDQ4LnZlcmlzaWduLmNvbS9DQS9WZXJpU2lnbkVDQTIwNDguY2VyMC8GCCsGAQUFBzABhiNo dHRwOi8vZWNhLWNsaWVudC1vY3NwLnZlcmlzaWduLmNvbTBSBgNVHSAESzBJMEcGCmCGSAFlAwIB DAEwOTA3BggrBgEFBQcCARYraHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvZWNh L2NwczAbBgNVHQkEFDASMBAGCCsGAQUFBwkEMQQTAlVTMA0GCSqGSIb3DQEBBQUAA4IBAQAIcndw xvmNUMXkrWwK8XbdOqSHdn8OQm8E6BIfX/YX7FH6zsEfLkvooL0xl7JIqDBXe+qPSkvIlEMj/JH7 pcPLw7cVRls7KPOb9+ZLkz+6OaHoKPENg4ahsVoAckncBjTuDMWan8HopjIj6fIIainjWEyJkUye VPwkyZdBBA3tDjrO8La58YbEbMDooP8I2PfMr9HnCw2OjWRUK24qOxjd2VFszd1A61+O/fhtzY/M ODMshE9/zMUuh7XnhSAfRRPSLzDEz2mErUQ6KmlmKYazIFdmztVB+BEDNFgrkaDEs/jACXEVyCvL kekGkMXrdbuCSiNYi/7d0BR79vNnR5sYMIIFbzCCBFegAwIBAgIQBqTMOXVcn9qRgE2571awDjAN BgkqhkiG9w0BAQUFADCBmTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4gR292ZXJubWVudDEM MAoGA1UECxMDRUNBMSIwIAYDVQQLExlDZXJ0aWZpY2F0aW9uIEF1dGhvcml0aWVzMT4wPAYDVQQD EzVWZXJpU2lnbiBDbGllbnQgRXh0ZXJuYWwgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHMjAe Fw0wOTExMTkwMDAwMDBaFw0xMjEyMDkyMzU5NTlaMIGNMQswCQYDVQQGEwJVUzEYMBYGA1UEChMP VS5TLiBHb3Zlcm5tZW50MQwwCgYDVQQLEwNFQ0ExFzAVBgNVBAsTDlZlcmlTaWduLCBJbmMuMSMw IQYDVQQLFBpDYXJuZWdpZSBNZWxsb24gVW5pdmVyc2l0eTEYMBYGA1UEAxMPSmFzb24gTWNDb3Jt aWNrMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoPqz0tzbMFRF6OsTN1GSejPAhsCq R5TytmI2QZX+Il7Bc2dr8hrDvK/iPTPQvC+tojgvcYt86Cm7HM09L2XJSCN/lC/8WZGsM9fvOq0J mn4IPT3OQk97DVecapfcd4rjFUgr39PiKqqtNSxDmJBN9Xml9HCXlY6V1I1FvXkz2QzjiOV9mhiJ f0M40R7+53ES+NQi7ocC/0baFB2kwdV+LaatIMl4p8TOEBTeYySWyHbWPWRW1laZxoQ55CgHvS4T BwfhSciIcRpM6xSiTlvzzy0FtedekVST5j2+Ax/omifU3x+p8PAiuNZpYmAvRsdfgPXfbR74hRp6 R2ZjRX4GLQIDAQABo4IBuzCCAbcwUQYDVR0fBEowSDBGoESgQoZAaHR0cDovL2VjYS1jbGllbnQt Y3JsLnZlcmlzaWduLmNvbS9WZXJpU2lnbkVDQTIwNDgvTGF0ZXN0Q1JMLmNybDAOBgNVHQ8BAf8E BAMCBSAwHQYDVR0OBBYEFPvmYCop3Syh128z5fqTk8ImImpfMB8GA1UdIwQYMBaAFA1PwsXaE5Ai F91QXAr0IUv8cigaMB4GA1UdEQQXMBWBE2phc29ubWNAc2VpLmNtdS5lZHUwgYAGCCsGAQUFBwEB BHQwcjA/BggrBgEFBQcwAoYzaHR0cHM6Ly9lY2EyMDQ4LnZlcmlzaWduLmNvbS9DQS9WZXJpU2ln bkVDQTIwNDguY2VyMC8GCCsGAQUFBzABhiNodHRwOi8vZWNhLWNsaWVudC1vY3NwLnZlcmlzaWdu LmNvbTBSBgNVHSAESzBJMEcGCmCGSAFlAwIBDAEwOTA3BggrBgEFBQcCARYraHR0cHM6Ly93d3cu dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvZWNhL2NwczAbBgNVHQkEFDASMBAGCCsGAQUFBwkEMQQT AlVTMA0GCSqGSIb3DQEBBQUAA4IBAQBFNYqDFMcXtWKGW4wBfD1F+9OaQvrcZ9xiqfA1sl3ozG8H lg1dam7gka5NfziQczSCRFWCO71TAbZelJSotTlNJGA5jEEcvfdFGSYm9ugSqBrE7W8o2kUnqp9x tgAZCr3UTo6ZXRHogxBmihgQ/+Fdrfz16CRkBPbzH4qTt21vtHUnv9rUbxk8g8kQNE//70+f1RMZ CSurN/LNwtzCAZaetUZdWT2RKfOHFRxITwy3P2C0x+5xzreO1rv44r5J2uWicf2wj/x8+gBRb1ah gO+Veaf3qf1lr0tm80xe8+vVIPuH7nhzzB6HN3ClOV8FxF7+Hho9ZxePomY82qFB1u6gMIIF7DCC BNSgAwIBAgIBCjANBgkqhkiG9w0BAQUFADBNMQswCQYDVQQGEwJVUzEYMBYGA1UEChMPVS5TLiBH b3Zlcm5tZW50MQwwCgYDVQQLEwNFQ0ExFjAUBgNVBAMTDUVDQSBSb290IENBIDIwHhcNMDgwNzAy MTQ0MTE4WhcNMTQwNzAxMTQ0MTE4WjCBmTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4gR292 ZXJubWVudDEMMAoGA1UECxMDRUNBMSIwIAYDVQQLExlDZXJ0aWZpY2F0aW9uIEF1dGhvcml0aWVz MT4wPAYDVQQDEzVWZXJpU2lnbiBDbGllbnQgRXh0ZXJuYWwgQ2VydGlmaWNhdGlvbiBBdXRob3Jp dHkgLSBHMjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALwLnuuN8oZoDYAkOM7mIXhe h2AdsF/aDXCOYuKLvIwGjEIrJsqT06i1nIkHFf7xGP4Pg9tUoFO6oIhJjqkTdCRO5uOhPN8UEPFm Y1+pI0Hxjz/iiA80c5Adc2fMHmjuejcYFl/UjhMjFMuZxC5e6nt/PmqMLRwF0sExlLiEi6pHdgTz t16J9zCSn3H3fCx2H3PxfpIs88Kxqf2tP0eSP3VII4CzpCSwAqqljLdWRceffAICgbFx6QpPsyMt vyu5JRmJYbYh9umJLw1vkMEGl2GLbD28zyOKek0wvXqpegtaYywvGA5PSx1MqAjxdkAgjFU2B7dp NenUp5b8r7XZ2RcCAwEAAaOCAogwggKEMBIGA1UdEwEB/wQIMAYBAf8CAQAwDgYDVR0PAQH/BAQD AgGGMC0GA1UdEQQmMCSkIjAgMR4wHAYDVQQDExVQcml2YXRlTGFiZWw0LTIwNDgtODEwHQYDVR0O BBYEFA1PwsXaE5AiF91QXAr0IUv8cigaMB8GA1UdIwQYMBaAFO3kh9AnxFDmhDr3zPfrOkn8Uk4h MDMGA1UdIAQsMCowDAYKYIZIAWUDAgEMATAMBgpghkgBZQMCAQwCMAwGCmCGSAFlAwIBDAMwgcgG A1UdHwSBwDCBvTA0oDKgMIYuaHR0cDovL2NybC5kaXNhLm1pbC9nZXRjcmw/RUNBJTIwUm9vdCUy MENBJTIwMjCBhKCBgaB/hn1sZGFwOi8vY3JsLmdkcy5kaXNhLm1pbC9jbiUzZEVDQSUyMFJvb3Ql MjBDQSUyMDIlMmNvdSUzZEVDQSUyY28lM2RVLlMuJTIwR292ZXJubWVudCUyY2MlM2RVUz9jZXJ0 aWZpY2F0ZVJldm9jYXRpb25MaXN0O2JpbmFyeTCB7gYIKwYBBQUHAQEEgeEwgd4wPwYIKwYBBQUH MAKGM2h0dHA6Ly9jcmwuZGlzYS5taWwvZ2V0SXNzdWVkVG8/RUNBJTIwUm9vdCUyMENBJTIwMjCB mgYIKwYBBQUHMAKGgY1sZGFwOi8vY3JsLmdkcy5kaXNhLm1pbC9jbiUzZEVDQSUyMFJvb3QlMjBD QSUyMDIlMmNvdSUzZEVDQSUyY28lM2RVLlMuJTIwR292ZXJubWVudCUyY2MlM2RVUz9jQUNlcnRp ZmljYXRlO2JpbmFyeSxjcm9zc0NlcnRpZmljYXRlUGFpcjtiaW5hcnkwDQYJKoZIhvcNAQEFBQAD ggEBALJeQM4LZEc8g2EFanpxgiYpo5lrosDGbDccbPXizubWq+AsRdwomRVfxLOMLyaZUWs2w2AJ v7yL35bNCOKWdACTj3fXU8khVtV5BsCNSeBP1zavf7hjQpVYkejpmCG8DMbGrJ7mC6makqmd/S/V KjHVzm/iDX3MKhIS6sjoSEgU2KhM5SKFJ0t8eoZ1B5kplnfGr1yAnYXKPJTQVnWenu7vNBK9u0LC 1XdsfmowJtcLhiU8f43Xsp//vu3S/9Tg/THK2LMtR7AYDSFgP2+YawPqQ/ElSIZoHUJQfbTKAvsj X158kXsnY2wvH2WdMMpHmj7GvikIw/tP/7w9/uwe6mExggPiMIID3gIBATCBrTCBmTELMAkGA1UE BhMCVVMxGDAWBgNVBAoTD1UuUy4gR292ZXJubWVudDEMMAoGA1UECxMDRUNBMSIwIAYDVQQLExlD ZXJ0aWZpY2F0aW9uIEF1dGhvcml0aWVzMT4wPAYDVQQDEzVWZXJpU2lnbiBDbGllbnQgRXh0ZXJu YWwgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHMgIPcZqZe3ji2BWjtsyB/llIMAkGBSsOAwIa BQCgggIJMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEwMDQyMjE3 NDAwOVowIwYJKoZIhvcNAQkEMRYEFM3H5mGmG8FXl9KUpFTWDn3LWwD6MCQGCSqGSIb3DQEJDzEX MBUwCgYIKoZIhvcNAwcwBwYFKw4DAhowgb8GCSsGAQQBgjcQBDGBsTCBrjCBmTELMAkGA1UEBhMC VVMxGDAWBgNVBAoTD1UuUy4gR292ZXJubWVudDEMMAoGA1UECxMDRUNBMSIwIAYDVQQLExlDZXJ0 aWZpY2F0aW9uIEF1dGhvcml0aWVzMT4wPAYDVQQDEzVWZXJpU2lnbiBDbGllbnQgRXh0ZXJuYWwg Q2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHMgIQBqTMOXVcn9qRgE2571awDjCBwQYLKoZIhvcN AQkQAgsxgbGgga4wgZkxCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAK BgNVBAsTA0VDQTEiMCAGA1UECxMZQ2VydGlmaWNhdGlvbiBBdXRob3JpdGllczE+MDwGA1UEAxM1 VmVyaVNpZ24gQ2xpZW50IEV4dGVybmFsIENlcnRpZmljYXRpb24gQXV0aG9yaXR5IC0gRzICEAak zDl1XJ/akYBNue9WsA4wDQYJKoZIhvcNAQEBBQAEggEAcXUNlNslaEAJ1b/NkvOUDnKBLZEwmbdx EM7XFBkRcNU9gO43OjuQj2WdyBJz2qHu8sFIGpIu8N23VgbrTsTl0fPBnfrcXTs5Oak0NNr6S/dQ w3XoqpjSIGBFVM5TAeihVwnoyot5xjbfVsZHGtEPDC6a5r5klpjEp7uOb/ISCpGuwg0vGI14CHwu tYzGtj3mohLWsvZr/HE6XuKJj4upfYW4hnEoUXcrIFBDA32NyONkLlUtl09eFKcLW2+jyUPsZE7h Dld0L3WvcShQt24zvwWWfJNLXIgNB97cFjHrHPaO7t6n74Qb+zZmDBUumuwz5tJYoaRP50zz3e7B JgFEqQAAAAAAAA== ------=_NextPart_000_0D3D_01CAE221.53A2B250-- From botsch@cnf.cornell.edu Thu Apr 22 19:07:02 2010 From: botsch@cnf.cornell.edu (Dave B) Date: Thu, 22 Apr 2010 14:07:02 -0400 Subject: [OpenAFS] OpenAFS + Windows 7 (x64) In-Reply-To: <81BFFE1EFAD6894D9992C1B6D2A255B5D03C52BCA2@EXCHANGE.sei.cmu.edu> References: <81BFFE1EFAD6894D9992C1B6D2A255B5D03C52BCA2@EXCHANGE.sei.cmu.edu> Message-ID: <1271959622.3939.17.camel@water.cnf.cornell.edu> Re folder redirection, we are using folder redirection to a user profile in AFS. But, we turned off Offline File Synch altogether in group policy. While having offline file synch on sped up logins and general use, with credentials being destroyed on logout, files would not sync until the next time the user logged back on. With the exception of Windows 7 periodically hanging at "Welcome" while logging on (nothing in the logs, so, the hang would appear to happen before afslogon.dll gets a chance to log anything), Win 7/AFS seems to work well, so far. So far, we have not seen the 50% cpu explorer issue. > > -- > Jason McCormick > Unix Team Lead, Systems Group, IT > Software Engineering Institute, Carnegie Mellon Univ. > E: jasonmc@sei.cmu.edu > > > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info -- ******************************** David William Botsch Programmer/Analyst CNF Computing botsch@cnf.cornell.edu ******************************** From mlane@sinenomine.net Thu Apr 22 20:28:42 2010 From: mlane@sinenomine.net (Mickey Lane) Date: Thu, 22 Apr 2010 14:28:42 -0500 Subject: [OpenAFS] OpenAFS + Windows 7 (x64) In-Reply-To: <0d4101cae242$db113f60$9133be20$@org> References: <81BFFE1EFAD6894D9992C1B6D2A255B5D03C52BCA2@EXCHANGE.sei.cmu.edu> <4BD08563.4000307@cgv.tugraz.at> <0d4101cae242$db113f60$9133be20$@org> Message-ID: <1171E06FDB4D8341937880DCD831A0E2671E1049@34093-MBX-C15.mex07a.mlsrvr.com> Re: Loopback + VPN problems on Windows 7 > Anyone know if there ever was a bug opened with Microsoft > that we could follow-up with through our Microsoft channels? Microsoft is currently working on this issue. No ETA on the fix though. From jaltman@secure-endpoints.com Thu Apr 22 20:40:23 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Thu, 22 Apr 2010 20:40:23 +0100 Subject: [OpenAFS] Re: Why does 'fs rmm' not resolve symlinks? In-Reply-To: <20100422101444.4feb65e3.adeason@sinenomine.net> References: <4BCF006D.50207@cern.ch> <20100421092233.f5ec17d3.adeason@sinenomine.net> <20100421110051.f618b725.adeason@sinenomine.net> <20100422101444.4feb65e3.adeason@sinenomine.net> Message-ID: <4BD0A627.4060509@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms090106020006000602000905 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/22/2010 4:14 PM, Andrew Deason wrote: > On Wed, 21 Apr 2010 11:00:51 -0500 > Andrew Deason wrote: >=20 >> This is possibly some odd quirk of the code to not resolve the >> mountpoint when trying to remove it, but I'll need to look. >=20 > 'fs rmm' just explicitly doesn't resolve symlinks. I don't know why; > it's the only 'fs' command to do so. My original thought had something > to do with avoiding resolving the final to-be-removed mountpoint, but > that doesn't make sense, since the directory-portion and > mountpoint-portion are separate arguments. >=20 > Either this is a bug or there's some corner case where not resolving > symlinks is desirable that I'm not seeing. A fix is in > . >=20 I'm sure this is just broken. I fixed this in the Windows client years a= go. Jeffrey Altman --------------ms090106020006000602000905 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MjIxOTQwMjNaMCMGCSqGSIb3DQEJBDEWBBSPh/ln A3tKu30ewv1FbkwNi3x38DBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAETfTvOwdIQ+8W7NRaHivBCieE+nSgq2hqQM lg8ikOejyshgkezx5B5mm0IZ9kyRpHK7EDxYCejoYgouWldfjRKInXKYuOkGph5SYlHT+BMf yFxhOTvFGRhIQSwBrFRp+wR4cLRN4jPmHKxc8KeqgwBjZScN+/ZOeHWkUleKxnT2w4VNskTA 7oAtvNhcWxypzCkHVV0u15rbPhYhdjv8VfDrHlxMfPbty9JBFZrn64q1dzFaX1roNfwl1DDd iaYwGszKGv+zXYRcUhKbIXrJTsNlDSqMvRzAoCidhxJvqtfxLBvUg11kk29ysbC/0ZReV2RK WM0qc+TcZ32n98jETvUAAAAAAAA= --------------ms090106020006000602000905-- From jaltman@secure-endpoints.com Thu Apr 22 20:52:56 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Thu, 22 Apr 2010 20:52:56 +0100 Subject: [OpenAFS] OpenAFS + Windows 7 (x64) In-Reply-To: <81BFFE1EFAD6894D9992C1B6D2A255B5D03C52BCA2@EXCHANGE.sei.cmu.edu> References: <81BFFE1EFAD6894D9992C1B6D2A255B5D03C52BCA2@EXCHANGE.sei.cmu.edu> Message-ID: <4BD0A918.4000400@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms030706070202010602020108 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/22/2010 5:49 PM, Jason D. McCormick wrote: > We're trying to deploy new workstations based on Windows 7 using OpenAF= S > (1.5.73) and Kerberos for Windows. I was curious how/if people are get= ting a > working configuration for this setup. We're encountering two major pr= oblems > that I was hoping someone on the list had already encountered and could= help > out with. >=20 > #1 - \\AFS UNC name doesn't function when making network transitions, n= otably > when using the Cisco VPN client but it also appears to die at other ran= dom > unrepeatable intervals (although this is during testing work). It appe= ars > that while on certain network configurations (e.g. wired physically to = the > network) the \\AFS appears to work and is bound to the AFS loopback ada= pter > (10.254.254.254). However unplugging the network and/or opening the VP= N > appear to cause some sort of network state transition that kills off th= e > mappings. I found a reference to a similar problem > () = where > Jeff said the bug is in Windows. Does anyone know if there's a workaro= und or > hotfix since then? There is no work around. Microsoft has known about this bug since September 2009. More sites need to file bug reports on this issue with Microsoft. Until Microsoft is convinced that this is a serious problem they are not going to make it a priority. SP1 betas have already been cut and if this bug is going to be fixed and added to SP1, they need to hear from a broad range of OpenAFS using sites. There really is nothing more that I can do until Microsoft decides the problem is a serious problem for *their* customers. > #2 - The Windows team is using folder redirection within profiles, but = only > selectively (e.g. Documents, Desktop, AppData). However something with= in the > synchronization service seems to think that \\AFS should somehow be ava= ilable > offline. We keep seeing explorer.exe routinely consume 50% or more of = the CPU > and it appears to be continuously trying to open > C:\Windows\CSC\v2.0.6\namespace\afs even though we don't have the files= ystem > marked as being available offline. Am I correct in understanding from = the > thread above > () > that this is also part of the SMB bug? This is the AFS Explorer Shell extension attempting to perform AFS if operations which are spinning due to the fact that the Netbios name resolution is failing. Its the same bug as above. > If there's an implementation guide for Win7 I'm missing, please point > it out. Thanks. There isn't one. There is nothing different about installing on Windows 7. Microsoft has a bug and it must get fixed by Microsoft. It won't get fixed until enough end user sites report it. Jeffrey Altman --------------ms030706070202010602020108 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MjIxOTUyNTZaMCMGCSqGSIb3DQEJBDEWBBSJlxfu kSL4EwohAdh2tEQSDzt0gzBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBABHA+zjuQ/OY/Fj8cgq34qPKaLH2XsdbH3N8 DZwWkULmwJqTE+Bf2oDRRsXS5aUkhWfZYk4oewOhVOBVQEMq0YTl2Bf60EZDFB5WUChHldNI fdV8C4MFrNRIy8a/gDxmJ5hpMA5lWEH67krRCGG/UnIAC89QCBav48X7+lRNLurgxIAVDK7j KosFhgWRJRNJL4jZavGl0zZkJ21Ssy8YnywXFa4sp3A6PBvmXpplTlxSp8LNXjx0TICAyfqg CnLmfZmb2U5gq5wRJeZ1Oin+odagrzjXcdBvH+Hu5Ci9+YqqHH5i0C4g6pjBhCkE39HbR7H8 pwm+/9gbqP4f2vLKIqwAAAAAAAA= --------------ms030706070202010602020108-- From jasonmc@cert.org Thu Apr 22 21:59:52 2010 From: jasonmc@cert.org (Jason D. McCormick) Date: Thu, 22 Apr 2010 16:59:52 -0400 Subject: [OpenAFS] OpenAFS + Windows 7 (x64) In-Reply-To: <4BD0A918.4000400@secure-endpoints.com> References: <81BFFE1EFAD6894D9992C1B6D2A255B5D03C52BCA2@EXCHANGE.sei.cmu.edu> <4BD0A918.4000400@secure-endpoints.com> Message-ID: <001701cae25e$c13416a0$439c43e0$@org> Jeff, > There is no work around. Microsoft has known about this bug since > September 2009. More sites need to file bug reports on this issue = with > Microsoft. Until Microsoft is convinced that this is a serious = problem > they are not going to make it a priority. SP1 betas have already been > cut and if this bug is going to be fixed and added to SP1, they need = to > hear from a broad range of OpenAFS using sites. >=20 > There really is nothing more that I can do until Microsoft decides the > problem is a serious problem for *their* customers. Can you point me to the bug report reference, number, whatever within = Microsoft to the issue? We'll file a support request with MS Premier = Support, we just need to now want to send our TAM after. Thanks. - Jason From jaltman@secure-endpoints.com Thu Apr 22 22:12:37 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Thu, 22 Apr 2010 22:12:37 +0100 Subject: [OpenAFS] OpenAFS + Windows 7 (x64) In-Reply-To: <001701cae25e$c13416a0$439c43e0$@org> References: <81BFFE1EFAD6894D9992C1B6D2A255B5D03C52BCA2@EXCHANGE.sei.cmu.edu> <4BD0A918.4000400@secure-endpoints.com> <001701cae25e$c13416a0$439c43e0$@org> Message-ID: <4BD0BBC5.3070803@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms000808040002000707040505 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/22/2010 9:59 PM, Jason D. McCormick wrote: > Jeff, >=20 >> There is no work around. Microsoft has known about this bug since >> September 2009. More sites need to file bug reports on this issue wit= h >> Microsoft. Until Microsoft is convinced that this is a serious proble= m >> they are not going to make it a priority. SP1 betas have already been= >> cut and if this bug is going to be fixed and added to SP1, they need t= o >> hear from a broad range of OpenAFS using sites. >> >> There really is nothing more that I can do until Microsoft decides the= >> problem is a serious problem for *their* customers. >=20 > Can you point me to the bug report reference, number, whatever within M= icrosoft to the issue? > We'll file a support request with MS Premier Support, we just need to n= ow want to send our TAM after. Unfortunately, I can't provide one. I'm not allowed to disclose it. The best thing for you to do is to file a new report describing the symptoms as your site is experiencing them. You can provide openafs-gatekeepers@openafs.org as a contact with the software vendor for the Microsoft support engineer to provide follow up. When a Microsoft support engineer initiates contact I can put them in touch with the developers that have been looking into the case. Jeffrey Altman --------------ms000808040002000707040505 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MjIyMTEyMzdaMCMGCSqGSIb3DQEJBDEWBBQ4eeBr 42Gta13XYYNC3InqWeD2/jBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAFSQFh5uUw8xkFxwf/EpvPtUD4UGMDAiOAgc ww/bGvc0mOOMTsavYTBEpFCiqZ3IP7YLX/d1pz7u70J1mxFA9MsCdK8e6WXzbKygsrjJCeWz 4STwekh6nYDLKx0kIn7UgG9CL1B75catSgryuGD0kLFW/6/ecwiiwNTahl9BqLW11Hu/z8sE WUdRTGi7WxDoUQypmwaAbHBuLQ8q/QVS4+BUd08Jt6tpWEfJdKSbuiwWa4bsCSrJi47LLlv5 wzhENRPq4KKPGoO0ku+h2Z2ixYVKBfSNQPXmVv59MHrqpfVzo55+grC0DdrLBAstCOG/81GJ Dhe5vO2SHtCMJ8BWDoUAAAAAAAA= --------------ms000808040002000707040505-- From jason@rampaginggeek.com Fri Apr 23 00:47:33 2010 From: jason@rampaginggeek.com (Jason Edgecombe) Date: Thu, 22 Apr 2010 19:47:33 -0400 Subject: [OpenAFS] pts -expandgroups vs -supergroups Message-ID: <4BD0E015.8050902@rampaginggeek.com> Hi, What is the difference between the new -expandgroups and -supergroups options to the pts mem command? That seem identical in my reading. Thanks, Jason From jason@rampaginggeek.com Fri Apr 23 03:05:43 2010 From: jason@rampaginggeek.com (Jason Edgecombe) Date: Thu, 22 Apr 2010 22:05:43 -0400 Subject: [OpenAFS] Recommended patches on top of 1.4.12? Message-ID: <4BD10077.4080401@rampaginggeek.com> Hi everyone, I'm going to compile 1.4.12 for my servers in a month. Are there any recommended patches that I should apply to 1.4.12 from the 1.4.x git branch? Thanks, Jason From rra@stanford.edu Fri Apr 23 03:09:39 2010 From: rra@stanford.edu (Russ Allbery) Date: Thu, 22 Apr 2010 19:09:39 -0700 Subject: [OpenAFS] Recommended patches on top of 1.4.12? In-Reply-To: <4BD10077.4080401@rampaginggeek.com> (Jason Edgecombe's message of "Thu, 22 Apr 2010 22:05:43 -0400") References: <4BD10077.4080401@rampaginggeek.com> Message-ID: <87wrvysyvw.fsf@windlord.stanford.edu> Jason Edgecombe writes: > I'm going to compile 1.4.12 for my servers in a month. Are there any > recommended patches that I should apply to 1.4.12 from the 1.4.x git > branch? I apply the following to the Debian builds: - [135e196b] Create missing root directory when ORPH_ATTACH - [190ef2cb] volmonitor keep vtrans lock - [812dcc2c] Increase the maximum number of sysnames - [a123d4ab] Print rxdebug statistics as unsigned values - [4ca7b6fc] Remove lih_r - [f3899ac3] Allow GetSomeSpace_r to select an optimal host - [94a43966] h_TossStuff_r: check held-ness after lock - [b78eeb0c] h_TossStuff_r: make sure host does not go away - [0583af32] volmonitor copy link before calling free - [eb799d07] Move non-executable stack assembly code to end of file Not all of these are particularly important, but they shouldn't hurt. -- Russ Allbery (rra@stanford.edu) From adeason@sinenomine.net Fri Apr 23 04:00:58 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Thu, 22 Apr 2010 22:00:58 -0500 Subject: [OpenAFS] Re: pts -expandgroups vs -supergroups References: <4BD0E015.8050902@rampaginggeek.com> Message-ID: <20100422220058.c0cce958.adeason@sinenomine.net> On Thu, 22 Apr 2010 19:47:33 -0400 Jason Edgecombe wrote: > Hi, > > What is the difference between the new -expandgroups and -supergroups > options to the pts mem command? That seem identical in my reading. -expandgroups just expands the listing of the normal pts output. So, if you have 'foo' is a member of 'bar' is a member of 'baz', 'pts mem baz' would just list 'bar'. Running 'pts mem baz -expandgroups' will list 'bar' and 'foo'. -supergroups lists the "parent" groups of a group. Normally if you run 'pts mem groupname' for a group, it lists the members of the group. 'pts mem groupname -supergroups' lists the groups that contain 'groupname'. The documentation could probably stand to have some examples. -- Andrew Deason adeason@sinenomine.net From jaltman@secure-endpoints.com Fri Apr 23 11:25:16 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Fri, 23 Apr 2010 11:25:16 +0100 Subject: [OpenAFS] Recommended patches on top of 1.4.12? In-Reply-To: <87wrvysyvw.fsf@windlord.stanford.edu> References: <4BD10077.4080401@rampaginggeek.com> <87wrvysyvw.fsf@windlord.stanford.edu> Message-ID: <4BD1758C.1050601@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms030602070604090602080507 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/23/2010 3:09 AM, Russ Allbery wrote: > Jason Edgecombe writes: >=20 >> I'm going to compile 1.4.12 for my servers in a month. Are there any >> recommended patches that I should apply to 1.4.12 from the 1.4.x git >> branch? >=20 > I apply the following to the Debian builds: >=20 > - [135e196b] Create missing root directory when ORPH_ATTACH > - [190ef2cb] volmonitor keep vtrans lock > - [812dcc2c] Increase the maximum number of sysnames > - [a123d4ab] Print rxdebug statistics as unsigned values > - [4ca7b6fc] Remove lih_r > - [f3899ac3] Allow GetSomeSpace_r to select an optimal host > - [94a43966] h_TossStuff_r: check held-ness after lock > - [b78eeb0c] h_TossStuff_r: make sure host does not go away > - [0583af32] volmonitor copy link before calling free > - [eb799d07] Move non-executable stack assembly code to end of file= >=20 > Not all of these are particularly important, but they shouldn't hurt. >=20 There are a number of rx patches on master that should be applied to 1.4. There may be others as well. Being on vacation I'm not going to perform a comprehensive search at the moment. Jeffrey Altman --------------ms030602070604090602080507 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MjMxMDI1MTZaMCMGCSqGSIb3DQEJBDEWBBSPr84u L/AVjQsTLgIo+5ytMapG9jBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAKi4z00ko9vY8+5m63+ywyO4MijAUJlupy5Z goNzIlyuK9USkdc0EGuIqH7A6zNwxxcI0jAxxx/l9MLu2bhm3zmph77hiZcEi4l78NvbxT21 3ARE7rK9TLzaqQfUoITtyF2Mnpf3Q3M1a4ao7gNR96YJb2BZ9KRGIwpwr/W5whYcRIubGaIQ l7o6Mur6atcul1Jqu8yCPuhVMt0P1HbUgl5jsm4UI2xrxAPdSNuyZzdqzfaZyhbemRG2Q0fU mDV1MUXfHLpKT982+V+TRIgVTXZIn273OoH3xT+o3Yy1S2Gxv6qPsOCa6PsYQE1b30fgg1UY RzgfCs+Rystkl6zdZWYAAAAAAAA= --------------ms030602070604090602080507-- From shadow@dementia.org Fri Apr 23 13:19:33 2010 From: shadow@dementia.org (Derrick J Brashear) Date: Fri, 23 Apr 2010 08:19:33 -0400 (EDT) Subject: [OpenAFS] Book your room for the ABPW10 today! Message-ID: Today's the last day to reserve a room as part of our block for this year's AFS & Kerberos Best Practices workshop! Hotel info here: http://workshop.openafs.org/afsbpw10/hotel.html Rate is $119/night at the I Hotel and Conference Center. Thank you, Derrick for the AFS & Kerberos Best Practices Workshop Organizers http://workshop.openafs.org/ From Dan Hyde Fri Apr 23 14:16:29 2010 From: Dan Hyde (Dan Hyde) Date: Fri, 23 Apr 2010 09:16:29 -0400 Subject: [OpenAFS] Recommended patches on top of 1.4.12? In-Reply-To: Your message of Fri, 23 Apr 2010 11:25:16 +0100. <4BD1758C.1050601@secure-endpoints.com> Message-ID: <1677.1272028589@block.ifs.umich.edu> > On 4/23/2010 3:09 AM, Russ Allbery wrote: > > Jason Edgecombe writes: > > > >> I'm going to compile 1.4.12 for my servers in a month. Are there any > >> recommended patches that I should apply to 1.4.12 from the 1.4.x git > >> branch? > > > > I apply the following to the Debian builds: > > > > - [135e196b] Create missing root directory when ORPH_ATTACH > > - [190ef2cb] volmonitor keep vtrans lock > > - [812dcc2c] Increase the maximum number of sysnames > > - [a123d4ab] Print rxdebug statistics as unsigned values > > - [4ca7b6fc] Remove lih_r > > - [f3899ac3] Allow GetSomeSpace_r to select an optimal host > > - [94a43966] h_TossStuff_r: check held-ness after lock > > - [b78eeb0c] h_TossStuff_r: make sure host does not go away > > - [0583af32] volmonitor copy link before calling free > > - [eb799d07] Move non-executable stack assembly code to end of file= > > > Not all of these are particularly important, but they shouldn't hurt. > > There are a number of rx patches on master that should be applied to > 1.4. There may be others as well. And parts of ca613599a2537756462a420ae1a632747a433226 are in the works getting ported to 1.4.x, and may be needed to help with the hostList / HTFree / hostAddrHashTable corruption we're seeing. Expect to see that posted between now and Monday. From holger.rauch@empic.de Sat Apr 24 19:00:05 2010 From: holger.rauch@empic.de (Holger Rauch) Date: Sat, 24 Apr 2010 20:00:05 +0200 Subject: [OpenAFS] Possible explanation(s) for obvious performance problems? Message-ID: <20100424180005.GA5946@heitec.de> --huq684BweRXVnRxX Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I'm running OpenAFS 1.4.11 (from lenny backports) on a Debian Lenny AMD64 system (QNAP TS 809 Turbo equipped with eightSeagate 7.2k Enterprise HDs, capacity: 1 TB each) which is a central file server (NAS), i. e. that server runs the - bosserver - ptserver - buserver - vlserver - volserver daemons simultaneously. (My primary reasons for choosing OpenAFS over Samba for SMB/CIFS, NFS v3/4, etc. was the user/rights/ACL management which doesn't require maintaining two separate user databases (as is the case with Samba) and the fact that OpenAFS volumes can easily be moved to a different host (provided storage space on that host is available). I'm experiencing *severe* performance problems when doing a dd inside an OpenAFS volume compared to a "plain" ext3 volume (both residing on separate logical volumes). Below is the dd output when dd is run inside a native ext3 volume. =3D=3D=3D dd if=3D/dev/zero of=3Dtestfile bs=3D1M count=3D256 256+0 records in 256+0 records out 268435456 bytes (268 MB) copied, 1,10903 s, 242 MB/s =20 =3D=3D=3D Inside an OpenAFS file system, the output looks as follows: =3D=3D=3D =20 dd if=3D/dev/zero of=3Dtestfile bs=3D1M count=3D256 256+0 records in 256+0 records out 268435456 bytes (268 MB) copied, 15,4072 s, 17,4 MB/s =3D=3D=3D (Both dd commands were run directly on the file server host in order to rule out possible network latency problems as a cause for the bad performance). Any ideas as to where that bad performance might come from? (I do have encryption enabled, but since it's only plain DES encryption on current machines that most likely can't be an explanation for the performance problem). In addition, it's also sort of interesting to see that on Windows 7 machines the loopback adapter for OpenAFS is only set to 10 MBit, even though the machine is phyiscally equipped with a gigbat capable NIC and the phyiscal connection is set to 1 GBit. I noticed that after having installed OpenAFS 1.5.72 on several Windows 7 systems. I get transfer rates of about 8 - 10 MBytes/sec in a gigabit network from the Windows 7 clients to the central file server. Sort of strange. How can the speed of the loopback adapter be increased? Thanks in advance for any hints & kind regards, Holger =20 --huq684BweRXVnRxX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvTMaUACgkQbiVtWpZdKQL0DACbBuYrTAD3bJIp0rIsy8oQp88l h/sAnRt/TDzvCN78G6ZK/Y0BruWEEkfj =/DEZ -----END PGP SIGNATURE----- --huq684BweRXVnRxX-- From carson@taltos.org Sat Apr 24 19:04:08 2010 From: carson@taltos.org (Carson Gaspar) Date: Sat, 24 Apr 2010 13:04:08 -0500 Subject: [OpenAFS] Re: [OpenAFS-announce] OpenAFS on Red Had Enterprise Linux 6 In-Reply-To: References: Message-ID: <4BD33298.5010803@taltos.org> Marc Dionne wrote: > Red Hat has recently announced the availability of a beta version of > its next Red Hat Enterprise Linux release (RHEL6). While OpenAFS is > functional with this release, it generates a large volume of messages > in the system log when used with a disk cache. ... > If you have a support contract with Red Hat and care about running > OpenAFS with RHEL 6, we encourage you to open a case through your > support channel and inquire about getting these changes backported to > RHEL 6. They have already committed to fix it, FYI. Or they had as of a month or 2 ago. -- Carson From sxw@inf.ed.ac.uk Sat Apr 24 20:04:24 2010 From: sxw@inf.ed.ac.uk (Simon Wilkinson) Date: Sat, 24 Apr 2010 20:04:24 +0100 Subject: [OpenAFS] Re: [OpenAFS-announce] OpenAFS on Red Had Enterprise Linux 6 In-Reply-To: <4BD33298.5010803@taltos.org> References: <4BD33298.5010803@taltos.org> Message-ID: <72D40EAA-EA75-4BAE-9477-2C12AB2C6845@inf.ed.ac.uk> On 24 Apr 2010, at 19:04, Carson Gaspar wrote: >=20 > They have already committed to fix it, FYI. Or they had as of a month = or 2 ago. Currently, my knowledge is based on Red Hat's response to bugzilla bug = #585286, which states: "I will be proposing that patch for inclusion in = RHEL6 although it's final determination is not yet known." If Product Management have accepted that the patch is required, then so = much the better, but they have yet to say so publicly. Cheers, Simon. From sxw@inf.ed.ac.uk Sat Apr 24 20:20:37 2010 From: sxw@inf.ed.ac.uk (Simon Wilkinson) Date: Sat, 24 Apr 2010 20:20:37 +0100 Subject: [OpenAFS] Possible explanation(s) for obvious performance problems? In-Reply-To: <20100424180005.GA5946@heitec.de> References: <20100424180005.GA5946@heitec.de> Message-ID: <45951DA4-E0BD-46AC-9DAC-EFBD688CC7E4@inf.ed.ac.uk> On 24 Apr 2010, at 19:00, Holger Rauch wrote: >=20 > (Both dd commands were run directly on the file server host in order > to rule out possible network latency problems as a cause for the bad > performance). So, it's very important to realise that this is a terrible comparison. = Whilst both filesystems ultimately result in the data hitting an ext3 = filesystem, OpenAFS is doing significantly more work. With the ext3 case, the dd calls the write() syscall, the data gets = copied from user into kernel space, the kernel marks the page as dirty, = and at a moment of its choosing flushes that page to disk. Job done. With OpenAFS, dd calls write(), and the data gets copied into the = kernel. The OpenAFS kernel module then copies the page to the local disk = cache (by calling ext3's write), and returns control to the user. When = dd completes it calls close. The kernel module then loads the data back = from the disk cache (by calling ext3's read, if the data has been paged = out), and converts it into a set of arguments to an RPC call. It figures = out where to deliver that RPC to, possibly by making network calls to = the vlserver. The RPC is then checksummed, encrypted, split up into = appropriately addressed UDP packets and passed to the kernel's = networking stack. The networking drivers then route the packets = (hopefully round the loopback interface, but that does depend) and = deliver them to the fileserver. This runs in userspace, so the data gets = copied out of the kernel into the fileserver's buffers. The file server = then decrypts the data, decodes the RPC arguments to get the data being = written, works out which file it corresponds to, and whether it needs to = notify anyone that that file has changed. It then calls ext3's write() = syscall which copies the data from user into kernel space, the kernel = marks that page as dirty, and eventually flushes it to disk. Finally, = we're done. With a level playing field, a directly connected local disk is always be = faster than a network filesystem - there's simply less work to be done = when throwing data straight onto a local disk than there is when you = send it across the network.=20 > Any ideas as to where that bad performance might come from? (I do have > encryption enabled, but since it's only plain DES encryption on > current machines that most likely can't be an explanation for the > performance problem). The encryption isn't DES, it's fcrypt. And encryption does have a = significant effect on performance (not only doing the encryption itself, = but also the number of additional copies that it adds in to the data = path) It's worth taking a look at the configuration of your fileserver. = There's been a lot written here in the past about the ideal settings for = the fileserver - I'll leave you to Google over the list, but it's just = worth noting that the out of the box configuration is not likely to = result in good performance. As a datapoint, using your test across a network, my homedirectory is = seeing write speeds of 70 MB/s from an OpenAFS 1.4.11 client. We're = currently running our fileservers with "-L -p 128 -rxpck 400 -busyat 600 = -s 1200 -l 1200 -cb 100000 -b 240 -vc 1200" All that said, we are trying to improve the performance of OpenAFS. = There are numerous changes in the 1.5 tree, particularly for Linux, that = help speed it up. I'd also encourage you to look at more meaningful = benchmarks - in particular those which mirror the kind of use you'll = actually be putting the filesystem to. Cheers, Simon. From adam@megacz.com Sat Apr 24 21:23:39 2010 From: adam@megacz.com (Adam Megacz) Date: Sat, 24 Apr 2010 20:23:39 +0000 Subject: [OpenAFS] Re: experience of SQLite on AFS References: Message-ID: Ken Dreyer writes: > SQLite has an option in os_unix.c (SQLITE_ENABLE_LOCKING_STYLE) to > automatically figure out the database's filesystem type and use the > most appropriate locking mechanism for that filesystem. Adam Megacz > wrote a patch to SQLite back in 2006 that added AFS to this list of > filesystems SQLite could detect. I'm not certain, but I think this > only works for OSX (Adam, correct me if I'm wrong :-) IIRC that is correct. Also, DRHipp never merged the patch (even though I sent him the legal papers he asked for). > Additionally, SQLite also has the (undocumented?) ability to define a > fixed locking style at compile-time with SQLITE_FIXED_LOCKING_STYLE. I must hasten to add that I have never been able to get sqlite working in a scenario where multiple client machines are concurrently accessing the same database -- even when "whole file locking" is in use. I originally thought that using whole-file locks only (and no byte-range locks) would work, but as far as I have been able to determine, it *does not*. > We hope we can make use of byte-range locking some day when OpenAFS > supports this on *nix. Me too, but my hopes are not high. The fact that the databases become corrupted when using whole-file locks only suggests that there is a more subtle problem lurking here. - a From rich@nd.edu Sat Apr 24 21:39:39 2010 From: rich@nd.edu (Rich Sudlow) Date: Sat, 24 Apr 2010 16:39:39 -0400 Subject: [OpenAFS] Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? In-Reply-To: <20100326182248.GA15657@heitec.de> References: <20100326182248.GA15657@heitec.de> Message-ID: On Mar 26, 2010, at 2:22 PM, Holger Rauch wrote: > Hi everybody, > > I installed OpenAFS for Windows 1.572 on a Windows 7 Professional (64 > bit) system with all system updates applied in conjunction with > Kerberos for Windows (KfW) and the Network Identity Manager. I > downloaded all packages from Secure Endpoints' web site. The PC is > consists of current HW (Intel Core2Duo, 4 to 8 GB RAM, etc.). > > Unfortunately, the maximum transfer speed on Windows is about 8-10 > MB/sec when I copy local files to an OpenAFS volume. All involved > network components are gigabit capable and I don't experience this > problem when doing file transfers to a native ext3 filesystem using > scp, for example. (I consider this comparable since the transfers are > encrypted as well, in case of SSH/SCP even with a much stronger > encryption algorithm). > > The server is a Debian Lenny system running OpenAFS 1.4.11 obtained > from the Debian backports repository. The system is a QNAP TS-809 Pro > with an external HD for the OS. The QNAP HDs are Seagate 7200k RPM > drives of the Enterprise series used with SW RAID 5, totalling 6,4 TB > in capacity. OpenAFS volumes reside on /vicep partitions which in turn > reside on Logical Volumes (LVs). (We're only 25 users, so this scheme > works perfectly well and has the advantage that the size of the > underlying LV implicitly determines the quota, so I don't have to > worry about setting OpenAFS quotas). > > The questions are thus: > > - Can I change the speed of the loopback adapter on Windows 7? If > so, how? > > - Why does the loopback adapter's speed default to 10 Mb instead of > the speed of the physical interface (Gb) at all? > > - What's a "normal" transfer speed for OpenAFS when run in gigabit > network environemnts? In our cell we typically see write speeds of 60 - 85 MB sec on gigabit clients (with no client tuning). You mentioned that your network connections are Gb capable - but are they set to Gb?? Your speeds are typical of a client with 100 Mb network connections. Rich > > (In case I forgot to mention something, please don't hesitate to ask). > > Thanks in advance! > > Kind regards & have a nice weekend, > > Holger From rich@nd.edu Sat Apr 24 21:51:11 2010 From: rich@nd.edu (Rich Sudlow) Date: Sat, 24 Apr 2010 16:51:11 -0400 Subject: [OpenAFS] Possible explanation(s) for obvious performance problems? In-Reply-To: <45951DA4-E0BD-46AC-9DAC-EFBD688CC7E4@inf.ed.ac.uk> References: <20100424180005.GA5946@heitec.de> <45951DA4-E0BD-46AC-9DAC-EFBD688CC7E4@inf.ed.ac.uk> Message-ID: <404D6EAA-07DF-4AB3-B1FE-5A6793DCA4FF@nd.edu> On Apr 24, 2010, at 3:20 PM, Simon Wilkinson wrote: > > On 24 Apr 2010, at 19:00, Holger Rauch wrote: >> >> (Both dd commands were run directly on the file server host in order >> to rule out possible network latency problems as a cause for the bad >> performance). > > So, it's very important to realise that this is a terrible > comparison. Whilst both filesystems ultimately result in the data > hitting an ext3 filesystem, OpenAFS is doing significantly more work. > > With the ext3 case, the dd calls the write() syscall, the data gets > copied from user into kernel space, the kernel marks the page as > dirty, and at a moment of its choosing flushes that page to disk. > Job done. > > With OpenAFS, dd calls write(), and the data gets copied into the > kernel. The OpenAFS kernel module then copies the page to the local > disk cache (by calling ext3's write), and returns control to the > user. When dd completes it calls close. The kernel module then loads > the data back from the disk cache (by calling ext3's read, if the > data has been paged out), and converts it into a set of arguments to > an RPC call. It figures out where to deliver that RPC to, possibly > by making network calls to the vlserver. The RPC is then > checksummed, encrypted, split up into appropriately addressed UDP > packets and passed to the kernel's networking stack. The networking > drivers then route the packets (hopefully round the loopback > interface, but that does depend) and deliver them to the fileserver. > This runs in userspace, so the data gets copied out of the kernel > into the fileserver's buffers. The file server then decrypts the > data, decodes the RPC arguments to get the data being written, works > out which file it corresponds to, and whether it needs to notify > anyone that that file has changed. It then calls ext3's write() > syscall which copies the data from user into kernel space, the > kernel marks that page as dirty, and eventually flushes it to disk. > Finally, we're done. > > With a level playing field, a directly connected local disk is > always be faster than a network filesystem - there's simply less > work to be done when throwing data straight onto a local disk than > there is when you send it across the network. > >> Any ideas as to where that bad performance might come from? (I do >> have >> encryption enabled, but since it's only plain DES encryption on >> current machines that most likely can't be an explanation for the >> performance problem). > > The encryption isn't DES, it's fcrypt. And encryption does have a > significant effect on performance (not only doing the encryption > itself, but also the number of additional copies that it adds in to > the data path) > > It's worth taking a look at the configuration of your fileserver. > There's been a lot written here in the past about the ideal settings > for the fileserver - I'll leave you to Google over the list, but > it's just worth noting that the out of the box configuration is not > likely to result in good performance. > > As a datapoint, using your test across a network, my homedirectory > is seeing write speeds of 70 MB/s from an OpenAFS 1.4.11 client. > We're currently running our fileservers with "-L -p 128 -rxpck 400 - > busyat 600 -s 1200 -l 1200 -cb 100000 -b 240 -vc 1200" As another data point on our fileservers we use -p 128 -b 480 -l 2400 -s 2400 -vc 2400 -cb 64000 -rxpck 800 -udpsize 1048576 -busyat 1200 -hr 1 -vattachpar 4 -implicit all -nojumbo But I think it's your client (or server) set to 100 Mb. Rich > > All that said, we are trying to improve the performance of OpenAFS. > There are numerous changes in the 1.5 tree, particularly for Linux, > that help speed it up. I'd also encourage you to look at more > meaningful benchmarks - in particular those which mirror the kind of > use you'll actually be putting the filesystem to. > > Cheers, > > Simon. > > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info From adeason@sinenomine.net Sat Apr 24 22:01:24 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Sat, 24 Apr 2010 16:01:24 -0500 Subject: [OpenAFS] Re: Possible explanation(s) for obvious performance problems? References: <20100424180005.GA5946@heitec.de> Message-ID: <20100424160124.fc2a4415.adeason@sinenomine.net> On Sat, 24 Apr 2010 20:00:05 +0200 Holger Rauch wrote: > Any ideas as to where that bad performance might come from? (I do have > encryption enabled, but since it's only plain DES encryption on > current machines that most likely can't be an explanation for the > performance problem). Well, there's one way to find out for sure... Simon covered server tweaking in general, but for throughput on a server that's not particularly loaded, my first guess might be -rxpck specifically. I recall some people have reported significant throughput improvement when it's raised to even 2000 or higher. To see if it's the client or the server that's the bottleneck, you could try a throughput test with afsio or afscp. If that yields a much faster result, you're likely hitting bottlenecks in the cache manager code. It could also be slower, though, if you've tweaked afsd's rx settings, as I don't think afsio or afscp allow you to tune those. (afsio is in src/venus, afscp is src/tests) -- Andrew Deason adeason@sinenomine.net From l.schimmer@cgv.tugraz.at Sun Apr 25 10:39:00 2010 From: l.schimmer@cgv.tugraz.at (Lars Schimmer) Date: Sun, 25 Apr 2010 11:39:00 +0200 Subject: [OpenAFS] Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? In-Reply-To: References: <20100326182248.GA15657@heitec.de> Message-ID: <4BD40DB4.9040703@cgv.tugraz.at> On 24.04.2010 22:39, Rich Sudlow wrote: > You mentioned that your network connections are Gb capable - but are th= ey > set to Gb?? Your speeds are typical of a client with 100 Mb network > connections. Usual auto negotiation does its job quite good. But OpenAFS enables encryption of data transfer on each standard install - which results in drastic performance decreases. E.g. my workstation client (linux) does 10-12 MB/sec with encryption enabled, but >70 MB/sec with encryption disabled. My point is on: disable encryption. Btw, our linux clients does roughly 20-50 MB/sec so far. Still need to test memcache. > Rich >=20 >> >> (In case I forgot to mention something, please don't hesitate to ask). >> >> Thanks in advance! >> >> Kind regards & have a nice weekend, >> >> Holger MfG, Lars Schimmer --=20 ------------------------------------------------------------- TU Graz, Institut f=FCr ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer@cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 From jason@rampaginggeek.com Fri Apr 23 18:00:46 2010 From: jason@rampaginggeek.com (Jason Edgecombe) Date: Fri, 23 Apr 2010 13:00:46 -0400 Subject: [OpenAFS] Re: pts -expandgroups vs -supergroups In-Reply-To: <20100422220058.c0cce958.adeason@sinenomine.net> References: <4BD0E015.8050902@rampaginggeek.com> <20100422220058.c0cce958.adeason@sinenomine.net> Message-ID: <4BD1D23E.9050802@rampaginggeek.com> Andrew Deason wrote: > On Thu, 22 Apr 2010 19:47:33 -0400 > Jason Edgecombe wrote: > > >> Hi, >> >> What is the difference between the new -expandgroups and -supergroups >> options to the pts mem command? That seem identical in my reading. >> > > -expandgroups just expands the listing of the normal pts output. So, if > you have 'foo' is a member of 'bar' is a member of 'baz', 'pts mem baz' > would just list 'bar'. Running 'pts mem baz -expandgroups' will list > 'bar' and 'foo'. > > -supergroups lists the "parent" groups of a group. Normally if you run > 'pts mem groupname' for a group, it lists the members of the group. > 'pts mem groupname -supergroups' lists the groups that contain > 'groupname'. > > The documentation could probably stand to have some examples. > > ok, so -supergroups expands parents and -expandgroups expands children? If that's the case, -supergroups would make more sense as "-parentgroups" Is it too late to rename that option? Jason From holger.rauch@empic.de Sun Apr 25 15:14:44 2010 From: holger.rauch@empic.de (Holger Rauch) Date: Sun, 25 Apr 2010 16:14:44 +0200 Subject: [OpenAFS] Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? In-Reply-To: References: <20100326182248.GA15657@heitec.de> Message-ID: <20100425141444.GA305@heitec.de> --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Rich, first of all, thanks a lot for your reply. On Sat, 24 Apr 2010, Rich Sudlow wrote: > [...]=20 > In our cell we typically see write speeds of 60 - 85 MB sec on > gigabit clients (with no client tuning). For Windows or Linux clients, or both? Besides, have you (or anybody else subscribed to this list) any recommendations for tuning on the server side? >=20 > You mentioned that your network connections are Gb capable - but are > they > set to Gb??=20 Yes, the phyiscal interface is set to GB, I notice this when I do an SCP transfer (also encrypted, even stronger than plain old DES) to a native ext3 fs where I get exactly the speeds you mentioned. So, I suppose it's likely to be something else, i. e. not the setting of the physical interface. >Your speeds are typical of a client with 100 Mb network > connections. Yes, I know. But the settings are clearly GB on both sides (client and sever). Thanks in advance and kind regards, Holger =20 --W/nzBZO5zC0uMSeA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvUTlQACgkQbiVtWpZdKQKXogCdEgzNJwN31hclBhvqJuJWHMUk 8S8An18tpz8wNcZX+YTFaB7dgNu5Le9R =XQo6 -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA-- From holger.rauch@empic.de Sun Apr 25 15:19:51 2010 From: holger.rauch@empic.de (Holger Rauch) Date: Sun, 25 Apr 2010 16:19:51 +0200 Subject: [OpenAFS] Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? In-Reply-To: <4BD40DB4.9040703@cgv.tugraz.at> References: <20100326182248.GA15657@heitec.de><4BD40DB4.9040703@cgv.tugraz.at> Message-ID: <20100425141951.GB305@heitec.de> --MfFXiAuoTsnnDAfZ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Lars, thanks for your reply. Lars Schimmer schrieb am Sunday, den 25. April 2010: > Usual auto negotiation does its job quite good. > But OpenAFS enables encryption of data transfer on each standard install > - which results in drastic performance decreases. Thanks for mentioning this and that's exactly what I'm wondering about. Encryption too is involved when doing SCP transfers (even stronger encryption, such as Blowfish or AES 256) and I get scp speeds of 60 to 82 MB/sec when transferring to native ext3 fs. So, my question is: Why is there almost no decrease when using SCP with a strong encryption algorithm (compared to plain DES that AFS uses) but there is *drastic* decrease in performance with only plain DES enabled compared to an unencrypted transfer? > E.g. my workstation client (linux) does 10-12 MB/sec with encryption > enabled, but >70 MB/sec with encryption disabled. > My point is on: disable encryption. > Btw, our linux clients does roughly 20-50 MB/sec so far. Still need to > test memcache. Any good ideas as to how to test memcache? Thanks in advance & kind regards, Holger =20 --MfFXiAuoTsnnDAfZ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvUT4cACgkQbiVtWpZdKQJIGgCfbOnSZxg5g02zyZwPwocVcE0n sjcAnRCLzyWzB1DV74qWsS35C1zEOtYq =+rDE -----END PGP SIGNATURE----- --MfFXiAuoTsnnDAfZ-- From adeason@sinenomine.net Sun Apr 25 18:45:07 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Sun, 25 Apr 2010 12:45:07 -0500 Subject: [OpenAFS] Re: pts -expandgroups vs -supergroups In-Reply-To: <4BD1D23E.9050802@rampaginggeek.com> References: <4BD0E015.8050902@rampaginggeek.com> <20100422220058.c0cce958.adeason@sinenomine.net> <4BD1D23E.9050802@rampaginggeek.com> Message-ID: <20100425124507.49400619.adeason@sinenomine.net> On Fri, 23 Apr 2010 13:00:46 -0400 Jason Edgecombe wrote: > ok, so -supergroups expands parents and -expandgroups expands > children? No. -expandgroups expands whatever we're displaying (I think). If you are displaying the children of a group, -expandgroups will expand all of the children. If you are displaying what groups an entry is in, -expandgroups will expand all of the supergroups. -supergroups displays the containing groups of a group instead of the group membership. That is, currently if you pass 'pts mem' a group, it will display the members of that group; if you give it a user, it will display the groups that user is in. Before -supergroups, there was no way to display what groups a group was in. Let me try an example to explain all of them. Say we have a group group1, which contains group2, which contains user3. 'pts mem group1' will display "group2". 'pts mem group1 -expandgroups' will display "group2, user3" 'pts mem group2 -supergroups' will display "g1". 'pts mem user3' will display "group2" 'pts mem user3 -expandgroups' will display "group2, group1" > If that's the case, -supergroups would make more sense as > "-parentgroups" > > Is it too late to rename that option? I thought that the term 'supergroup' has always referred to a group that contained another group (in AFS PTS). So, you're listing the group's supergroups... I don't know, it makes sense to me. We could just make a -parentgroups switch do the same thing as -supergroups, if there is demand. -- Andrew Deason adeason@sinenomine.net From l.schimmer@cgv.tugraz.at Sun Apr 25 20:52:05 2010 From: l.schimmer@cgv.tugraz.at (Lars Schimmer) Date: Sun, 25 Apr 2010 21:52:05 +0200 Subject: [OpenAFS] Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? In-Reply-To: <20100425141951.GB305@heitec.de> References: <20100326182248.GA15657@heitec.de><4BD40DB4.9040703@cgv.tugraz.at> <20100425141951.GB305@heitec.de> Message-ID: <4BD49D65.9070804@cgv.tugraz.at> On 25.04.2010 16:19, Holger Rauch wrote: > Hi Lars, >=20 > thanks for your reply. >=20 > Lars Schimmer schrieb am Sunday, den 25. April 2010: >=20 >> Usual auto negotiation does its job quite good. >> But OpenAFS enables encryption of data transfer on each standard insta= ll >> - which results in drastic performance decreases. >=20 > Thanks for mentioning this and that's exactly what I'm wondering > about. Encryption too is involved when doing SCP transfers (even > stronger encryption, such as Blowfish or AES 256) and I get scp speeds > of 60 to 82 MB/sec when transferring to native ext3 fs. >=20 > So, my question is: Why is there almost no decrease when using SCP > with a strong encryption algorithm (compared to plain DES that AFS > uses) but there is *drastic* decrease in performance with only plain > DES enabled compared to an unencrypted transfer? OpenAFS does not use DES. And those are complete different implementations, as already laid out by simon. Data is far often copied and shuffled around within OpenAFS than with scp/ftp/ssh. And the encryption implementation was not designed to be done perfect over gigabit - it was designed for 1-2 mbit lines. A new implementation of that encryption is currently worked on, guess it will be faster. Oh, btw, a lot of small files will still fail to reach higher speeds, as callbacks are done massive. A network filesystem has some more needs than a local one ;-) >> E.g. my workstation client (linux) does 10-12 MB/sec with encryption >> enabled, but >70 MB/sec with encryption disabled. >> My point is on: disable encryption. >> Btw, our linux clients does roughly 20-50 MB/sec so far. Still need to >> test memcache. >=20 > Any good ideas as to how to test memcache? Get a machine use memcache, deactivate encryption and test the transfer rates? Or get a machine with those nice SSD and set the cache with ~10-30 GB on those fast SSD. Should increase bandwidth, to. I just need to set that client up. Although current rates are quite fine, still got most machines on 100MBit switches and those lines are saturated with OpenAFS. > Thanks in advance & kind regards, >=20 >=20 > Holger > =20 MfG, Lars Schimmer --=20 ------------------------------------------------------------- TU Graz, Institut f=FCr ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer@cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 From jason@rampaginggeek.com Sun Apr 25 21:07:41 2010 From: jason@rampaginggeek.com (Jason Edgecombe) Date: Sun, 25 Apr 2010 16:07:41 -0400 Subject: [OpenAFS] Re: pts -expandgroups vs -supergroups In-Reply-To: <20100425124507.49400619.adeason@sinenomine.net> References: <4BD0E015.8050902@rampaginggeek.com> <20100422220058.c0cce958.adeason@sinenomine.net> <4BD1D23E.9050802@rampaginggeek.com> <20100425124507.49400619.adeason@sinenomine.net> Message-ID: <4BD4A10D.5060105@rampaginggeek.com> Andrew Deason wrote: > On Fri, 23 Apr 2010 13:00:46 -0400 > Jason Edgecombe wrote: > > >> ok, so -supergroups expands parents and -expandgroups expands >> children? >> > > No. -expandgroups expands whatever we're displaying (I think). If you > are displaying the children of a group, -expandgroups will expand all of > the children. If you are displaying what groups an entry is in, > -expandgroups will expand all of the supergroups. > > -supergroups displays the containing groups of a group instead of the > group membership. That is, currently if you pass 'pts mem' a group, it > will display the members of that group; if you give it a user, it will > display the groups that user is in. Before -supergroups, there was no > way to display what groups a group was in. > > Let me try an example to explain all of them. Say we have a group > group1, which contains group2, which contains user3. > > 'pts mem group1' will display "group2". > > 'pts mem group1 -expandgroups' will display "group2, user3" > > 'pts mem group2 -supergroups' will display "g1". > > 'pts mem user3' will display "group2" > > 'pts mem user3 -expandgroups' will display "group2, group1" > > >> If that's the case, -supergroups would make more sense as >> "-parentgroups" >> >> Is it too late to rename that option? >> > > I thought that the term 'supergroup' has always referred to a group that > contained another group (in AFS PTS). So, you're listing the group's > supergroups... I don't know, it makes sense to me. We could just make a > -parentgroups switch do the same thing as -supergroups, if there is > demand. > Thanks for clarifying. Can I use that patch against the 1.4.x tree? Can I use the 1.5.x pts with that patch on a 1.4.x client with 1.4.x servers? Thanks, Jason From sxw@inf.ed.ac.uk Sun Apr 25 21:44:24 2010 From: sxw@inf.ed.ac.uk (Simon Wilkinson) Date: Sun, 25 Apr 2010 21:44:24 +0100 Subject: [OpenAFS] Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? In-Reply-To: <20100425141951.GB305@heitec.de> References: <20100326182248.GA15657@heitec.de><4BD40DB4.9040703@cgv.tugraz.at> <20100425141951.GB305@heitec.de> Message-ID: <351FB1FA-A78D-4E48-9B3B-15B82A9B2E8B@inf.ed.ac.uk> On 25 Apr 2010, at 15:19, Holger Rauch wrote: > So, my question is: Why is there almost no decrease when using SCP > with a strong encryption algorithm (compared to plain DES that AFS > uses) but there is *drastic* decrease in performance with only plain > DES enabled compared to an unencrypted transfer? Firstly, as I (and others) have mentioned, OpenAFS doesn't use DES, it = uses an encryption algorithm called fcrypt, which is a DES derivative. Secondly, your assumption that weaker encryption algorithms will be = faster to compute is sadly false. Typical DES implementations are = significantly slower than AES ones, for example - just compare the = output from OpenSSL's speed tool. Cheers, Simon. From shadow@gmail.com Sun Apr 25 23:05:57 2010 From: shadow@gmail.com (Derrick Brashear) Date: Sun, 25 Apr 2010 18:05:57 -0400 Subject: [OpenAFS] Re: pts -expandgroups vs -supergroups In-Reply-To: <20100425124507.49400619.adeason@sinenomine.net> References: <4BD0E015.8050902@rampaginggeek.com> <20100422220058.c0cce958.adeason@sinenomine.net> <4BD1D23E.9050802@rampaginggeek.com> <20100425124507.49400619.adeason@sinenomine.net> Message-ID: On Sun, Apr 25, 2010 at 1:45 PM, Andrew Deason wrote: > On Fri, 23 Apr 2010 13:00:46 -0400 > Jason Edgecombe wrote: > >> ok, so -supergroups expands parents and -expandgroups expands >> children? > > No. -expandgroups expands whatever we're displaying (I think). If you > are displaying the children of a group, -expandgroups will expand all of > the children. If you are displaying what groups an entry is in, > -expandgroups will expand all of the supergroups. > > -supergroups displays the containing groups of a group instead of the > group membership. That is, currently if you pass 'pts mem' a group, it > will display the members of that group; if you give it a user, it will > display the groups that user is in. Before -supergroups, there was no > way to display what groups a group was in. > > Let me try an example to explain all of them. Say we have a group > group1, which contains group2, which contains user3. > > 'pts mem group1' will display "group2". > > 'pts mem group1 -expandgroups' will display "group2, user3" > > 'pts mem group2 -supergroups' will display "g1". > > 'pts mem user3' will display "group2" > > 'pts mem user3 -expandgroups' will display "group2, group1" > >> If that's the case, -supergroups would make more sense as >> "-parentgroups" >> >> Is it too late to rename that option? > > I thought that the term 'supergroup' has always referred to a group that > contained another group (in AFS PTS). Unless you're moose, it has. > So, you're listing the group's > supergroups... I don't know, it makes sense to me. We could just make a > -parentgroups switch do the same thing as -supergroups, if there is > demand. This is the first time I've seen parentgroup used ever. From jason@rampaginggeek.com Sun Apr 25 23:16:29 2010 From: jason@rampaginggeek.com (Jason Edgecombe) Date: Sun, 25 Apr 2010 18:16:29 -0400 Subject: [OpenAFS] Re: pts -expandgroups vs -supergroups In-Reply-To: References: <4BD0E015.8050902@rampaginggeek.com> <20100422220058.c0cce958.adeason@sinenomine.net> <4BD1D23E.9050802@rampaginggeek.com> <20100425124507.49400619.adeason@sinenomine.net> Message-ID: <4BD4BF3D.9010800@rampaginggeek.com> Derrick Brashear wrote: > On Sun, Apr 25, 2010 at 1:45 PM, Andrew Deason wrote: > >> On Fri, 23 Apr 2010 13:00:46 -0400 >> Jason Edgecombe wrote: >> >> >>> ok, so -supergroups expands parents and -expandgroups expands >>> children? >>> >> No. -expandgroups expands whatever we're displaying (I think). If you >> are displaying the children of a group, -expandgroups will expand all of >> the children. If you are displaying what groups an entry is in, >> -expandgroups will expand all of the supergroups. >> >> -supergroups displays the containing groups of a group instead of the >> group membership. That is, currently if you pass 'pts mem' a group, it >> will display the members of that group; if you give it a user, it will >> display the groups that user is in. Before -supergroups, there was no >> way to display what groups a group was in. >> >> Let me try an example to explain all of them. Say we have a group >> group1, which contains group2, which contains user3. >> >> 'pts mem group1' will display "group2". >> >> 'pts mem group1 -expandgroups' will display "group2, user3" >> >> 'pts mem group2 -supergroups' will display "g1". >> >> 'pts mem user3' will display "group2" >> >> 'pts mem user3 -expandgroups' will display "group2, group1" >> >> >>> If that's the case, -supergroups would make more sense as >>> "-parentgroups" >>> >>> Is it too late to rename that option? >>> >> I thought that the term 'supergroup' has always referred to a group that >> contained another group (in AFS PTS). >> > > Unless you're moose, it has. > > >> So, you're listing the group's >> supergroups... I don't know, it makes sense to me. We could just make a >> -parentgroups switch do the same thing as -supergroups, if there is >> demand. >> > > This is the first time I've seen parentgroup used ever. -parentgroup is my own invention. supergroup is the proper AFS term. When I first red about the -supergroup option, it wasn't clear what it did and the option wasn't a good mnemonic. That's why I suggested the option be named -parentgroup. Jason From adeason@sinenomine.net Sun Apr 25 23:56:47 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Sun, 25 Apr 2010 17:56:47 -0500 Subject: [OpenAFS] Re: pts -expandgroups vs -supergroups In-Reply-To: <4BD4A10D.5060105@rampaginggeek.com> References: <4BD0E015.8050902@rampaginggeek.com> <20100422220058.c0cce958.adeason@sinenomine.net> <4BD1D23E.9050802@rampaginggeek.com> <20100425124507.49400619.adeason@sinenomine.net> <4BD4A10D.5060105@rampaginggeek.com> Message-ID: <20100425175647.698f49c7.adeason@sinenomine.net> On Sun, 25 Apr 2010 16:07:41 -0400 Jason Edgecombe wrote: > Can I use that patch against the 1.4.x tree? Probably; I don't imagine pts code is very different. If it's something that would be considered appropriate for 1.4, submit the cherry pick to gerrit. Or Mike or I could do it (or... anyone). > Can I use the 1.5.x pts with that patch on a 1.4.x client with 1.4.x > servers? Yes. -- Andrew Deason adeason@sinenomine.net From jaltman@secure-endpoints.com Mon Apr 26 02:19:24 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Sun, 25 Apr 2010 21:19:24 -0400 Subject: [OpenAFS] Re: experience of SQLite on AFS In-Reply-To: References: Message-ID: <4BD4EA1C.3070603@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms070505020706040208090604 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/24/2010 4:23 PM, Adam Megacz wrote: > Me too, but my hopes are not high. The fact that the databases become > corrupted when using whole-file locks only suggests that there is a mor= e > subtle problem lurking here. >=20 Actually it is a well understood problem. I just didn't realize that the unix cm had it. When a whole file lock is write-held, all of the dirty data in the cache must be written back to the file server before the lock is released. This is currently not being done and as a result, the database becomes corrupted. I suspect this will be fixed shortly. Jeffrey Altman --------------ms070505020706040208090604 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MjYwMTE5MjRaMCMGCSqGSIb3DQEJBDEWBBSb1tjY 7WrlV9hz8/7o8iugY7fJGDBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAF9LXOaZFW9O/91Z7rxMJ1xA8HXzTNoiLoBm pyii/0T9RwLV70HS9Ir0XWleGa1IrqR1VUJU4JJ8yItW7UcG074s3qncDW14Lb41GN9k1zh6 QpKd3gF8KqHA4ZxSu/e9wZEmE+RmCZ4FeZQV2yeoBe1JPvRt2UieF0AfTs4EuQjVU4j2vyYX C9By+YJR9F2wDSUsMp3ikwtIt8BBpq4OMft3kMuitx9IlV86Xl2j0i4scUgr2KAhFaRJhpzb 1hBCURQmArPTmXxFB/Vc3dwa4mzG5wasCI+fAYZUxS6cYlVqlFF4XdfyKKB0ESr+gyuKUDEn g+otKSxpOsZ1syXDcTcAAAAAAAA= --------------ms070505020706040208090604-- From jaltman@secure-endpoints.com Mon Apr 26 02:42:49 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Sun, 25 Apr 2010 21:42:49 -0400 Subject: [OpenAFS] Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? In-Reply-To: <20100326182248.GA15657@heitec.de> References: <20100326182248.GA15657@heitec.de> Message-ID: <4BD4EF99.6070901@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms030606090502050201000107 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 3/26/2010 2:22 PM, Holger Rauch wrote: > Hi everybody, >=20 > I installed OpenAFS for Windows 1.572 on a Windows 7 Professional (64 > bit) system with all system updates applied in conjunction with > Kerberos for Windows (KfW) and the Network Identity Manager. I > downloaded all packages from Secure Endpoints' web site. The PC is > consists of current HW (Intel Core2Duo, 4 to 8 GB RAM, etc.). 1.5.74 is the current release. > Unfortunately, the maximum transfer speed on Windows is about 8-10 > MB/sec when I copy local files to an OpenAFS volume.=20 This is common when encryption is in use, jumbo grams are disabled, and the file server is running with its defaults. > All involved > network components are gigabit capable and I don't experience this > problem when doing file transfers to a native ext3 filesystem using > scp, for example. (I consider this comparable since the transfers are > encrypted as well, in case of SSH/SCP even with a much stronger > encryption algorithm). The performance of a secure transfer protocol is very roughly comparable to the cost of the encryption algorithm itself (fcrypt, DES, RC4, AES, etc.), the encryption mode, and the number of encryption operations that must be performed (size of the chunks). For AFS without jumbograms the size of the data portion of a packet is under 1444 bytes per encryption operation. For something like SSH/SCP which is a tcp/ip stream protocol instead of packet based, the number of operations are significantly small= er. The AFS Rx fcrypt also does not lend itself particularly well to pipeline operations. Disabling encryption of the data will result in significant performance improvements and the cost of sending your data in the clear. > The server is a Debian Lenny system running OpenAFS 1.4.11 obtained > from the Debian backports repository. The system is a QNAP TS-809 Pro > with an external HD for the OS. The QNAP HDs are Seagate 7200k RPM > drives of the Enterprise series used with SW RAID 5, totalling 6,4 TB > in capacity. OpenAFS volumes reside on /vicep partitions which in turn > reside on Logical Volumes (LVs). (We're only 25 users, so this scheme > works perfectly well and has the advantage that the size of the > underlying LV implicitly determines the quota, so I don't have to > worry about setting OpenAFS quotas). >=20 > The questions are thus: >=20 > - Can I change the speed of the loopback adapter on Windows 7? If so, h= ow? The Microsoft loopback adapter has no speed (it is virtual and doesn't report one. When an adapter does not report a link speed it is reported as 10Mbit. This has no impact. > - Why does the loopback adapter's speed default to 10 Mb instead of > the speed of the physical interface (Gb) at all? The loopback adapter is not associated with the physical interface. All AFS Rx traffic to the file server is sent over the physical interfaces. The loopback adapter is used as a method of binding a Netbios name "AFS" that is visible only to the local machine. If the name was published on a physical adapter, there would be no mechanism for providing a common UNC name on all machines. > - What's a "normal" transfer speed for OpenAFS when run in gigabit > network environemnts? On 64-bit Win7, the SMB-to-AFS gateway is limited to approximately 65MB/second having nothing to do with the AFS Cache Manager to File Server interface speed. The AFS Redirector on 64-bit Win7 is currently producing sustained read performance from the cache manager of 380MB/sec. The AFS Redirector implementation is not publicly available as yet. When the 1.7 branch is ready for code submissions the AFS Redirector code base will be integrated and test releases will be made available. The maximum throughput of an Rx connection (without encryption) on a network that supports an MTU size of 9000 octets and clients and file servers configured to use jumbograms is somewhere between 260MB/sec and 280MB/sec. --- In reading the rest of the thread, there appears to be a mixture of reports describing Windows and Unix cache manager performance numbers. In this e-mail you are asking specifically about Windows. I'm not sure that the discussion of tuning Unix cache managers is of any value to you.= On Windows, there is one type of cache. It is a memory mapped paging fil= e. As others have mentioned, accessing lots of small files versus a small number of large files will also result is lower bandwidth numbers. This is especially true on Windows because properly implementation of file sharing operations requires that file locks be obtained for each and every file open. This overhead will not be present in SSH/SCP. Jeffrey Altman --------------ms030606090502050201000107 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MjYwMTQyNDlaMCMGCSqGSIb3DQEJBDEWBBTUnuh4 RT0GSwDm0yLLCmtTgf7mJDBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAFlg9sfI1JDrpSkp6LvS0VDiCbMXXmeY7It9 qpGOQ7FoUqk01hLWD/6s476aDqoRpx4COGBVbMTmWFhknoCwAFbnlmTY3rhVV+4Vdxus7vY/ 3s3/p2TRI7UG68TW+t4Jrj9ZOKDV4fFjr862vMKS/xN96qIluubrXfdnLFOYivwR8FRkjQYi DXJSpcrwYBYi9mZHXM6ZLFn+Wq0AghcU+nLFN6yCQu2GPHPE37B1OUzSOhBk23l6wAtROW8V /Jw6iZzZvoD5gE/H2hD77DIk4N70eVyV8nBrlRyZ6zpLIXwWXjlXm4i75wI1mWG+w0P0RTKY qK0R2cTD+BIlC0nXSHIAAAAAAAA= --------------ms030606090502050201000107-- From adeason@sinenomine.net Mon Apr 26 04:00:07 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Sun, 25 Apr 2010 22:00:07 -0500 Subject: [OpenAFS] Re: experience of SQLite on AFS References: <4BD4EA1C.3070603@secure-endpoints.com> Message-ID: <20100425220007.159058f3.adeason@sinenomine.net> On Sun, 25 Apr 2010 21:19:24 -0400 Jeffrey Altman wrote: > On 4/24/2010 4:23 PM, Adam Megacz wrote: > > > Me too, but my hopes are not high. The fact that the databases > > become corrupted when using whole-file locks only suggests that > > there is a more subtle problem lurking here. > > > > Actually it is a well understood problem. I just didn't realize that > the unix cm had it. > > When a whole file lock is write-held, all of the dirty data in the > cache must be written back to the file server before the lock is > released. This is currently not being done and as a result, the > database becomes corrupted. If I understand Simon correctly, clients are also not getting file updates while the file is opened O_RDWR. That would still seem to be a problem even if we flush on unlock. -- Andrew Deason adeason@sinenomine.net From allbery@ece.cmu.edu Mon Apr 26 04:18:37 2010 From: allbery@ece.cmu.edu (Brandon S. Allbery KF8NH) Date: Sun, 25 Apr 2010 23:18:37 -0400 Subject: [OpenAFS] Re: experience of SQLite on AFS In-Reply-To: <20100425220007.159058f3.adeason@sinenomine.net> References: <4BD4EA1C.3070603@secure-endpoints.com> <20100425220007.159058f3.adeason@sinenomine.net> Message-ID: <2E613888-2A59-4451-A1EF-FB2C006D741A@ece.cmu.edu> This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-43--260541656 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On Apr 25, 2010, at 23:00 , Andrew Deason wrote: > On Sun, 25 Apr 2010 21:19:24 -0400 > Jeffrey Altman wrote: >> When a whole file lock is write-held, all of the dirty data in the >> cache must be written back to the file server before the lock is >> released. This is currently not being done and as a result, the >> database becomes corrupted. > > If I understand Simon correctly, clients are also not getting file > updates while the file is opened O_RDWR. That would still seem to be a > problem even if we flush on unlock. Flushing will update the server, which will break callbacks as necessary. The default behavior is to only flush changes to the server on close, but there's no good reason to change that in the situation where there is no locking; the specced behavior remains "last closer wins". (I think fsync() updates the server in all cases, though.) -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH --Apple-Mail-43--260541656 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (Darwin) iEYEARECAAYFAkvVBhgACgkQIn7hlCsL25WbFwCfU0lpCHNeYbxiAwDGV8u/R0Uq sBsAoI3Os3KD0lbfz/AU19vFSw518dHJ =sUJc -----END PGP SIGNATURE----- --Apple-Mail-43--260541656-- From sxw@inf.ed.ac.uk Mon Apr 26 06:59:49 2010 From: sxw@inf.ed.ac.uk (Simon Wilkinson) Date: Mon, 26 Apr 2010 06:59:49 +0100 Subject: [OpenAFS] Re: experience of SQLite on AFS In-Reply-To: <2E613888-2A59-4451-A1EF-FB2C006D741A@ece.cmu.edu> References: <4BD4EA1C.3070603@secure-endpoints.com> <20100425220007.159058f3.adeason@sinenomine.net> <2E613888-2A59-4451-A1EF-FB2C006D741A@ece.cmu.edu> Message-ID: <65A74C8D-B0A4-4A6E-9591-5C15D2989A19@inf.ed.ac.uk> On 26 Apr 2010, at 04:18, Brandon S. Allbery KF8NH wrote: >>=20 >> If I understand Simon correctly, clients are also not getting file >> updates while the file is opened O_RDWR. That would still seem to be = a >> problem even if we flush on unlock. >=20 > Flushing will update the server, which will break callbacks as = necessary. No, this is still a problem. If a client believes that it has dirty = chunks, then it ignores callback breaks in favour of preserving the data = already in the cache. It would appear that, on Linux at least, simply = opening a file O_RDWR is enough to cause the cache manager to mark the = file as being dirty. In this situation, you'll never see updated data = from the server. Both this problem, and the lack of flushing, need to be = fixed. Cheers, Simon. From crestani@informatik.uni-tuebingen.de Mon Apr 26 08:13:07 2010 From: crestani@informatik.uni-tuebingen.de (Marcus Crestani) Date: Mon, 26 Apr 2010 09:13:07 +0200 Subject: [OpenAFS] Documentation for Preference Pane in 1.4.12 on MacOSX In-Reply-To: <4BCC09B3.80609@kezia.com> (Fabien COMBERNOUS's message of "Mon, 19 Apr 2010 09:43:47 +0200") References: <4BCC09B3.80609@kezia.com> Message-ID: >>>>>"FC" == Fabien COMBERNOUS writes: FC> To answer to many of our questions, you can use fseventer tool [1]. It FC> is a useful free closed source software to know the files modified FC> and/or created by a GUI on MacOSX. I planed to do it by myself, but i FC> didn't yet have enough time. Thanks for the pointer to fseventer, this is indeed a great tool for this and many other situations. But other than that, I cannot believe that there seems to be no documentation for the new Preference Pane. Anyone? -- Marcus From holger.rauch@empic.de Mon Apr 26 08:32:44 2010 From: holger.rauch@empic.de (Holger Rauch) Date: Mon, 26 Apr 2010 09:32:44 +0200 Subject: [OpenAFS] Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? In-Reply-To: <4BD4EF99.6070901@secure-endpoints.com> References: <20100326182248.GA15657@heitec.de><4BD4EF99.6070901@secure-endpoints.com> Message-ID: <20100426073244.GA21381@heitec.de> --a8Wt8u1KmwUX3Y2C Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Jeffrey, thanks a lot for your reply. On Sun, 25 Apr 2010, Jeffrey Altman wrote: > [...]=20 > 1.5.74 is the current release. Yes, but it wasn't at the time I setup up the Windows machine. >=20 > > Unfortunately, the maximum transfer speed on Windows is about 8-10 > > MB/sec when I copy local files to an OpenAFS volume.=20 >=20 > This is common when encryption is in use, jumbo grams are disabled, and > the file server is running with its defaults. Ok, but jumbo grams are an IPv6 only feature, right? (At least that's what googling revealed). Any good hints for tuning of the file server? > [...]=20 > Disabling encryption of the data will result in significant performance > improvements and the cost of sending your data in the clear. Ok, will think about it. > [...]=20 > In reading the rest of the thread, there appears to be a mixture of > reports describing Windows and Unix cache manager performance numbers. > In this e-mail you are asking specifically about Windows. I'm not sure > that the discussion of tuning Unix cache managers is of any value to you. Well, probably tuning both sides (Windows and Unix cache managers) is of value to me, so I'm open to suggestions for both. > [...] > On Windows, there is one type of cache. It is a memory mapped paging fil= e. Ok, how do I tune that appropriately? Thanks a lot for your detailed explanations. Kind regards, Holger =20 --a8Wt8u1KmwUX3Y2C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEUEARECAAYFAkvVQZwACgkQbiVtWpZdKQLTSgCWOfeXdfggzcBH6ElhVwLE93iK ewCePrWPJCKT68MY4oRS3k/5f9J5F1s= =oOnw -----END PGP SIGNATURE----- --a8Wt8u1KmwUX3Y2C-- From holger.rauch@empic.de Mon Apr 26 08:40:40 2010 From: holger.rauch@empic.de (Holger Rauch) Date: Mon, 26 Apr 2010 09:40:40 +0200 Subject: [OpenAFS] Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? In-Reply-To: <4BD49D65.9070804@cgv.tugraz.at> References: <20100326182248.GA15657@heitec.de><4BD40DB4.9040703@cgv.tugraz.at><20100425141951.GB305@heitec.de><4BD49D65.9070804@cgv.tugraz.at> Message-ID: <20100426074040.GB21381@heitec.de> --v9Ux+11Zm5mwPlX6 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Lars, thanks for your reply. Lars Schimmer schrieb am Sunday, den 25. April 2010: > [...] A network filesystem has some more needs > than a local one ;-) I'm aware of that, but even when I transfer a large .iso file (~ 600 MB) using scp to a remote host acting an an NFSv4 client and has a file system mounted with sec=3Dkrb5i, I still get roughly the same speeds as if using scp directly to local file system on the remote host (around 60-80 MB/sec). > [...] > > Any good ideas as to how to test memcache? >=20 > Get a machine use memcache, deactivate encryption and test the transfer > rates? That exactly was my question: How do I actually use (read: enable/configure, etc.) memcache? Thanks in advance for any info. Kind regards, Holger =20 --v9Ux+11Zm5mwPlX6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvVQ3gACgkQbiVtWpZdKQIHRwCeONsDx8sVCZEiI7oCEePS/qcy k5IAoIq3JL/FGbKvr1RNqc5JQ8ta1gGf =ktj8 -----END PGP SIGNATURE----- --v9Ux+11Zm5mwPlX6-- From holger.rauch@empic.de Mon Apr 26 08:44:15 2010 From: holger.rauch@empic.de (Holger Rauch) Date: Mon, 26 Apr 2010 09:44:15 +0200 Subject: [OpenAFS] Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? In-Reply-To: <351FB1FA-A78D-4E48-9B3B-15B82A9B2E8B@inf.ed.ac.uk> References: <20100326182248.GA15657@heitec.de><4BD40DB4.9040703@cgv.tugraz.at><20100425141951.GB305@heitec.de><351FB1FA-A78D-4E48-9B3B-15B82A9B2E8B@inf.ed.ac.uk> Message-ID: <20100426074415.GC21381@heitec.de> --ncSAzJYg3Aa9+CRW Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Simon, thanks for your reply. On Sun, 25 Apr 2010, Simon Wilkinson wrote: > [...]=20 > Firstly, as I (and others) have mentioned, OpenAFS doesn't use DES, it us= es an encryption algorithm called fcrypt, which is a DES derivative. I got the impression that DES was used because one has to use enable_weak_crypto with recent MIT Kerberos versions, which enables DES. Kind regards, Holger =20 --ncSAzJYg3Aa9+CRW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvVRE8ACgkQbiVtWpZdKQLXGACeJJkiOOhfFYIewMSb6HleKhpr Q6gAniatzv1wfsjeXJT8XTx0cFGz+OMh =ju9n -----END PGP SIGNATURE----- --ncSAzJYg3Aa9+CRW-- From haba@kth.se Mon Apr 26 10:32:43 2010 From: haba@kth.se (Harald Barth) Date: Mon, 26 Apr 2010 11:32:43 +0200 (CEST) Subject: [OpenAFS] Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? In-Reply-To: <20100426073244.GA21381@heitec.de> References: <20100326182248.GA15657@heitec.de> <4BD4EF99.6070901@secure-endpoints.com> <20100426073244.GA21381@heitec.de> Message-ID: <20100426.113243.07197285.haba@habanero.pdc.kth.se> > Ok, but jumbo grams are an IPv6 only feature, right? No. Unfortunately the name is quite overloaded. So I'd rather say "IP packets sent on a network with an MTU > 1500". But that is rather long. Normally people talk only about ethernet. Other technologies have different default MTU sizes, for example FDDI had 4k. In addition to that, some rx implementation have the habit to send rx packets in IP packets that span multiples (typically 4) times the MTU size. These packets are then fragmented and reassembled by the IP stack. I doubt that that is a good choice today. Harald. PS: # ifconfig -a ... eth0 Link encap:Ethernet HWaddr 00:1E:C9:B4:02:B3 inet addr:130.237.232.185 Bcast:130.237.232.255 Mask:255.255.255.0 ... UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ... ib0 Link encap:InfiniBand HWaddr 80:00:00:48:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00 ... UP BROADCAST RUNNING MULTICAST MTU:65520 Metric:1 ... From jaltman@secure-endpoints.com Mon Apr 26 11:09:04 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Mon, 26 Apr 2010 06:09:04 -0400 Subject: [OpenAFS] Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? In-Reply-To: <20100426074415.GC21381@heitec.de> References: <20100326182248.GA15657@heitec.de><4BD40DB4.9040703@cgv.tugraz.at><20100425141951.GB305@heitec.de><351FB1FA-A78D-4E48-9B3B-15B82A9B2E8B@inf.ed.ac.uk> <20100426074415.GC21381@heitec.de> Message-ID: <4BD56640.80107@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms090903070509020106090700 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/26/2010 3:44 AM, Holger Rauch wrote: > Hi Simon, >=20 > thanks for your reply. >=20 > On Sun, 25 Apr 2010, Simon Wilkinson wrote: >=20 >> [...]=20 >> Firstly, as I (and others) have mentioned, OpenAFS doesn't use DES, it= uses an encryption algorithm called fcrypt, which is a DES derivative. >=20 > I got the impression that DES was used because one has to use > enable_weak_crypto with recent MIT Kerberos versions, which enables DES= =2E The key form that is used with fcrypt is the same as DES (aka 56-bit parity checked keys). The encryption itself is not. Jeffrey Altman --------------ms090903070509020106090700 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MjYxMDA5MDRaMCMGCSqGSIb3DQEJBDEWBBQGODpr RHNXW8iQgXqEoaNU6EKyqzBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBALdm9B/wBcN91HaJiItV3rfd+gOMWAZqY9f6 B7iXTIRQguETUIn33aD+P15kPmhpT0FfgiTVg+gkZUgMPnpDewvhRFse5MfLVLRfQkfrUuWR waSLhLojTMToaunZsgTSnCki2NqisM7Baf7sOsNkNafBJF3oRKane36yObESE9SnG7o2PBev 7pUkKE850Brc6ZM3GWv+zfo7cZIZZAk6Mrxchtlpdta6UZYIwRUDpEIQ9D9KIy6IKfdPPKvx WroQ1cC42s8LCx4IR3kBdWsLtkQ4KvYrfa6uA8zRojwD4qSKVGXLRV4+adpHXtLvCCSUI7IT XaEEIs/BLTLNpioL0vEAAAAAAAA= --------------ms090903070509020106090700-- From jaltman@secure-endpoints.com Mon Apr 26 11:12:40 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Mon, 26 Apr 2010 06:12:40 -0400 Subject: [OpenAFS] Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? In-Reply-To: <20100426073244.GA21381@heitec.de> References: <20100326182248.GA15657@heitec.de><4BD4EF99.6070901@secure-endpoints.com> <20100426073244.GA21381@heitec.de> Message-ID: <4BD56718.8020603@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms030209010205010009030304 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/26/2010 3:32 AM, Holger Rauch wrote: >>> Unfortunately, the maximum transfer speed on Windows is about 8-10 >>> MB/sec when I copy local files to an OpenAFS volume.=20 >> >> This is common when encryption is in use, jumbo grams are disabled, an= d >> the file server is running with its defaults. >=20 > Ok, but jumbo grams are an IPv6 only feature, right? (At least that's > what googling revealed). Any good hints for tuning of the file server? Rx jumbograms have nothing to do with IPv6. OpenAFS has no IPv6 support at present. See "-jumbo" option on the UNIX CM and servers and the equivalent registry value for Windows that is documented in Appendix A of the OpenAFS for Windows Release Notes. >> [...] >> On Windows, there is one type of cache. It is a memory mapped paging = file. >=20 > Ok, how do I tune that appropriately? All of the knobs are described in the OpenAFS for Windows Release Notes. If you have not read them, please do. If you then have questions, feel free to ask them. Jeffrey Altman --------------ms030209010205010009030304 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MjYxMDEyNDBaMCMGCSqGSIb3DQEJBDEWBBSYUlUI rbaPY6yu7yl3ljbXkl88WDBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAFNmrzh1EmkbMAHyy8JvrxtfBRTb047C6rOP 4IHAwRpNo7bq8MovfKU1NXnzYP1n3eengGVifk9h2BhilOyK+gPxMYfN8RPP0k87aWlN782N s+AibdTnL/gLSSQdzLQ+j9s6XP9vYOw1Hw1CykTgo7w36igvven5iCDAMLi4JOSWnQwxHuIN fw899El4NAqhlyJZXvs2mUUOuPqvmMNN3qXs9EbTMwH7dKpGK5InkHtWY3/dTRuLWhzQajGf xo1f8iBWK4mvSh5NruQa0KBImmS1qZGm/4wdVcEGpNTQYdYO9smwf04LGloIblhrse4nDCvG CgiDQzhvHc1wqSuQuM0AAAAAAAA= --------------ms030209010205010009030304-- From shadow@gmail.com Mon Apr 26 13:32:36 2010 From: shadow@gmail.com (Derrick Brashear) Date: Mon, 26 Apr 2010 08:32:36 -0400 Subject: [OpenAFS] Documentation for Preference Pane in 1.4.12 on MacOSX In-Reply-To: References: <4BCC09B3.80609@kezia.com> Message-ID: On Mon, Apr 26, 2010 at 3:13 AM, Marcus Crestani wrote: >>>>>>"FC" =3D=3D Fabien COMBERNOUS writes: > FC> To answer to many of our questions, you can use fseventer tool [1]. I= t > FC> is a useful free closed source software to know the files modified > FC> and/or created by a GUI on MacOSX. I planed to do it by myself, but i > FC> didn't yet have enough time. > > Thanks for the pointer to fseventer, this is indeed a great tool for > this and many other situations. > > But other than that, I cannot believe that there seems to be no > documentation for the new Preference Pane. =A0Anyone? There is a genesis of documentation from Arthur Prokosch which is not yet included in OpenAFS, but it is not complete yet. If you'd be willing to help edit it I can commit what he has and you can push patches to gerrit or otherwise submit changes; would that help? From rich@nd.edu Mon Apr 26 15:14:01 2010 From: rich@nd.edu (Rich Sudlow) Date: Mon, 26 Apr 2010 10:14:01 -0400 Subject: [OpenAFS] Max number of files in a volume Message-ID: <4BD59FA9.9010302@nd.edu> I'm having problems with a volume going off-line and not coming back with Salvage - what is the maximum number of files per volume? I believe the volume in question has over 20 million. Thanks, Rich -- Rich Sudlow University of Notre Dame Center for Research Computing 128 Information Technology Center PO Box 539 Notre Dame, IN 46556-0539 (574) 631-7258 office phone (574) 631-9283 office fax From adeason@sinenomine.net Mon Apr 26 15:14:13 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Mon, 26 Apr 2010 09:14:13 -0500 Subject: [OpenAFS] Re: Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? References: <20100326182248.GA15657@heitec.de> <4BD40DB4.9040703@cgv.tugraz.at> <20100425141951.GB305@heitec.de> <4BD49D65.9070804@cgv.tugraz.at> <20100426074040.GB21381@heitec.de> Message-ID: <20100426091413.da79b504.adeason@sinenomine.net> On Mon, 26 Apr 2010 09:40:40 +0200 Holger Rauch wrote: > That exactly was my question: How do I actually use (read: > enable/configure, etc.) memcache? For Unix clients, pass -memcache to afsd. You also want to make sure your cache isn't configured to be greater than your RAM when you do that. -- Andrew Deason adeason@sinenomine.net From adeason@sinenomine.net Mon Apr 26 15:46:45 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Mon, 26 Apr 2010 09:46:45 -0500 Subject: [OpenAFS] Re: Max number of files in a volume References: <4BD59FA9.9010302@nd.edu> Message-ID: <20100426094645.d45c0ea4.adeason@sinenomine.net> On Mon, 26 Apr 2010 10:14:01 -0400 Rich Sudlow wrote: > I'm having problems with a volume going off-line and not > coming back with Salvage - what is the maximum number > of files per volume? I believe the volume in question > has over 20 million. You'd need over 2 billion to saturate the vnode namespace (maybe 1 billion to get something confused about negative vnodes if that's possible). What does the salvager say when you try to salvage? -- Andrew Deason adeason@sinenomine.net From rich@nd.edu Mon Apr 26 15:58:57 2010 From: rich@nd.edu (Rich Sudlow) Date: Mon, 26 Apr 2010 10:58:57 -0400 Subject: [OpenAFS] Re: Max number of files in a volume In-Reply-To: <20100426094645.d45c0ea4.adeason@sinenomine.net> References: <4BD59FA9.9010302@nd.edu> <20100426094645.d45c0ea4.adeason@sinenomine.net> Message-ID: <4BD5AA31.1020909@nd.edu> Andrew Deason wrote: > On Mon, 26 Apr 2010 10:14:01 -0400 > Rich Sudlow wrote: > >> I'm having problems with a volume going off-line and not >> coming back with Salvage - what is the maximum number >> of files per volume? I believe the volume in question >> has over 20 million. Looks like there were actually 30 million files. > > You'd need over 2 billion to saturate the vnode namespace (maybe 1 > billion to get something confused about negative vnodes if that's > possible). > > What does the salvager say when you try to salvage? The salvage core dumps - 04/26/2010 09:43:20 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager /vicepa 536881461) 04/26/2010 10:28:43 2 nVolumesInInodeFile 56 04/26/2010 10:28:47 CHECKING CLONED VOLUME 536881465. 04/26/2010 10:28:47 g.dial.backup (536881465) updated 04/26/2010 01:32 04/26/2010 10:29:07 SALVAGING VOLUME 536881461. 04/26/2010 10:29:07 g.dial (536881461) updated 04/26/2010 04:22 04/26/2010 10:30:41 "Salvage volume group" core dumped! the volume went off line when the fileserver core dumped earlier. Mon Apr 26 04:22:47 2010 Program aborted: Mon Apr 26 04:22:47 2010 VAllocVnode: can't stat index file! Rich > -- Rich Sudlow University of Notre Dame Center for Research Computing 128 Information Technology Center PO Box 539 Notre Dame, IN 46556-0539 (574) 631-7258 office phone (574) 631-9283 office fax From adeason@sinenomine.net Mon Apr 26 16:27:29 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Mon, 26 Apr 2010 10:27:29 -0500 Subject: [OpenAFS] Re: Max number of files in a volume References: <4BD59FA9.9010302@nd.edu> <20100426094645.d45c0ea4.adeason@sinenomine.net> <4BD5AA31.1020909@nd.edu> Message-ID: <20100426102729.5c90e976.adeason@sinenomine.net> On Mon, 26 Apr 2010 10:58:57 -0400 Rich Sudlow wrote: > 04/26/2010 10:29:07 g.dial (536881461) updated 04/26/2010 04:22 > 04/26/2010 10:30:41 "Salvage volume group" core dumped! Platform? Is this namei? If you're missing the small/large vnode index as indicated by the fileserver log below... I don't know how recoverable that is. At least on namei, I think we could probably recover the individual files (possibly only those not in the backup volume you appear to have)... but directory structure etc would be lost at least. Anyway, the salvager doesn't currently handle this case at all, I don't think. Data can possibly be recovered, but it's not easy. But that's assuming that's what you're missing. To be sure... assuming you're on something with gdb: # gdb /usr/afs/bin/salvager /path/to/core (gdb) bt be careful of any sensitive information in that backtrace; worst thing I can think of that would appear is a file name. > Mon Apr 26 04:22:47 2010 Program aborted: > Mon Apr 26 04:22:47 2010 VAllocVnode: can't stat index file! Ugh, wow, we could certainly handle this a bit better... -- Andrew Deason adeason@sinenomine.net From holger.rauch@empic.de Mon Apr 26 17:32:15 2010 From: holger.rauch@empic.de (Holger Rauch) Date: Mon, 26 Apr 2010 18:32:15 +0200 Subject: [OpenAFS] Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? In-Reply-To: <4BD56718.8020603@secure-endpoints.com> References: <20100326182248.GA15657@heitec.de><4BD4EF99.6070901@secure-endpoints.com><20100426073244.GA21381@heitec.de><4BD56718.8020603@secure-endpoints.com> Message-ID: <20100426163215.GA12340@heitec.de> --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Jeffrey, thanks for your reply. On Mon, 26 Apr 2010, Jeffrey Altman wrote: > [...]=20 > Rx jumbograms have nothing to do with IPv6. OpenAFS has no IPv6 support > at present. See "-jumbo" option on the UNIX CM Sorry, didn't find anything about "-jumbo" in the afsd man page. So, to which daemon does this option belong to exactly? > and servers and the > equivalent registry value for Windows that is documented in Appendix A > of the OpenAFS for Windows Release Notes. Yes, I read the appendix. I came accross a registry parameter having "NoJumbo" in it. So, I suppose I've got to set the value for that parameter to 0 in order to enable jumbogram usage on Windows, right? >=20 > >> [...] > >> On Windows, there is one type of cache. It is a memory mapped paging = file. Ok, and how should it be tuned for a gigabit networking environment? (Please see my notes below). > >=20 > > Ok, how do I tune that appropriately? >=20 > All of the knobs are described in the OpenAFS for Windows Release Notes. > If you have not read them, please do. If you then have questions, feel > free to ask them. Well, "described" is a bit exaggerated, IMHO. They are "mentioned" in the sense that a short statement is made as to what each parameter is determined for. There's nothing wrong with that, but what's missing IMHO are explanations as to how the parameters are related to each other, especially in the sense of performance tuning. Furthermore, concrete examples for *current* network setups (e.g. gigabit networking) would be nice. So, as unfortunate as it may be, I have to repeat my original question, slightly paraphrased in two questions: Which parameters should be adjusted for an OpenAFS Windows client and a Unix server when both are operated in a gigabit network? What values are recommended for these parameters? (Sorry to bother you with these questions, but IMHO sort of hard to infer from the release notes without concrete examples). Thanks for your advice & kind regards, Holger =20 --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvVwA8ACgkQbiVtWpZdKQIj6ACeIWkJNja4cd9LJ2tLGga0OtmT i4MAniLAhFp951RVhcO3HOLcD0dVbx/E =QfnI -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- From adeason@sinenomine.net Mon Apr 26 17:50:47 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Mon, 26 Apr 2010 11:50:47 -0500 Subject: [OpenAFS] Re: Why is speed of AFS loopback adapter set to 10 Mb, even if physical interface is Gb capable? References: <20100326182248.GA15657@heitec.de> <4BD4EF99.6070901@secure-endpoints.com> <20100426073244.GA21381@heitec.de> <4BD56718.8020603@secure-endpoints.com> <20100426163215.GA12340@heitec.de> Message-ID: <20100426115047.8b44d97a.adeason@sinenomine.net> On Mon, 26 Apr 2010 18:32:15 +0200 Holger Rauch wrote: > Sorry, didn't find anything about "-jumbo" in the afsd man page. So, > to which daemon does this option belong to exactly? Just server daemons. For your purposes in this thread, the fileserver is the only relevant daemon to use it with. (I don't think anything is necessary on the Unix CM to use them, but I'm not the one to ask.) You generally want jumbograms off, though, unless the only communication between fileservers and clients is on networks you control, and you know what such networks can handle fragmented packets. They're usually not beneficial across the general Internet from what I've seen. -- Andrew Deason adeason@sinenomine.net From mmeffie@sinenomine.net Mon Apr 26 19:25:13 2010 From: mmeffie@sinenomine.net (Michael Meffie) Date: Mon, 26 Apr 2010 14:25:13 -0400 Subject: [OpenAFS] Re: pts -expandgroups vs -supergroups In-Reply-To: <20100422220058.c0cce958.adeason@sinenomine.net> References: <4BD0E015.8050902@rampaginggeek.com> <20100422220058.c0cce958.adeason@sinenomine.net> Message-ID: <4BD5DA89.7070502@sinenomine.net> Andrew Deason wrote: > On Thu, 22 Apr 2010 19:47:33 -0400 > Jason Edgecombe wrote: > >> Hi, >> >> What is the difference between the new -expandgroups and -supergroups >> options to the pts mem command? That seem identical in my reading. > > -expandgroups just expands the listing of the normal pts output. So, if > you have 'foo' is a member of 'bar' is a member of 'baz', 'pts mem baz' > would just list 'bar'. Running 'pts mem baz -expandgroups' will list > 'bar' and 'foo'. > > -supergroups lists the "parent" groups of a group. Normally if you run > 'pts mem groupname' for a group, it lists the members of the group. > 'pts mem groupname -supergroups' lists the groups that contain > 'groupname'. Yes, said another way, -supergroups only gives you an addition stanza of information (and only for groups), where -expandgroups gives you a completely different stanza by traversing the group nesting (for groups and for users). pts mem -supergroups adds the list of groups the group belongs to (the supergroups) to the output. It has no effect when getting the membership of a user, because pts already lists the groups a user belongs to. pts mem -supergroups does not recurse, it only lists the direct supergroups of a group. The -expandgroups recurses to find all the users in a group, and recurses to find all the groups a user belongs to. > The documentation could probably stand to have some examples. Yes, it could. Is the following clear and helpful? The following example shows how to list the groups to which nested groups belong. In this example the group C is a member of the group C and the group C is a member of the group C. The group C is called a supergroup of the group C and the group C is called a supergroup of the group C. % pts membership executives Members of executives (id: -208) are: jane % pts membership executives -supergroups Members of executives (id: -208) are: jane Groups executives (id: -208) is a member of: management % pts membership management -supergroups Members of management (id: -207) are: executives mary sarah carol Groups management (id: -207) is a member of: staff % pts membership staff -supergroups Members of staff (id: -206) are: sales marketing engineering management Groups staff (id: -206) is a member of: The following example shows how to find all the users which belong to a group, including users of nested groups. In this example, the user C is listed as an expanded member of the group C instead of the group C. % pts membership management -expandgroups Expanded Members of management (id: -207) are: jane mary sarah carol The following example shows how to find all the groups a user is a member of, including membership due to nested groups. In this example the user C is a direct member of the group C. The C<-expandgroups> flag shows all the groups to which C has membership status. % pts membership jane Groups jane (id: 7) is a member of: executives % pts membership jane -expandgroups Expanded Groups jane (id: 7) is a member of: staff management executives From mmeffie@sinenomine.net Mon Apr 26 19:38:40 2010 From: mmeffie@sinenomine.net (Michael Meffie) Date: Mon, 26 Apr 2010 14:38:40 -0400 Subject: [OpenAFS] Re: pts -expandgroups vs -supergroups In-Reply-To: <20100425175647.698f49c7.adeason@sinenomine.net> References: <4BD0E015.8050902@rampaginggeek.com> <20100422220058.c0cce958.adeason@sinenomine.net> <4BD1D23E.9050802@rampaginggeek.com> <20100425124507.49400619.adeason@sinenomine.net> <4BD4A10D.5060105@rampaginggeek.com> <20100425175647.698f49c7.adeason@sinenomine.net> Message-ID: <4BD5DDB0.9070307@sinenomine.net> Andrew Deason wrote: > On Sun, 25 Apr 2010 16:07:41 -0400 Jason Edgecombe > wrote: > >> Can I use that patch against the 1.4.x tree? > > Probably; I don't imagine pts code is very different. If it's > something that would be considered appropriate for 1.4, submit > the cherry pick to gerrit. Or Mike or I could do it (or... > anyone). > > >> Can I use the 1.5.x pts with that patch on a 1.4.x client with >> 1.4.x servers? > > Yes. The backport to 1.4.x is trivial, the only thing to watch for is the new prototypes in ptuser.h due to the code reformatting between 1.4.x and 1.5.x in that header. However, this is strictly a change to the pts client, so yes, 1.5.x pts works against your 1.4.x server. Mike -- From adam@megacz.com Mon Apr 26 19:39:07 2010 From: adam@megacz.com (Adam Megacz) Date: Mon, 26 Apr 2010 18:39:07 +0000 Subject: [OpenAFS] Re: experience of SQLite on AFS References: <4BD4EA1C.3070603@secure-endpoints.com> Message-ID: Jeffrey Altman writes: > When a whole file lock is write-held, all of the dirty data in the cache > must be written back to the file server before the lock is released. > This is currently not being done and as a result, the database becomes > corrupted. > > I suspect this will be fixed shortly. Please notify me once the this is fixed in the Linux CM and I will test it for you. - a From shadow@gmail.com Mon Apr 26 19:45:43 2010 From: shadow@gmail.com (Derrick Brashear) Date: Mon, 26 Apr 2010 14:45:43 -0400 Subject: [OpenAFS] Re: experience of SQLite on AFS In-Reply-To: References: <4BD4EA1C.3070603@secure-endpoints.com> Message-ID: the best way to know it's fixed? watch the release announcements. it's not like we're going to be coy about it. On Mon, Apr 26, 2010 at 2:39 PM, Adam Megacz wrote: > > Jeffrey Altman writes: >> When a whole file lock is write-held, all of the dirty data in the cache >> must be written back to the file server before the lock is released. >> This is currently not being done and as a result, the database becomes >> corrupted. >> >> I suspect this will be fixed shortly. > > Please notify me once the this is fixed in the Linux CM and I will test > it for you. > > =A0- a > > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info > --=20 Derrick From tkeiser@sinenomine.net Mon Apr 26 21:33:26 2010 From: tkeiser@sinenomine.net (Tom Keiser) Date: Mon, 26 Apr 2010 16:33:26 -0400 Subject: [OpenAFS] Re: Max number of files in a volume In-Reply-To: <4BD5AA31.1020909@nd.edu> References: <4BD59FA9.9010302@nd.edu> <20100426094645.d45c0ea4.adeason@sinenomine.net> <4BD5AA31.1020909@nd.edu> Message-ID: On Mon, Apr 26, 2010 at 10:58 AM, Rich Sudlow wrote: > Andrew Deason wrote: >> >> On Mon, 26 Apr 2010 10:14:01 -0400 >> Rich Sudlow wrote: >> >>> I'm having problems with a volume going off-line and not >>> coming back with Salvage - what is the maximum number >>> of files per volume? I believe the volume in question >>> has over 20 million. > > Looks like there were actually 30 million files. > Hi Rich, On most platforms we build the salvager as a 32-bit binary (excluding certain 64-bit linux platforms where the platform maintainers decided to simplify things by making everything a 64-bit binary). One operation that the salvager performs is to build an in-memory index of critical details for every vnode in the volume [see SalvageIndex() in src/vol/vol-salvage.c]. Each entry in this array requires 56 bytes in a 32-bit process, which comes out to 1602MB of virtual memory for 30 million files. Likewise, we require 56 bytes per directory vnode, which for 30 million files requires a minimum of ~462 directories, and thus an additional 26MB of heap. My suspicion is your salvager is core dumping because the heap and the stack have grown into each other. Depending on the hardware, it may be possible to build a custom 64-bit salvager to work around this issue. The first step here is to figure out whether your salvager binary is 32-bit or 64-bit; the output of file /usr/afs/bin/salvager should be sufficient. Cheers, -Tom From jfgodfrey@gmail.com Mon Apr 26 00:18:07 2010 From: jfgodfrey@gmail.com (John F. Godfrey) Date: Sun, 25 Apr 2010 17:18:07 -0600 Subject: [OpenAFS] No new token after re-authenticating from screensave Message-ID: <1272237487.14985.2.camel@church.spirit.org> A question about tokens on debian lenny. When I log back in, or come back through a screensaver that needs a password to authenticate, I get a renewed kerberos ticket. However, I don't get a new afs token, so have to do an aklog. Not a big deal, but is there a way to change/adjust this behavior? Thanks! john -- John F. Godfrey, Pastor Belgrade Christian Assembly Belgrade, MT 59714 "Jesus said to him, 'I am the Way, and the Truth, and the Life; no one comes to the Father but through Me'" (John 14:6). From jason@rampaginggeek.com Tue Apr 27 01:04:19 2010 From: jason@rampaginggeek.com (Jason Edgecombe) Date: Mon, 26 Apr 2010 20:04:19 -0400 Subject: [OpenAFS] Re: pts -expandgroups vs -supergroups In-Reply-To: <4BD5DDB0.9070307@sinenomine.net> References: <4BD0E015.8050902@rampaginggeek.com> <20100422220058.c0cce958.adeason@sinenomine.net> <4BD1D23E.9050802@rampaginggeek.com> <20100425124507.49400619.adeason@sinenomine.net> <4BD4A10D.5060105@rampaginggeek.com> <20100425175647.698f49c7.adeason@sinenomine.net> <4BD5DDB0.9070307@sinenomine.net> Message-ID: <4BD62A03.9070408@rampaginggeek.com> Michael Meffie wrote: > Andrew Deason wrote: >> On Sun, 25 Apr 2010 16:07:41 -0400 Jason Edgecombe >> wrote: >> >>> Can I use that patch against the 1.4.x tree? >> >> Probably; I don't imagine pts code is very different. If it's >> something that would be considered appropriate for 1.4, submit >> the cherry pick to gerrit. Or Mike or I could do it (or... >> anyone). >> >> >>> Can I use the 1.5.x pts with that patch on a 1.4.x client with >>> 1.4.x servers? >> >> Yes. > > The backport to 1.4.x is trivial, the only thing to watch for is > the new prototypes in ptuser.h due to the code reformatting > between 1.4.x and 1.5.x in that header. However, this is strictly > a change to the pts client, so yes, 1.5.x pts works against > your 1.4.x server. cool, thanks. Jason From rra@stanford.edu Tue Apr 27 01:07:13 2010 From: rra@stanford.edu (Russ Allbery) Date: Mon, 26 Apr 2010 17:07:13 -0700 Subject: [OpenAFS] No new token after re-authenticating from screensave In-Reply-To: <1272237487.14985.2.camel@church.spirit.org> (John F. Godfrey's message of "Sun, 25 Apr 2010 17:18:07 -0600") References: <1272237487.14985.2.camel@church.spirit.org> Message-ID: <87sk6h21xq.fsf@windlord.stanford.edu> "John F. Godfrey" writes: > A question about tokens on debian lenny. When I log back in, or come > back through a screensaver that needs a password to authenticate, I get > a renewed kerberos ticket. However, I don't get a new afs token, so > have to do an aklog. Not a big deal, but is there a way to > change/adjust this behavior? What does your PAM configuration look like? pam-afs-session should take care of this if you use its recommended configuration (primarily listing it in the session stack). -- Russ Allbery (rra@stanford.edu) From crestani@informatik.uni-tuebingen.de Tue Apr 27 18:51:31 2010 From: crestani@informatik.uni-tuebingen.de (Marcus Crestani) Date: Tue, 27 Apr 2010 19:51:31 +0200 Subject: [OpenAFS] Documentation for Preference Pane in 1.4.12 on MacOSX In-Reply-To: (Derrick Brashear's message of "Mon, 26 Apr 2010 08:32:36 -0400") References: <4BCC09B3.80609@kezia.com> Message-ID: >>>>>"DB" == Derrick Brashear writes: DB> There is a genesis of documentation from Arthur Prokosch which is not DB> yet included in OpenAFS, but it is not complete yet. If you'd be DB> willing to help edit it I can commit what he has and you can push DB> patches to gerrit or otherwise submit changes; would that help? Sure, if there is documentation of the Preference Pane included. -- Marcus From jblaine@kickflop.net Tue Apr 27 20:09:56 2010 From: jblaine@kickflop.net (Jeff Blaine) Date: Tue, 27 Apr 2010 15:09:56 -0400 Subject: [OpenAFS] Windows : CellServDB from website at install-time? Message-ID: <4BD73684.4050906@kickflop.net> Is this gone forever? Am I just missing it? 1.5.66 had it 1.5.74 doesn't This allowed us a) a simple way for users to configure the cell information without visiting the control panel at all b) a simple way to trash the provided CellServDB cells in the same action (we don't have access to or participate in the global /afs namespace). From jaltman@secure-endpoints.com Tue Apr 27 20:30:18 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Tue, 27 Apr 2010 15:30:18 -0400 Subject: [OpenAFS] Windows : CellServDB from website at install-time? In-Reply-To: <4BD73684.4050906@kickflop.net> References: <4BD73684.4050906@kickflop.net> Message-ID: <4BD73B4A.7000700@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms010501090008070308090406 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =2Eexe has it =2Emsi does not I have recommended for a long time that organizations should distribute openafs msi installers that have been customized using transforms to include their own configuration data for their users. This is documented in the release notes. Asanka Herath also gave a talk on this subject at the NJIT AFS and Kerberos workshop. Jeffrey Altman On 4/27/2010 3:09 PM, Jeff Blaine wrote: > Is this gone forever? Am I just missing it? >=20 > 1.5.66 had it > 1.5.74 doesn't >=20 > This allowed us >=20 > a) a simple way for users to configure the cell > information without visiting the control panel > at all >=20 > b) a simple way to trash the provided CellServDB > cells in the same action (we don't have access > to or participate in the global /afs namespace). > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info >=20 --------------ms010501090008070308090406 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MjcxOTMwMThaMCMGCSqGSIb3DQEJBDEWBBSHzTRV FfRZ/VPGQxLMBpq7NFDPzTBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAGL5Vzs/uc/bXNiMLCCCOjSt1Qg6LleN6tkW NVX+JjPUnjJCw/aEl7uOn9q6rJsJfteatjqgIs4gSsIEs6Sx/lZTE90XSF4k3eiYo5M1iQBM rCwCuCSHwmIhow1OE3KTAQXDKWNN66B0jG44zJ2LUcO7N/4QbHgeVBjJ6hGy9+Yd+OyzKaVs wtRr3nhALaugX8rxF5r+zBfOT5vutSLxKnQ+VWVTy8FpO8Vzqk/FG9hfUPlUD9GZr+1/Ro51 kKEbdgbEbF6+FkB1v/EIlpoKW+UtS0ILrDjgtXEq3mqRSRDbYodjQ11odnGne5Q14GdquoYE yY7BBOGTc0FKS6QxbpcAAAAAAAA= --------------ms010501090008070308090406-- From jblaine@kickflop.net Tue Apr 27 20:39:54 2010 From: jblaine@kickflop.net (Jeff Blaine) Date: Tue, 27 Apr 2010 15:39:54 -0400 Subject: [OpenAFS] Windows : CellServDB from website at install-time? In-Reply-To: <4BD73B4A.7000700@secure-endpoints.com> References: <4BD73684.4050906@kickflop.net> <4BD73B4A.7000700@secure-endpoints.com> Message-ID: <4BD73D8A.4030303@kickflop.net> On 4/27/2010 3:30 PM, Jeffrey Altman wrote: > .exe has it > > .msi does not I have the complete opposite listed in my notes and our documentation for users per previous conversation with the list. *confused* > I have recommended for a long time that organizations should distribute > openafs msi installers that have been customized using transforms to > include their own configuration data for their users. This is > documented in the release notes. Asanka Herath also gave a talk on this > subject at the NJIT AFS and Kerberos workshop. In an ideal world, I would learn how to do such a thing and make one. As it is, this small step proved good enough for the time-being for the ~10 Windows+OpenAFS users we deal with. > Jeffrey Altman > > > On 4/27/2010 3:09 PM, Jeff Blaine wrote: >> Is this gone forever? Am I just missing it? >> >> 1.5.66 had it >> 1.5.74 doesn't >> >> This allowed us >> >> a) a simple way for users to configure the cell >> information without visiting the control panel >> at all >> >> b) a simple way to trash the provided CellServDB >> cells in the same action (we don't have access >> to or participate in the global /afs namespace). >> _______________________________________________ >> OpenAFS-info mailing list >> OpenAFS-info@openafs.org >> https://lists.openafs.org/mailman/listinfo/openafs-info >> > From shadow@gmail.com Tue Apr 27 21:08:35 2010 From: shadow@gmail.com (Derrick Brashear) Date: Tue, 27 Apr 2010 16:08:35 -0400 Subject: [OpenAFS] Windows : CellServDB from website at install-time? In-Reply-To: <4BD73D8A.4030303@kickflop.net> References: <4BD73684.4050906@kickflop.net> <4BD73B4A.7000700@secure-endpoints.com> <4BD73D8A.4030303@kickflop.net> Message-ID: On Tue, Apr 27, 2010 at 3:39 PM, Jeff Blaine wrote: > On 4/27/2010 3:30 PM, Jeffrey Altman wrote: >> >> .exe has it >> >> .msi does not > > I have the complete opposite listed in my notes and our > documentation for users per previous conversation with > the list. =A0*confused* > >> I have recommended for a long time that organizations should distribute >> openafs msi installers that have been customized using transforms to >> include their own configuration data for their users. =A0This is >> documented in the release notes. =A0Asanka Herath also gave a talk on th= is >> subject at the NJIT AFS and Kerberos workshop. > > In an ideal world, I would learn how to do such a thing > and make one. =A0As it is, this small step proved good > enough for the time-being for the ~10 Windows+OpenAFS > users we deal with. The msi transform is incredibly simple, you write it once, and then run it. I have no idea if you have a support contract but your support contractor could certainly do it too. From jaltman@secure-endpoints.com Tue Apr 27 21:18:10 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Tue, 27 Apr 2010 16:18:10 -0400 Subject: [OpenAFS] Windows : CellServDB from website at install-time? In-Reply-To: <4BD73D8A.4030303@kickflop.net> References: <4BD73684.4050906@kickflop.net> <4BD73B4A.7000700@secure-endpoints.com> <4BD73D8A.4030303@kickflop.net> Message-ID: <4BD74682.40406@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms050401040704080400090908 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/27/2010 3:39 PM, Jeff Blaine wrote: > On 4/27/2010 3:30 PM, Jeffrey Altman wrote: >> .exe has it >> >> .msi does not >=20 > I have the complete opposite listed in my notes and our > documentation for users per previous conversation with > the list. *confused* I'm sorry that you are confused by the functionality used to implement the copy config file at install time is built into NSIS which is used to produce the 32-bit .exe installers. It is not present in the WiX Toolkit that we use for the 32-bit and 64-bit .msi installers. This is true of both KFW and OpenAFS. It has been this way since I started building the OpenAFS installers in late 2003. >> I have recommended for a long time that organizations should distribut= e >> openafs msi installers that have been customized using transforms to >> include their own configuration data for their users. This is >> documented in the release notes. Asanka Herath also gave a talk on th= is >> subject at the NJIT AFS and Kerberos workshop. >=20 > In an ideal world, I would learn how to do such a thing > and make one. As it is, this small step proved good > enough for the time-being for the ~10 Windows+OpenAFS > users we deal with. Transforms are created once and then applied to each OpenAFS subsequent MSI release. It does require a certain comfort level with the Microsoft Installer tools. If you don't want to do it yourself, you can hire people to do so including Secure Endpoints. Jeffrey Altman --------------ms050401040704080400090908 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MjcyMDE4MTBaMCMGCSqGSIb3DQEJBDEWBBRHgIM5 grIgGWw0bi4WoaXtSDA/FjBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBADvNrY4YYSAC5UDqL1efRMDxHr/iG6u20xBy hbyevZ2W9QMt/vUlbEtcgJCSXZZKQ9+oIvJiuMZnPnDyiDKc4GtjFAHhwMbqnm1+rp8muR6q RCSsjfp5SsB/Fy1iwtp+a+qbM0WY5p32ffF4jZbxZ5sB+aAJYj2Eikake5Rz32rYboB0ul4q QFXB8ZUQGsIf3bg6C3C0C7meHlIgAilKm/d1HI7dWao+n09iqqxI90EwctHjjEpkql8x1twT DuOY8IjAi+vkk1MH0O1LP+04sHVT9MA7/cH3UBONeU9gKGDn+DAAovc3UNTVONfgQs0voGMn Jpe4ov+ozpRUZMWGFeUAAAAAAAA= --------------ms050401040704080400090908-- From bampfamd@berkeley.edu Tue Apr 27 21:49:26 2010 From: bampfamd@berkeley.edu (bampfamd@berkeley.edu) Date: Tue, 27 Apr 2010 13:49:26 -0700 Subject: [OpenAFS] openAFS 1.4.12 Kernel Panic on restart? (mac) In-Reply-To: <4BCDEEB5.1080702@mitre.org> References: <4BCDEEB5.1080702@mitre.org> Message-ID: Hi, just wondering if anyone could really help with this issue? sam and I seems to be having the same problem > I'm also having this problem, Mac Pro version 1,1 running 10.6.3. I ran > > % sudo /Library/OpenAFS/Tools/tools/decode-panic -i > /Library/Logs/DiagnosticReports/Kernel_2010-04-19-175345_mac-admins-mac-pro.panic > > > which I believe is what you were asking the previous correspondent on > this thread, and retrieved the attached file from /var/db/openafs/logs. > The attached panic probably has other kernel modules installed; I > subsequently uninstalled all of them and still encountered the problem. > > The error arises when I do > > % sudo /Library/OpenAFS/Tools/root.client/usr/vice/etc/afs.rc stop > > either on the command line directly or indirectly as part of a shutdown. > > I encountered this problem with 1.4.12 (attached dumps) as well as > 1.4.11. I did NOT encounter it with the 1.5.73-3 build; I'd send you the > decoded panic for 1.4.11 as well, except I'm getting an error with the > decode-panic script in 1.5.73 and I'm frankly bored with rebooting my > Mac today. > > Hope this helps - > Sam Bayer > The MITRE Corporation > sam@mitre.org > From sxw@inf.ed.ac.uk Wed Apr 28 11:32:41 2010 From: sxw@inf.ed.ac.uk (Simon Wilkinson) Date: Wed, 28 Apr 2010 11:32:41 +0100 Subject: [OpenAFS] Re: experience of SQLite on AFS In-Reply-To: References: <4BD4EA1C.3070603@secure-endpoints.com> Message-ID: <1E33045F-E221-40C2-95F4-3CB767CF59F6@inf.ed.ac.uk> On 26 Apr 2010, at 19:39, Adam Megacz wrote: >=20 > Jeffrey Altman writes: >> When a whole file lock is write-held, all of the dirty data in the = cache >> must be written back to the file server before the lock is released. >> This is currently not being done and as a result, the database = becomes >> corrupted. >>=20 >> I suspect this will be fixed shortly. >=20 > Please notify me once the this is fixed in the Linux CM and I will = test > it for you. Derrick has pushed changes=20 = http://git.openafs.org/?p=3Dopenafs.git;a=3Dcommit;h=3Dfa70575af3dd5b8e146= 7dd516413b6d153a9963a and = http://git.openafs.org/?p=3Dopenafs.git;a=3Dcommit;h=3D014821d281cac7815ac= 7908a853191b17bf2a868 which should fix these issues to the master branch. Once we have = sufficient confidence from that branch that the changes are correct, = they'll get pulled up to 1.4. Cheers, Simon. From mlane@sinenomine.net Wed Apr 28 22:31:48 2010 From: mlane@sinenomine.net (Mickey Lane) Date: Wed, 28 Apr 2010 16:31:48 -0500 Subject: [OpenAFS] Windows: Update KB980408 causes problems with kerberos credentials Message-ID: <1171E06FDB4D8341937880DCD831A0E2683ED523@34093-MBX-C15.mex07a.mlsrvr.com> --_000_1171E06FDB4D8341937880DCD831A0E2683ED52334093MBXC15mex0_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Windows 7 (32-bit) All updates prior to 4/27/2010 Kfw-3-2-2 Openafs-en_US-1-5-7400 Installing Windows update KB980408 (published yesterday, 4/27/2010) causes = several unexpected error dialogs related to acquiring kerberos credentials. If the error dialogs are ignored, OpenAFS seems to work (*very* brief testi= ng). I believe the problem will trigger an assert in a debug version of OpenAFS = but I haven't proved that yet. (I got asserts while dealing with another is= sue and it was only after the fact that I associated them with this situati= on.) Suggestion: Don't install KB980408 until more info is available. --_000_1171E06FDB4D8341937880DCD831A0E2683ED52334093MBXC15mex0_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Windows 7 (32-bit)

All updates prior to 4/27/2010

Kfw-3-2-2

Openafs-en_US-1-5-7400

 

Installing Windows update KB980408 (published yesterda= y, 4/27/2010) causes several unexpected error dialogs related to acquiring ker= beros credentials.

 

If the error dialogs are ignored, OpenAFS seems to wor= k (*very* brief testing).

 

I believe the problem will trigger an assert in a debu= g version of OpenAFS but I haven’t proved that yet. (I got asserts whil= e dealing with another issue and it was only after the fact that I associated them with this situation.)

 

Suggestion: Don’t install KB980408 until more in= fo is available.

 

 

--_000_1171E06FDB4D8341937880DCD831A0E2683ED52334093MBXC15mex0_-- From botsch@cnf.cornell.edu Wed Apr 28 23:47:21 2010 From: botsch@cnf.cornell.edu (Dave B) Date: Wed, 28 Apr 2010 18:47:21 -0400 Subject: [OpenAFS] Windows: Update KB980408 causes problems with kerberos credentials In-Reply-To: <1171E06FDB4D8341937880DCD831A0E2683ED523@34093-MBX-C15.mex07a.mlsrvr.com> References: <1171E06FDB4D8341937880DCD831A0E2683ED523@34093-MBX-C15.mex07a.mlsrvr.com> Message-ID: <1272494841.19673.2851.camel@flume> What about integrated login? On Wed, 2010-04-28 at 16:31 -0500, Mickey Lane wrote: > Windows 7 (32-bit) >=20 > All updates prior to 4/27/2010 >=20 > Kfw-3-2-2 >=20 > Openafs-en_US-1-5-7400 >=20 > =20 >=20 > Installing Windows update KB980408 (published yesterday, 4/27/2010) > causes several unexpected error dialogs related to acquiring kerberos > credentials. >=20 > =20 >=20 > If the error dialogs are ignored, OpenAFS seems to work (*very* brief > testing). >=20 > =20 >=20 > I believe the problem will trigger an assert in a debug version of > OpenAFS but I haven=E2=80=99t proved that yet. (I got asserts while dea= ling > with another issue and it was only after the fact that I associated > them with this situation.) >=20 > =20 >=20 > Suggestion: Don=E2=80=99t install KB980408 until more info is available. >=20 > =20 >=20 > =20 >=20 >=20 --=20 ******************************** David William Botsch Programmer/Analyst CNF Computing botsch@cnf.cornell.edu ******************************** From jaltman@secure-endpoints.com Thu Apr 29 00:55:23 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Wed, 28 Apr 2010 19:55:23 -0400 Subject: [OpenAFS] Windows: Update KB980408 causes problems with kerberos credentials In-Reply-To: <1171E06FDB4D8341937880DCD831A0E2683ED523@34093-MBX-C15.mex07a.mlsrvr.com> References: <1171E06FDB4D8341937880DCD831A0E2683ED523@34093-MBX-C15.mex07a.mlsrvr.com> Message-ID: <4BD8CAEB.3070700@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms070003000703040004070801 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/28/2010 5:31 PM, Mickey Lane wrote: > Windows 7 (32-bit) >=20 > All updates prior to 4/27/2010 >=20 > Kfw-3-2-2 >=20 > Openafs-en_US-1-5-7400 >=20 > =20 >=20 > Installing Windows update KB980408 (published yesterday, 4/27/2010) > causes several unexpected error dialogs related to acquiring kerberos > credentials. You need to be a bit more specific about the problem. I have installed KB090408 on Win7 64-bit, use KFW and OpenAFS with NetIdMgr v2 and do not experience problems when obtaining credentials using an API: credential cache. What credentials are you having trouble with and how are you obtaining them and with which tools? > If the error dialogs are ignored, OpenAFS seems to work (*very* brief > testing). The OpenAFS service, afsd_service.exe, does not perform any Kerberos operations and does not use KFW so I would expect this to work fine under any circumstances. Tools that are linked to KFW are netidmgr.exe's krb5 and afs credential providers, aklog.exe, integrated logon (afslogon.dll), and afscreds.exe. > I believe the problem will trigger an assert in a debug version of > OpenAFS but I haven=E2=80=99t proved that yet. (I got asserts while dea= ling with > another issue and it was only after the fact that I associated them wit= h > this situation.) Please provide a full report including what the error dialogs are and what they are saying along with where the asserts (if any) are being triggered (source file and line). > Suggestion: Don=E2=80=99t install KB980408 until more info is available= =2E If I was to make a guess the problem only occurs when the MSLSA: credential cache is used. The asserts occur in the cc_mslsa.c source file because Lsa handles are not properly closed. Jeffrey Altman --------------ms070003000703040004070801 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MjgyMzU1MjNaMCMGCSqGSIb3DQEJBDEWBBTGrs4o GwgmHR5wmLmnVMk3dUf69zBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAG2ZuOWw9fea0NxPhvzdoGqIr8kpdxIBn1Y2 vSSaz3aoDRM9lHpk/E94lS6Wdo065g30YoPydj8/8la5JeXKxwG5IIICUyBK/tN4MiE3/GI2 KR4p4TTtq8yx4WcHEAzwHV0APG320v0Cs6Oi+GRb6W7zxqITw4OO1bAT0eHkUaJ8jjTkiXcg Z+y6XqN4xXJkMpVMvkuMAIxnteQZaJ5wSJ9gF7N1xDjSnT20p3+TrHQAhXU4tKtYrFmIspFD LOxEfs5/f06zv8KLlVZTxiyqw05zvATyZVwXZDSHRhqWRPXncL2P4WmMjuMa8WpOHVUOg/+4 5quvtT9xBsNTsAXRxSUAAAAAAAA= --------------ms070003000703040004070801-- From kejzlar@civ.zcu.cz Thu Apr 29 11:44:27 2010 From: kejzlar@civ.zcu.cz (Lubos Kejzlar) Date: Thu, 29 Apr 2010 12:44:27 +0200 Subject: [OpenAFS] CFP: European AFS&Kerberoc Conference 2010 Message-ID: <1272537867.26580.14.camel@castor.civ.zcu.cz> Hi all, The European AFS & Kerberos Conference 2010 announces a first Call for Participation & Contribution. The European AFS & Kerberos Conference is a three day long conference (including half-day tutorial classes) for the novice and the experienced. The conference will take place in Pilsen, Czech Republic from September 13 to September 15, 2010. The conference is being hosted by Centre for Information Technology, University of West Bohemia. Come talk to your peers in general about: * Completed projects * Work in progress * Case studies * Best practices * Related research * Theories, new ideas * Updates on previous talks... or anything else of note involving AFS and/or Kerberos. Topics may include, but are not limited to: * AFS, Kerberos, LDAP and other related technologies * Performance tuning and benchmarking * Diagnostic, service monitoring and troubleshooting * Scalability and high availability issues * AFS/Kerberos & large scale, grid and cloud computing environments * Unique methods of AFS/Kerberos environment Backups * Web integration * Delegated administration and user management * Access control and related authorization services * Related tools for end-users, admins and programmers * Single Sign-On strategies * Cross cell/realm trust in real world * PKI and alternate security mechanism integration * AFS/Kerberos on the world globe: comparsion,interoperability,supplements, competitors and successors * Underlying OS, FS and hardware features * Work in progress, new features and future... We look forward to hearing about your talk! Especially welcome are presentations from Heimdal, Arla and simmilar related user groups. Please share your visions and experiences to help improve current products and grow our community. Submit your talk at http://afs2010.civ.zcu.cz/cfp.php or e-mail to afs2010@civ.zcu.cz. The Call for Participation will end Monday August 2, 2010. Acceptances will be made based upon quality, applicability, and fit with other submissions. Want be a sponsor? Sponsorship and contributor opportunities are available! For more info take a look at http://afs2010.civ.zcu.cz/sponsorship.php or send us an e-mail. The Workshop Organizers, http://afs2010.civ.zcu.cz/ afs2010@civ.zcu.cz From jjmpal@utu.fi Thu Apr 29 14:50:15 2010 From: jjmpal@utu.fi (Joonatan Palmu) Date: Thu, 29 Apr 2010 16:50:15 +0300 Subject: [OpenAFS] Vicepa partition over two terabytes Message-ID: <20100429165015.39bd71d4@neumann.tfy.utu.fi> Hello, I recently resized my /vicepa xfs-partition over two terabytes (2239707136k) which lead to vos partinfo message: "Free space on partition /vicepa: 149840764 K blocks out of total -2055260160". Can you tell me how critical this situation is and which would be the right way to fix it? I run openafs-fileserver version 1.4.7.dfsg1-6+lenny1 on Debian servers and there is a problem partition only on one machine. Best regards, Joonatan Palmu -------------------------------------- Joonatan Palmu, Sysadmin of Theoretical Physics Department of Physics and Astronomy, University of Turku FIN-20014 Turku, Finland phone: +358-2-3335964 -------------------------------------- From adeason@sinenomine.net Thu Apr 29 15:57:32 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Thu, 29 Apr 2010 09:57:32 -0500 Subject: [OpenAFS] Re: Vicepa partition over two terabytes References: <20100429165015.39bd71d4@neumann.tfy.utu.fi> Message-ID: <20100429095732.d835daad.adeason@sinenomine.net> On Thu, 29 Apr 2010 16:50:15 +0300 Joonatan Palmu wrote: > Hello, > > I recently resized my /vicepa xfs-partition over two terabytes > (2239707136k) which lead to vos partinfo message: "Free space on > partition /vicepa: 149840764 K blocks out of total -2055260160". Can > you tell me how critical this situation is and which would be the right > way to fix it? I run openafs-fileserver version 1.4.7.dfsg1-6+lenny1 on > Debian servers and there is a problem partition only on one machine. 1.4.8 will fix that; I don't think 1.4.7.dfsg1-6+lenny1 has the necessary patch. Debian backports has lenny packages for newer versions. Note that even with the newest versions of OpenAFS, you will still get similiar confusing output from 'fs listquota', but it is purely cosmetic. The wire protocol changes necessary to fix that have not yet been standardized. -- Andrew Deason adeason@sinenomine.net From stephan.wiesand@desy.de Thu Apr 29 17:54:30 2010 From: stephan.wiesand@desy.de (Stephan Wiesand) Date: Thu, 29 Apr 2010 18:54:30 +0200 Subject: [OpenAFS] is the 1.5.74 client supposed to work on RHEL6 beta? Message-ID: Quick question: is the 1.5.74 client known to cause a kernel panic on = the RHEL6 public beta (amd64) as soon as the module is loaded, or am I = doing something stupid? Thanks, Stephan --=20 Stephan Wiesand DESY -DV- Platanenenallee 6 15738 Zeuthen, Germany From marc.c.dionne@gmail.com Thu Apr 29 17:59:06 2010 From: marc.c.dionne@gmail.com (Marc Dionne) Date: Thu, 29 Apr 2010 12:59:06 -0400 Subject: [OpenAFS] is the 1.5.74 client supposed to work on RHEL6 beta? In-Reply-To: References: Message-ID: --00504502d2376be6230485630b3e Content-Type: text/plain; charset=ISO-8859-1 On Thu, Apr 29, 2010 at 12:54 PM, Stephan Wiesand wrote: > Quick question: is the 1.5.74 client known to cause a kernel panic on the > RHEL6 public beta (amd64) as soon as the module is loaded, or am I doing > something stupid? > > Thanks, > Stephan > Hi Stephan, That's a known bug, fixed in the current master by this commit: http://git.openafs.org/?p=openafs.git;a=commit;h=14195f0f48d52dd3a81c52c4a3bc2078857d0f86 Marc --00504502d2376be6230485630b3e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Thu, Apr 29, 2010 at 12:54 PM, Stephan Wiesan= d <stephan.= wiesand@desy.de> wrote:
Quick question: is the 1.5.74 client known to cause a kernel panic on the R= HEL6 public beta (amd64) as soon as the module is loaded, or am I doing som= ething stupid?

Thanks,
=A0 =A0 =A0 =A0Stephan

Hi Stephan,

That&#= 39;s a known bug, fixed in the current master by this commit:
http://git.openafs.org/?p=3Dopenafs.git;a=3Dcommit;h= =3D14195f0f48d52dd3a81c52c4a3bc2078857d0f86

Marc
--00504502d2376be6230485630b3e-- From sh@ltu.se Fri Apr 30 09:15:44 2010 From: sh@ltu.se (=?ISO-8859-1?Q?Staffan_H=E4m=E4l=E4?=) Date: Fri, 30 Apr 2010 10:15:44 +0200 Subject: [OpenAFS] AFS version of du Message-ID: <4BDA91B0.7010908@ltu.se> Is there a version of du that does not follow AFS mountpoints? If I try to do a 'du -sh *' in a directory that has some AFS mountpoints it inevitably fails after some time. It also takes a lot of time when it has to look through things in mounted volumes (e.g. the backup volume that I have mounted in many places). I've tried -P and -x to make it skip mount points, but it doesn't work (at least on CentOS 5 Linux). Staffan From mike@area9.dk Fri Apr 30 11:23:47 2010 From: mike@area9.dk (Mike Pliskin) Date: Fri, 30 Apr 2010 14:23:47 +0400 Subject: [OpenAFS] Getting started with OpenAFS Message-ID: --_000_C43B843E09660543A88BB3E08F2841210C6ED2001Cexch1mmltloca_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 RGVhciBhbGwsDQoNCkZpcnN0LCBsZXQgbWUgc3RhdGUgdGhhdCBJIGFtIGEgY29tcGxldGUgT3Bl bkFGUyBuZXdiaWUuIEnigJl2ZSBqdXN0IHN0YXJ0ZWQgcGxheWluZyB3aXRoIGl0IGFuZCBmb3Vu ZCBzb21lIG9ic3RhY2xlcyBJIGZhaWxlZCB0byByZXNvbHZlIG15c2VsZiBldmVuIGFmdGVyIHJl YWRpbmcgdGhlIGRvY3Mg4oCTIHRoZXJlZm9yZSBhc2tpbmcgZm9yIGhlbHAgaGVyZS4NCg0KIDEu ICB3aGljaCB2ZXJzaW9uIHRvIGluc3RhbGw/IEkgbmVlZCB3aW5kb3dzIGNsaWVudCBzdXBwb3J0 IHNvIEkgbmVlZCAxLjUgLSByaWdodD8gQnV0IGl0IGlzIG5vdCBzdGFibGUuLiBPciBpcyBpdD8g QW5kIGRvbid0IHNlZSBhbnkgcHJlLWJ1aWx0IHJwbXMgZm9yIGl0LCBzbyBjb21waWxpbmcgZnJv bSBzb3VyY2VzPw0KIDIuICB0cmllZCB0byBjb21waWxlIGFuZCBpdCB3b3JrZWQgYnV0IGl0IGNy ZWF0ZWQgYSBub24tIm1wIiBrZXJuZWwgbW9kdWxlIHdoaWxlIG15IGtlcm5lbCBuZWVkcyBhbiBt cCBvbmUgLSBob3cgdG8gZml4IHRoYXQ/DQogMy4gIGRvIEkgcmVhbGx5IG5lZWQgYSBuZXcgZnJl c2ggcGFydGl0aW9uIHRvIHN0YXJ0IHdpdGggb3IgSSBjYW4gcmUtdXNlIGFuIGV4aXN0aW5nIG9u ZSBhbmQganVzdCBtYWtlIGl0IGF2YWlsYWJsZSB2aWEgYWZzPw0KQWN0dWFsbHkgIzMgaXMgdGhl IG1vc3QgaW1wb3J0YW50IHNvIGxldCBtZSBleHBsYWluLiBJIGhhdmUgYSBzZXJ2ZXIgYWxyZWFk eSBhbmQgd2lsbGluZyB0byBtYWtlIGEgbGFyZ2UgcmVwb3NpdG9yeSBhdmFpbGFibGUgdmlhIGFm cy4gQXR0YWNoaW5nIGEgbmV3IGhhcmQgZHJpdmUgb3IgZXZlbiBjaGFuZ2luZyBwYXJ0aXRpb25z IGlzIGhhcmQgZm9yIG1lIGFzIHRoZSBzZXJ2ZXJzIGlzIHJlbW90ZSBmb3IgbWUgYW5kIGhhcyBw bGVudHkgb2YgZGF0YSBhbHJlYWR5LiBTbyBpcyB0aGVyZSBhbnkgd2F5IHRvIG1ha2UgYWZzIHVz ZSBqdXN0IGEgZm9sZGVyIHNvbWV3aGVyZT8gQW55IHdvcmthcm91bmRzPw0KDQpUaGFua3MgYSBs b3QgZm9yIHRoZSBpbmZvcm1hdGlvbiBpbiBhZHZhbmNlLA0KICBNaWtlIFBsaXNraW4NCg0K --_000_C43B843E09660543A88BB3E08F2841210C6ED2001Cexch1mmltloca_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50 PSJNaWNyb3NvZnQgV29yZCAxNCAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6V2luZ2RpbmdzOw0K CXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls eTpXaW5nZGluZ3M7DQoJcGFub3NlLTE6NSAwIDAgMCAwIDAgMCAwIDAgMDt9DQpAZm9udC1mYWNl DQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7 fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2IDQg MyA1IDQgNCAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5N c29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4w MDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt c2VyaWYiOw0KCW1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTO30NCmE6bGluaywgc3Bhbi5Nc29I eXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1k ZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93 ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29y YXRpb246dW5kZXJsaW5lO30NCnAuTXNvQWNldGF0ZSwgbGkuTXNvQWNldGF0ZSwgZGl2Lk1zb0Fj ZXRhdGUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiLQotC10LrR gdGCINCy0YvQvdC+0YHQutC4INCX0L3QsNC6IjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0 b206LjAwMDFwdDsNCglmb250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNh bnMtc2VyaWYiOw0KCW1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTO30NCnNwYW4uRW1haWxTdHls ZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLWNvbXBvc2U7DQoJZm9udC1mYW1pbHk6IkNh bGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNwYW4uYQ0KCXttc28t c3R5bGUtbmFtZToi0KLQtdC60YHRgiDQstGL0L3QvtGB0LrQuCDQl9C90LDQuiI7DQoJbXNvLXN0 eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiLQotC10LrRgdGCINCy0YvQvdC+0YHQ utC4IjsNCglmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7fQ0KLk1zb0NocERlZmF1 bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki LCJzYW5zLXNlcmlmIjsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQpAcGFnZSBXb3Jk U2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjIuMGNtIDQyLjVwdCAy LjBjbSAzLjBjbTt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi8q IExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGwwDQoJe21zby1saXN0LWlkOjEwOTIwNDMzMDU7 DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOjEzNjU3OTkxMjI7fQ0KQGxpc3QgbDA6bGV2ZWwxDQoJ e21zby1sZXZlbC10YWItc3RvcDozNi4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjps ZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDt9 DQpAbGlzdCBsMDpsZXZlbDINCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1z by1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOjcyLjBwdDsNCgltc28tbGV2ZWwt bnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCgltc28tYW5zaS1m b250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJbXNvLWJpZGkt Zm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7fQ0KQGxpc3QgbDA6bGV2ZWwzDQoJe21zby1s ZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxl dmVsLXRhYi1zdG9wOjEwOC4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0K CXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250 LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw0DQoJe21zby1sZXZlbC1udW1iZXIt Zm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9w OjE0NC4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50 Oi0xOC4wcHQ7DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5n ZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw1DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxl dDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjE4MC4wcHQ7DQoJ bXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJ bXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxp c3QgbDA6bGV2ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2 ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjIxNi4wcHQ7DQoJbXNvLWxldmVsLW51 bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJbXNvLWFuc2ktZm9u dC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw3 DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7 DQoJbXNvLWxldmVsLXRhYi1zdG9wOjI1Mi4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlv bjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBw dDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21zby1sZXZl bC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVs LXRhYi1zdG9wOjI4OC4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRl eHQtaW5kZW50Oi0xOC4wcHQ7DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZh bWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw5DQoJe21zby1sZXZlbC1udW1iZXItZm9y bWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjMy NC4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0x OC4wcHQ7DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5nZGlu Z3M7fQ0Kb2wNCgl7bWFyZ2luLWJvdHRvbTowY207fQ0KdWwNCgl7bWFyZ2luLWJvdHRvbTowY207 fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMg djpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lm IGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFw IHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlm XS0tPjwvaGVhZD48Ym9keSBsYW5nPVJVIGxpbms9Ymx1ZSB2bGluaz1wdXJwbGU+PGRpdiBjbGFz cz1Xb3JkU2VjdGlvbjE+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVM+RGVhciBh bGwsPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVO LVVTPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4g bGFuZz1FTi1VUz5GaXJzdCwgbGV0IG1lIHN0YXRlIHRoYXQgSSBhbSBhIGNvbXBsZXRlIE9wZW5B RlMgbmV3YmllLiBJ4oCZdmUganVzdCBzdGFydGVkIHBsYXlpbmcgd2l0aCBpdCBhbmQgZm91bmQg c29tZSBvYnN0YWNsZXMgSSBmYWlsZWQgdG8gcmVzb2x2ZSBteXNlbGYgZXZlbiBhZnRlciByZWFk aW5nIHRoZSBkb2NzIOKAkyB0aGVyZWZvcmUgYXNraW5nIGZvciBoZWxwIGhlcmUuPG86cD48L286 cD48L3NwYW4+PC9wPjxvbCBzdGFydD0xIHR5cGU9MT48bGkgY2xhc3M9TXNvTm9ybWFsIHN0eWxl PSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzttc28t bGlzdDpsMCBsZXZlbDEgbGZvMSc+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEy LjBwdDtmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO21zby1mYXJlYXN0LWxh bmd1YWdlOlJVJz53aGljaCB2ZXJzaW9uIHRvIGluc3RhbGw/IEkgbmVlZCB3aW5kb3dzIGNsaWVu dCBzdXBwb3J0IHNvIEkgbmVlZCAxLjUgLSByaWdodD8gQnV0IGl0IGlzIG5vdCBzdGFibGUuLiBP ciBpcyBpdD8gQW5kIGRvbid0IHNlZSBhbnkgcHJlLWJ1aWx0IHJwbXMgZm9yIGl0LCBzbyBjb21w aWxpbmcgZnJvbSBzb3VyY2VzPzxvOnA+PC9vOnA+PC9zcGFuPjwvbGk+PGxpIGNsYXNzPU1zb05v cm1hbCBzdHlsZT0nbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0 OmF1dG87bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzEnPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2Zv bnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjttc28t ZmFyZWFzdC1sYW5ndWFnZTpSVSc+dHJpZWQgdG8gY29tcGlsZSBhbmQgaXQgd29ya2VkIGJ1dCBp dCBjcmVhdGVkIGEgbm9uLSZxdW90O21wJnF1b3Q7IGtlcm5lbCBtb2R1bGUgd2hpbGUgbXkga2Vy bmVsIG5lZWRzIGFuIG1wIG9uZSAtIGhvdyB0byBmaXggdGhhdD88bzpwPjwvbzpwPjwvc3Bhbj48 L2xpPjxsaSBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z by1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21zby1saXN0OmwwIGxldmVsMSBsZm8xJz48c3BhbiBs YW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg Um9tYW4iLCJzZXJpZiI7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6UlUnPmRvIEkgcmVhbGx5IG5lZWQg YSBuZXcgZnJlc2ggcGFydGl0aW9uIHRvIHN0YXJ0IHdpdGggb3IgSSBjYW4gcmUtdXNlIGFuIGV4 aXN0aW5nIG9uZSBhbmQganVzdCBtYWtlIGl0IGF2YWlsYWJsZSB2aWEgYWZzPzxvOnA+PC9vOnA+ PC9zcGFuPjwvbGk+PC9vbD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1VUz5BY3R1 YWxseSAjMyBpcyB0aGUgbW9zdCBpbXBvcnRhbnQgc28gbGV0IG1lIGV4cGxhaW4uIEkgaGF2ZSBh IHNlcnZlciBhbHJlYWR5IGFuZCB3aWxsaW5nIHRvIG1ha2UgYSBsYXJnZSByZXBvc2l0b3J5IGF2 YWlsYWJsZSB2aWEgYWZzLiBBdHRhY2hpbmcgYSBuZXcgaGFyZCBkcml2ZSBvciBldmVuIGNoYW5n aW5nIHBhcnRpdGlvbnMgaXMgaGFyZCBmb3IgbWUgYXMgdGhlIHNlcnZlcnMgaXMgcmVtb3RlIGZv ciBtZSBhbmQgaGFzIHBsZW50eSBvZiBkYXRhIGFscmVhZHkuIFNvIGlzIHRoZXJlIGFueSB3YXkg dG8gbWFrZSBhZnMgdXNlIGp1c3QgYSBmb2xkZXIgc29tZXdoZXJlPyBBbnkgd29ya2Fyb3VuZHM/ PG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVT PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFu Zz1FTi1VUz5UaGFua3MgYSBsb3QgZm9yIHRoZSBpbmZvcm1hdGlvbiBpbiBhZHZhbmNlLDxvOnA+ PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1VUz7CoCBN aWtlIFBsaXNraW48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFu IGxhbmc9RU4tVVM+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjwvZGl2PjwvYm9keT48L2h0 bWw+ --_000_C43B843E09660543A88BB3E08F2841210C6ED2001Cexch1mmltloca_-- From l.schimmer@cgv.tugraz.at Fri Apr 30 11:41:25 2010 From: l.schimmer@cgv.tugraz.at (Lars Schimmer) Date: Fri, 30 Apr 2010 12:41:25 +0200 Subject: [OpenAFS] Getting started with OpenAFS In-Reply-To: References: Message-ID: <4BDAB3D5.70005@cgv.tugraz.at> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mike Pliskin wrote: > Dear all, >=20 > First, let me state that I am a complete OpenAFS newbie. I=E2=80=99ve j= ust started playing with it and found some obstacles I failed to resolve = myself even after reading the docs =E2=80=93 therefore asking for help he= re. >=20 > 1. which version to install? I need windows client support so I need = 1.5 - right? But it is not stable.. Or is it? And don't see any pre-built= rpms for it, so compiling from sources? As the protocol is compatible with rather old versions, you can mix client and server versions. BUT as security and bandwidth wise you should use a 1.4.12 or newer server on your *nix machines. For a client use 1.5.74 on windows and 1.4.12 on *nix machines. If you want to test and feel lucky, try the dev builds of 1.5.x on *nix and report bugs/errors/... > 2. tried to compile and it worked but it created a non-"mp" kernel mo= dule while my kernel needs an mp one - how to fix that? > 3. do I really need a new fresh partition to start with or I can re-u= se an existing one and just make it available via afs? > Actually #3 is the most important so let me explain. I have a server al= ready and willing to make a large repository available via afs. Attaching= a new hard drive or even changing partitions is hard for me as the serve= rs is remote for me and has plenty of data already. So is there any way t= o make afs use just a folder somewhere? Any workarounds? You need to spend a partition exclusive for OpenAFS server. OpenAFS does have its onw structure of files in the server-partitions (but it is not influenced by "false" files in those partitions). Which ends up in: you need to copy your files into the OpenAFS space after you have created the server and volumes and the logic fs-tree structure. You COULD share the openAFS fileserver-partitions via NFS or else and save extra data in those partitions (which are left alone by the OpenAFS fileserver) but that includes horrible security issues and is absolute NOT a way to go. More important about a new setup are some limits,IMHO the most important for new users are: - -only 1 ReadWrite copy of a volume - -no more than 64k files in a directory - -replica only on manual/script interaction - -only whole file locking on server - -experimental disconnected-mode But those are all fields which are worked on. > Thanks a lot for the information in advance, > Mike Pliskin MfG, Lars Schimmer - -- - ------------------------------------------------------------- TU Graz, Institut f=C3=BCr ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer@cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvas9UACgkQmWhuE0qbFyOeoQCfU3I895CFV8BpjpbeOCNLLFKJ E9QAn2tbqhiBWX+wf5d6OnxsN4AZ0NsO =3Dv20Z -----END PGP SIGNATURE----- From mike@area9.dk Fri Apr 30 12:07:40 2010 From: mike@area9.dk (Mike Pliskin) Date: Fri, 30 Apr 2010 15:07:40 +0400 Subject: [OpenAFS] Getting started with OpenAFS In-Reply-To: <4BDAB3D5.70005@cgv.tugraz.at> References: <4BDAB3D5.70005@cgv.tugraz.at> Message-ID: RGVhciBMYXJzLA0KDQpUaGFua3MgYSBsb3QgZm9yIHRoZSBkZXRhaWxlZCByZXNwb25zZSwgbGV0 IG1lIHNlZSB3aGF0IEkgY2FuIGRvIGluIHRlcm1zIG9mIHBhcnRpdGlvbnMuIEdlbmVyYWxseSB0 aGUgdGFzayBJIGFtIHRyeWluZyB0byBzb2x2ZSBpcyB0aGUgZm9sbG93aW5nOg0KIC0gdGhlcmUg aXMgYSAxMDAtZ2lnYWJ5dGUgY29sbGVjdGlvbiBvZiBsYXJnZSBmaWxlcyAoMTAgbWIgdG8gMSBn YikNCiAtIHRoZXJlIGFyZSBzZXZlcmFsIGdlb2dyYXBoaWNhbGx5IGRpc3RyaWJ1dGVkIHNpdGVz IHdpdGggcGVvcGxlIHRoYXQgbmVlZCBhY2Nlc3MNCiAtIGZpbGVzIGFyZSBvcmdhbml6ZWQgaW4g Zm9sZGVycywgYW5kIHRoZXJlIGlzIGEgZmFpcmx5IGdvb2QgYWRtaW5pc3RyYXRpdmUgc2VwYXJh dGlvbiBvbiB3aG8gbmVlZHMgd2hpY2ggZmlsZXMgLSBpLmUuIGNoYW5jZXMgb2YgcGVvcGxlIHdy aXRpbmcgdGhlIHNhbWUgZmlsZSBhdCBvbmNlIGFyZSBwcmV0dHkgbG93DQogLSBzcGVlZCBpcyBp bXBvcnRhbnQgYXMgd2VsbCBhcyBhIHdheSB0byBhY2Nlc3MgYW55IGZpbGUgZnJvbSBhbnl3aGVy ZSAoYnV0IG9rIHRvIGRlZ3JhZGUgc3BlZWQgaWYgcmVwbGljYXMgYXJlbid0IHN5bmNlZCB5ZXQp DQoNClNvIHRoZSBxdWVzdGlvbiBpcyAtIGRvIHlvdSB0aGluayBPcGVuQUZTIGlzIGEgcmlnaHQg dG9vbCBmb3IgdGhpcyBwcm9ibGVtPw0KDQpUaGFua3MsDQogIE1pa2UNCg0KLS0tLS1PcmlnaW5h bCBNZXNzYWdlLS0tLS0NCkZyb206IG9wZW5hZnMtaW5mby1hZG1pbkBvcGVuYWZzLm9yZyBbbWFp bHRvOm9wZW5hZnMtaW5mby1hZG1pbkBvcGVuYWZzLm9yZ10gT24gQmVoYWxmIE9mIExhcnMgU2No aW1tZXINClNlbnQ6IEZyaWRheSwgQXByaWwgMzAsIDIwMTAgMjo0MSBQTQ0KQ2M6IG9wZW5hZnMt aW5mb0BvcGVuYWZzLm9yZw0KU3ViamVjdDogUmU6IFtPcGVuQUZTXSBHZXR0aW5nIHN0YXJ0ZWQg d2l0aCBPcGVuQUZTDQoNCi0tLS0tQkVHSU4gUEdQIFNJR05FRCBNRVNTQUdFLS0tLS0NCkhhc2g6 IFNIQTENCg0KTWlrZSBQbGlza2luIHdyb3RlOg0KPiBEZWFyIGFsbCwNCj4gDQo+IEZpcnN0LCBs ZXQgbWUgc3RhdGUgdGhhdCBJIGFtIGEgY29tcGxldGUgT3BlbkFGUyBuZXdiaWUuIEnigJl2ZSBq dXN0IHN0YXJ0ZWQgcGxheWluZyB3aXRoIGl0IGFuZCBmb3VuZCBzb21lIG9ic3RhY2xlcyBJIGZh aWxlZCB0byByZXNvbHZlIG15c2VsZiBldmVuIGFmdGVyIHJlYWRpbmcgdGhlIGRvY3Mg4oCTIHRo ZXJlZm9yZSBhc2tpbmcgZm9yIGhlbHAgaGVyZS4NCj4gDQo+ICAxLiAgd2hpY2ggdmVyc2lvbiB0 byBpbnN0YWxsPyBJIG5lZWQgd2luZG93cyBjbGllbnQgc3VwcG9ydCBzbyBJIG5lZWQgMS41IC0g cmlnaHQ/IEJ1dCBpdCBpcyBub3Qgc3RhYmxlLi4gT3IgaXMgaXQ/IEFuZCBkb24ndCBzZWUgYW55 IHByZS1idWlsdCBycG1zIGZvciBpdCwgc28gY29tcGlsaW5nIGZyb20gc291cmNlcz8NCg0KQXMg dGhlIHByb3RvY29sIGlzIGNvbXBhdGlibGUgd2l0aCByYXRoZXIgb2xkIHZlcnNpb25zLCB5b3Ug Y2FuIG1peA0KY2xpZW50IGFuZCBzZXJ2ZXIgdmVyc2lvbnMuDQpCVVQgYXMgc2VjdXJpdHkgYW5k IGJhbmR3aWR0aCB3aXNlIHlvdSBzaG91bGQgdXNlIGEgMS40LjEyIG9yIG5ld2VyDQpzZXJ2ZXIg b24geW91ciAqbml4IG1hY2hpbmVzLg0KRm9yIGEgY2xpZW50IHVzZSAxLjUuNzQgb24gd2luZG93 cyBhbmQgMS40LjEyIG9uICpuaXggbWFjaGluZXMuDQpJZiB5b3Ugd2FudCB0byB0ZXN0IGFuZCBm ZWVsIGx1Y2t5LCB0cnkgdGhlIGRldiBidWlsZHMgb2YgMS41Lnggb24gKm5peA0KYW5kIHJlcG9y dCBidWdzL2Vycm9ycy8uLi4NCg0KPiAgMi4gIHRyaWVkIHRvIGNvbXBpbGUgYW5kIGl0IHdvcmtl ZCBidXQgaXQgY3JlYXRlZCBhIG5vbi0ibXAiIGtlcm5lbCBtb2R1bGUgd2hpbGUgbXkga2VybmVs IG5lZWRzIGFuIG1wIG9uZSAtIGhvdyB0byBmaXggdGhhdD8NCj4gIDMuICBkbyBJIHJlYWxseSBu ZWVkIGEgbmV3IGZyZXNoIHBhcnRpdGlvbiB0byBzdGFydCB3aXRoIG9yIEkgY2FuIHJlLXVzZSBh biBleGlzdGluZyBvbmUgYW5kIGp1c3QgbWFrZSBpdCBhdmFpbGFibGUgdmlhIGFmcz8NCj4gQWN0 dWFsbHkgIzMgaXMgdGhlIG1vc3QgaW1wb3J0YW50IHNvIGxldCBtZSBleHBsYWluLiBJIGhhdmUg YSBzZXJ2ZXIgYWxyZWFkeSBhbmQgd2lsbGluZyB0byBtYWtlIGEgbGFyZ2UgcmVwb3NpdG9yeSBh dmFpbGFibGUgdmlhIGFmcy4gQXR0YWNoaW5nIGEgbmV3IGhhcmQgZHJpdmUgb3IgZXZlbiBjaGFu Z2luZyBwYXJ0aXRpb25zIGlzIGhhcmQgZm9yIG1lIGFzIHRoZSBzZXJ2ZXJzIGlzIHJlbW90ZSBm b3IgbWUgYW5kIGhhcyBwbGVudHkgb2YgZGF0YSBhbHJlYWR5LiBTbyBpcyB0aGVyZSBhbnkgd2F5 IHRvIG1ha2UgYWZzIHVzZSBqdXN0IGEgZm9sZGVyIHNvbWV3aGVyZT8gQW55IHdvcmthcm91bmRz Pw0KDQpZb3UgbmVlZCB0byBzcGVuZCBhIHBhcnRpdGlvbiBleGNsdXNpdmUgZm9yIE9wZW5BRlMg c2VydmVyLiBPcGVuQUZTIGRvZXMNCmhhdmUgaXRzIG9udyBzdHJ1Y3R1cmUgb2YgZmlsZXMgaW4g dGhlIHNlcnZlci1wYXJ0aXRpb25zIChidXQgaXQgaXMgbm90DQppbmZsdWVuY2VkIGJ5ICJmYWxz ZSIgZmlsZXMgaW4gdGhvc2UgcGFydGl0aW9ucykuDQoNCldoaWNoIGVuZHMgdXAgaW46IHlvdSBu ZWVkIHRvIGNvcHkgeW91ciBmaWxlcyBpbnRvIHRoZSBPcGVuQUZTIHNwYWNlDQphZnRlciB5b3Ug aGF2ZSBjcmVhdGVkIHRoZSBzZXJ2ZXIgYW5kIHZvbHVtZXMgYW5kIHRoZSBsb2dpYyBmcy10cmVl DQpzdHJ1Y3R1cmUuDQpZb3UgQ09VTEQgc2hhcmUgdGhlIG9wZW5BRlMgZmlsZXNlcnZlci1wYXJ0 aXRpb25zIHZpYSBORlMgb3IgZWxzZSBhbmQNCnNhdmUgZXh0cmEgZGF0YSBpbiB0aG9zZSBwYXJ0 aXRpb25zICh3aGljaCBhcmUgbGVmdCBhbG9uZSBieSB0aGUgT3BlbkFGUw0KZmlsZXNlcnZlcikg YnV0IHRoYXQgaW5jbHVkZXMgaG9ycmlibGUgc2VjdXJpdHkgaXNzdWVzIGFuZCBpcyBhYnNvbHV0 ZQ0KTk9UIGEgd2F5IHRvIGdvLg0KDQpNb3JlIGltcG9ydGFudCBhYm91dCBhIG5ldyBzZXR1cCBh cmUgc29tZSBsaW1pdHMsSU1ITyB0aGUgbW9zdCBpbXBvcnRhbnQNCmZvciBuZXcgdXNlcnMgYXJl Og0KLSAtb25seSAxIFJlYWRXcml0ZSBjb3B5IG9mIGEgdm9sdW1lDQotIC1ubyBtb3JlIHRoYW4g NjRrIGZpbGVzIGluIGEgZGlyZWN0b3J5DQotIC1yZXBsaWNhIG9ubHkgb24gbWFudWFsL3Njcmlw dCBpbnRlcmFjdGlvbg0KLSAtb25seSB3aG9sZSBmaWxlIGxvY2tpbmcgb24gc2VydmVyDQotIC1l eHBlcmltZW50YWwgZGlzY29ubmVjdGVkLW1vZGUNCg0KQnV0IHRob3NlIGFyZSBhbGwgZmllbGRz IHdoaWNoIGFyZSB3b3JrZWQgb24uDQoNCg0KPiBUaGFua3MgYSBsb3QgZm9yIHRoZSBpbmZvcm1h dGlvbiBpbiBhZHZhbmNlLA0KPiAgIE1pa2UgUGxpc2tpbg0KDQpNZkcsDQpMYXJzIFNjaGltbWVy DQotIC0tDQotIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0NClRVIEdyYXosIEluc3RpdHV0IGbDvHIgQ29tcHV0ZXJHcmFwaGlrICYg V2lzc2Vuc1Zpc3VhbGlzaWVydW5nDQpUZWw6ICs0MyAzMTYgODczLTU0MDUgICAgICAgRS1NYWls OiBsLnNjaGltbWVyQGNndi50dWdyYXouYXQNCkZheDogKzQzIDMxNiA4NzMtNTQwMiAgICAgICBQ R1AtS2V5LUlEOiAweDRBOUIxNzIzDQotLS0tLUJFR0lOIFBHUCBTSUdOQVRVUkUtLS0tLQ0KVmVy c2lvbjogR251UEcgdjEuNC45IChHTlUvTGludXgpDQpDb21tZW50OiBVc2luZyBHbnVQRyB3aXRo IE1vemlsbGEgLSBodHRwOi8vZW5pZ21haWwubW96ZGV2Lm9yZw0KDQppRVlFQVJFQ0FBWUZBa3Zh czlVQUNna1FtV2h1RTBxYkZ5T2VvUUNmVTNJODk1Q0ZWOEJwanBiZU9DTkxMRktKDQpFOVFBbjJ0 YnFoaUJXWCt3ZjVkNk9ueHNONEFaME5zTw0KPXYyMFoNCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUt LS0tLQ0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCk9w ZW5BRlMtaW5mbyBtYWlsaW5nIGxpc3QNCk9wZW5BRlMtaW5mb0BvcGVuYWZzLm9yZw0KaHR0cHM6 Ly9saXN0cy5vcGVuYWZzLm9yZy9tYWlsbWFuL2xpc3RpbmZvL29wZW5hZnMtaW5mbw0K From jaltman@secure-endpoints.com Fri Apr 30 12:35:55 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Fri, 30 Apr 2010 07:35:55 -0400 Subject: [OpenAFS] Windows: Update KB980408 causes problems with kerberos credentials In-Reply-To: <4BD8CAEB.3070700@secure-endpoints.com> References: <1171E06FDB4D8341937880DCD831A0E2683ED523@34093-MBX-C15.mex07a.mlsrvr.com> <4BD8CAEB.3070700@secure-endpoints.com> Message-ID: <4BDAC09B.2010303@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms050309000508010009070508 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/28/2010 7:55 PM, Jeffrey Altman wrote: > On 4/28/2010 5:31 PM, Mickey Lane wrote: >> Windows 7 (32-bit) >> >> All updates prior to 4/27/2010 >> >> Kfw-3-2-2 >> >> Openafs-en_US-1-5-7400 >> >> =20 >> >> Installing Windows update KB980408 (published yesterday, 4/27/2010) >> causes several unexpected error dialogs related to acquiring kerberos >> credentials. >=20 > You need to be a bit more specific about the problem. I have installe= d > KB090408 on Win7 64-bit, use KFW and OpenAFS with NetIdMgr v2 and do > not experience problems when obtaining credentials using an API: > credential cache. Secure Endpoints staff has attempted to replicate this problem using 32-bit Win7, OpenAFS 1.5.74, and MIT distributed KFW 3.2.2. Attempts were made with the machine in standalone mode and joined to a domain. Both with domain and non-domain logon credentials. In no manner were we able to reproduce this issue or associate it with KB980408. Is there anyone else who has seen this issue? Is SNA able to provide any additional information that can be used to attempt a reproduction? Jeffrey Altman --------------ms050309000508010009070508 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MzAxMTM1NTVaMCMGCSqGSIb3DQEJBDEWBBRk8YNb 9J7v9rJ7U3ZuMyC3RAe2sTBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAM/QV64UugXmo5VxbXxJZqv3wUnss8IzxHzo 8POZ8FUXjbNudgbdt4Udo6ZCaPpdFCkO53XHVlKtnayUJ5w9fQLuCSHjtJEMKb7+y1DFIRbd 1/1CmxSAVmwEOAdMt93Vj+hpNSQNFbsb8sDBAC2DGk1wXnHZopwKcTuTWt6ESTtd1G7xPpw4 bcd5lWS/DHi1x/gKUZt0ullswin4Kn5OtWmwXQS0PppRN9npItC7MIsQzOw3Ff/38lZ3xxp/ JGto0GWgt5ktNK4NcRZnozVndCIZ5SenYu5CJHw2Z4dwLO5EfQbJEGji5/kyKpIqtfwTNHQw 0Z1mt7lwGhj8YRYjId4AAAAAAAA= --------------ms050309000508010009070508-- From mlane@sinenomine.net Fri Apr 30 13:15:01 2010 From: mlane@sinenomine.net (Mickey Lane) Date: Fri, 30 Apr 2010 07:15:01 -0500 Subject: [OpenAFS] Windows: Update KB980408 causes problems with kerberos credentials In-Reply-To: <4BDAC09B.2010303@secure-endpoints.com> References: <1171E06FDB4D8341937880DCD831A0E2683ED523@34093-MBX-C15.mex07a.mlsrvr.com> <4BD8CAEB.3070700@secure-endpoints.com> <4BDAC09B.2010303@secure-endpoints.com> Message-ID: <1171E06FDB4D8341937880DCD831A0E2683ED946@34093-MBX-C15.mex07a.mlsrvr.com> PiBTZWN1cmUgRW5kcG9pbnRzIHN0YWZmIGhhcyBhdHRlbXB0ZWQgdG8gcmVwbGljYXRlIHRoaXMg cHJvYmxlbSB1c2luZw0KPiAzMi1iaXQgV2luNywgT3BlbkFGUyAxLjUuNzQsIGFuZCBNSVQgZGlz dHJpYnV0ZWQgS0ZXIDMuMi4yLg0KPiANCj4gQXR0ZW1wdHMgd2VyZSBtYWRlIHdpdGggdGhlIG1h Y2hpbmUgaW4gc3RhbmRhbG9uZSBtb2RlIGFuZCBqb2luZWQgdG8gYQ0KPiBkb21haW4uICBCb3Ro IHdpdGggZG9tYWluIGFuZCBub24tZG9tYWluIGxvZ29uIGNyZWRlbnRpYWxzLg0KPiANCj4gSW4g bm8gbWFubmVyIHdlcmUgd2UgYWJsZSB0byByZXByb2R1Y2UgdGhpcyBpc3N1ZSBvciBhc3NvY2lh dGUgaXQNCj4gd2l0aCBLQjk4MDQwOC4NCj4gDQo+IA0KPiBJcyB0aGVyZSBhbnlvbmUgZWxzZSB3 aG8gaGFzIHNlZW4gdGhpcyBpc3N1ZT8NCj4gDQo+IElzIFNOQSBhYmxlIHRvIHByb3ZpZGUgYW55 IGFkZGl0aW9uYWwgaW5mb3JtYXRpb24gdGhhdCBjYW4gYmUgdXNlZCB0bw0KPiBhdHRlbXB0IGEg cmVwcm9kdWN0aW9uPw0KPiANCj4gSmVmZnJleSBBbHRtYW4NCj4gDQoNCkkgZ290IGFuIGUtbWFp bCBmcm9tIHNvbWVvbmUgd2hvIHNhaWQgc29tZW9uZSBlbHNlIG1pZ2h0IGhhdmUgc2Vlbg0KYSBw cm9ibGVtLiBJdCB3YXMgcHJldHR5IHZhZ3VlLg0KDQpJIHVzZWQgYW4gZXhpc3RpbmcgdmlydHVh bCBtYWNoaW5lIGluIEVTWGkgd2l0aCBub3RoaW5nIGluc3RhbGxlZCBvbg0KaXQgZXhjZXB0IEFG UyBhbmQgdGhlIE1pY3Jvc29mdCB1cGRhdGVzLiBJIHVzZWQgYSByZXN0b3JlIHBvaW50IHRvIGdl dA0KdGhlIG1hY2hpbmUgYmFjayB0byBpdHMgaW5zdGFsbCBzdGF0ZSBiZWZvcmUgcmVpbnN0YWxs aW5nIGFuZCB0cnlpbmcNCmFueXRoaW5nLg0KDQpJIGl0ZXJhdGl2ZWx5IGFkZGVkIHVwZGF0ZXMs IHJlYm9vdGVkIGFuZCBjaGVja2VkIEFGUy4gRXZlcnl0aGluZw0Kd29ya2VkIGZpbmUgdW50aWwg SSBhZGRlZCB0aGUgb25lIHVwZGF0ZSBLQjk4MDQwOC4NCg0KSSBzdXBwb3NlIGl0IGlzIHBvc3Np YmxlIHRoYXQgdGhlIHJlc3RvcmUgZGlkIG5vdCBnaXZlIG1lIHdoYXQgSQ0Kd2FzIHRoaW5raW5n IGl0IHdvdWxkIGdpdmUgbWUuIEkgd2lsbCByZXBlYXQgdGhlIHByb2Nlc3Mgd2l0aCBhDQpuZXds eSBpbnN0YWxsZWQgVk0gYW5kIGlmIEkgY2FuIHJlcHJvZHVjZSB0aGUgcHJvYmxlbSwgd2lsbCBy ZXBvcnQNCnRoZSBleGFjdCBzdGVwcyB1c2VkIGFuZCB0aGUgZXhhY3QgcmVzdWx0cyBvYnRhaW5l ZC4NCg0KTWlja2V5Lg0KDQo= From utoddl@email.unc.edu Fri Apr 30 13:32:34 2010 From: utoddl@email.unc.edu (Todd Lewis) Date: Fri, 30 Apr 2010 08:32:34 -0400 Subject: [OpenAFS] Getting started with OpenAFS In-Reply-To: References: <4BDAB3D5.70005@cgv.tugraz.at> Message-ID: <4BDACDE2.9010207@email.unc.edu> On 04/30/2010 07:07 AM, Mike Pliskin wrote: > - speed is important as well as a way to access any file from anywhere (but ok to degrade speed if replicas aren't synced yet) Your "replicas aren't synced yet" phrase indicates you're still under the assumption that so many people start with -- that the ro replicas are somehow automatically synced in near real time from the single rw volume. They are not. It's a manual process, or scripted, which pushes the volume image from the rw server to the ro replicas. Think of it more as a publishing operation. Everybody else is reading "today's edition" of some ro volume, while a few people are preparing the next edition. It could involve lots of changes across the volume that don't make sense separately, but only as a complete set of changes. Once you've got the contents of the rw volume consistent and the changes are complete, then you "release" that volume. The ro replicas get the changes in one go. If your users are geographically distributed, then the hope is that the ro volume they are using is on a server that is relatively close to them so the data has only to cross slow/long network links once -- during the release operation -- rather than as they read data. Writes/updates still have to get to the single rw volume across whatever network hops it takes. Note also that the path to a rw volume will differ from the path to its ro replicas (unless you've configure the client to use only rw volumes throughout your cell). Todd From mike@area9.dk Fri Apr 30 13:41:17 2010 From: mike@area9.dk (Mike Pliskin) Date: Fri, 30 Apr 2010 16:41:17 +0400 Subject: [OpenAFS] Getting started with OpenAFS In-Reply-To: <4BDACDE2.9010207@email.unc.edu> References: <4BDAB3D5.70005@cgv.tugraz.at> <4BDACDE2.9010207@email.unc.edu> Message-ID: VG9kZCwNCg0KVGhhbmtzIGEgbG90IGZvciBjbGFyaWZ5aW5nLCBJIGFtIHByb2JhYmx5IHN0YXJ0 aW5nIHRvIHVuZGVyc3RhbmQgd2hhdCBPcGVuQUZTIGNhbiBhY3R1YWxseSBkby4gV2VsbCBub3Qg c3VyZSBpZiBpdCBpcyB0aGUgc29sdXRpb24gdG8gbXkgcHJvYmxlbSB0aGVuLi4uIEFueSBjaGFu Y2VzIGZvciB0aGUgJ2F1dG9tYXRpYyByZXBsaWNhdGlvbicgb3Igc29tZXRoaW5nIGluIHRoZSBj b21pbmcgZnV0dXJlPyANCg0KTWlrZQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJv bTogVG9kZCBMZXdpcyBbbWFpbHRvOnV0b2RkbEBlbWFpbC51bmMuZWR1XSANClNlbnQ6IEZyaWRh eSwgQXByaWwgMzAsIDIwMTAgNDozMyBQTQ0KVG86IE1pa2UgUGxpc2tpbg0KQ2M6IG9wZW5hZnMt aW5mb0BvcGVuYWZzLm9yZw0KU3ViamVjdDogUmU6IFtPcGVuQUZTXSBHZXR0aW5nIHN0YXJ0ZWQg d2l0aCBPcGVuQUZTDQoNCg0KDQpPbiAwNC8zMC8yMDEwIDA3OjA3IEFNLCBNaWtlIFBsaXNraW4g d3JvdGU6DQo+IC0gc3BlZWQgaXMgaW1wb3J0YW50IGFzIHdlbGwgYXMgYSB3YXkgdG8gYWNjZXNz IGFueSBmaWxlIGZyb20gYW55d2hlcmUgDQo+IChidXQgb2sgdG8gZGVncmFkZSBzcGVlZCBpZiBy ZXBsaWNhcyBhcmVuJ3Qgc3luY2VkIHlldCkNCg0KWW91ciAicmVwbGljYXMgYXJlbid0IHN5bmNl ZCB5ZXQiIHBocmFzZSBpbmRpY2F0ZXMgeW91J3JlIHN0aWxsIHVuZGVyIHRoZSBhc3N1bXB0aW9u IHRoYXQgc28gbWFueSBwZW9wbGUgc3RhcnQgd2l0aCAtLSB0aGF0IHRoZSBybyByZXBsaWNhcyBh cmUgc29tZWhvdyBhdXRvbWF0aWNhbGx5IHN5bmNlZCBpbiBuZWFyIHJlYWwgdGltZSBmcm9tIHRo ZSBzaW5nbGUgcncgdm9sdW1lLiBUaGV5IGFyZSBub3QuIEl0J3MgYSBtYW51YWwgcHJvY2Vzcywg b3Igc2NyaXB0ZWQsIHdoaWNoIHB1c2hlcyB0aGUgdm9sdW1lIGltYWdlIGZyb20gdGhlIHJ3IHNl cnZlciB0byB0aGUgcm8gcmVwbGljYXMuDQoNClRoaW5rIG9mIGl0IG1vcmUgYXMgYSBwdWJsaXNo aW5nIG9wZXJhdGlvbi4gRXZlcnlib2R5IGVsc2UgaXMgcmVhZGluZyAidG9kYXkncyBlZGl0aW9u IiBvZiBzb21lIHJvIHZvbHVtZSwgd2hpbGUgYSBmZXcgcGVvcGxlIGFyZSBwcmVwYXJpbmcgdGhl IG5leHQgZWRpdGlvbi4gSXQgY291bGQgaW52b2x2ZSBsb3RzIG9mIGNoYW5nZXMgYWNyb3NzIHRo ZSB2b2x1bWUgdGhhdCBkb24ndCBtYWtlIHNlbnNlIHNlcGFyYXRlbHksIGJ1dCBvbmx5IGFzIGEg Y29tcGxldGUgc2V0IG9mIGNoYW5nZXMuIA0KT25jZSB5b3UndmUgZ290IHRoZSBjb250ZW50cyBv ZiB0aGUgcncgdm9sdW1lIGNvbnNpc3RlbnQgYW5kIHRoZSBjaGFuZ2VzIGFyZSBjb21wbGV0ZSwg dGhlbiB5b3UgInJlbGVhc2UiIHRoYXQgdm9sdW1lLiBUaGUgcm8gcmVwbGljYXMgZ2V0IHRoZSBj aGFuZ2VzIGluIG9uZSBnby4gSWYgeW91ciB1c2VycyBhcmUgZ2VvZ3JhcGhpY2FsbHkgZGlzdHJp YnV0ZWQsIHRoZW4gdGhlIGhvcGUgaXMgdGhhdCB0aGUgcm8gdm9sdW1lIHRoZXkgYXJlIHVzaW5n IGlzIG9uIGEgc2VydmVyIHRoYXQgaXMgcmVsYXRpdmVseSBjbG9zZSB0byB0aGVtIHNvIHRoZSBk YXRhIGhhcyBvbmx5IHRvIGNyb3NzIHNsb3cvbG9uZyBuZXR3b3JrIGxpbmtzIG9uY2UgLS0gZHVy aW5nIHRoZSByZWxlYXNlIG9wZXJhdGlvbiAtLSByYXRoZXIgdGhhbiBhcyB0aGV5IHJlYWQgZGF0 YS4NCg0KV3JpdGVzL3VwZGF0ZXMgc3RpbGwgaGF2ZSB0byBnZXQgdG8gdGhlIHNpbmdsZSBydyB2 b2x1bWUgYWNyb3NzIHdoYXRldmVyIG5ldHdvcmsgaG9wcyBpdCB0YWtlcy4NCg0KTm90ZSBhbHNv IHRoYXQgdGhlIHBhdGggdG8gYSBydyB2b2x1bWUgd2lsbCBkaWZmZXIgZnJvbSB0aGUgcGF0aCB0 byBpdHMgcm8gcmVwbGljYXMgKHVubGVzcyB5b3UndmUgY29uZmlndXJlIHRoZSBjbGllbnQgdG8g dXNlIG9ubHkgcncgdm9sdW1lcyB0aHJvdWdob3V0IHlvdXIgY2VsbCkuDQoNClRvZGQNCg== From l.schimmer@cgv.tugraz.at Fri Apr 30 13:42:30 2010 From: l.schimmer@cgv.tugraz.at (Lars Schimmer) Date: Fri, 30 Apr 2010 14:42:30 +0200 Subject: [OpenAFS] Getting started with OpenAFS In-Reply-To: References: <4BDAB3D5.70005@cgv.tugraz.at> Message-ID: <4BDAD036.5040601@cgv.tugraz.at> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mike Pliskin wrote: > Dear Lars, (please, TOFU) > Thanks a lot for the detailed response, let me see what I can do in ter= ms of partitions. Generally the task I am trying to solve is the followin= g: > - there is a 100-gigabyte collection of large files (10 mb to 1 gb) No problem, we have >5 TB of data in OpenAFS which includes files of 20GB so far. But for files >4GB you need at least a client version >1.4.0. > - there are several geographically distributed sites with people that = need access Readonly access or read/write access the same data or different directories? Thats a important point as only one read/write copy of a volume/directory can exist in one OpenAFS cell. > - files are organized in folders, and there is a fairly good administr= ative separation on who needs which files - i.e. chances of people writin= g the same file at once are pretty low You can set ACLs on directories in OpenAFS - fairly simple and works. > - speed is important as well as a way to access any file from anywhere= (but ok to degrade speed if replicas aren't synced yet) Readonly replica could be done via night and clients can access a local readonly replica for faster access (if a local fileserver exists). The client cache could do a difference, to. Needs to be big enough (for bigger files) and persistant over reboots. If a file could be served out of client local cache and not from (slow) server overseas fine. > So the question is - do you think OpenAFS is a right tool for this prob= lem? So far yes. BUT the read/write and readonly point is still open. You could setup one volume per directory and mount that directories after the rules of rw access into the filetree. But if you have e.g. a /afs/test/useraa/files/ firectory for user aa on a fileserver in dk and a user bb in the US needs to write to that directory, it needs to access that fileserver the rw volume is on. If user bb in the us need only to access a readonly copy of that directory, copy that volume/directory to the us fileserver (over night) and the user bb could access it readonly from the us local fileserver. Hope it is made clear now why it needs some think-over with a multi-homing site. But it is absolute possible and could work great. > Thanks, > Mike > MfG, Lars Schimmer - -- - ------------------------------------------------------------- TU Graz, Institut f=C3=BCr ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer@cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkva0DYACgkQmWhuE0qbFyMBEACggL2GZC31kpZ5u8BIoNFUep+n iB0Anixf9lxO3b/R+QktJUUH61GW01Kn =3D6Yr5 -----END PGP SIGNATURE----- From jaltman@secure-endpoints.com Fri Apr 30 13:57:56 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Fri, 30 Apr 2010 08:57:56 -0400 Subject: [OpenAFS] Windows: Update KB980408 causes problems with kerberos credentials In-Reply-To: <1171E06FDB4D8341937880DCD831A0E2683ED946@34093-MBX-C15.mex07a.mlsrvr.com> References: <1171E06FDB4D8341937880DCD831A0E2683ED523@34093-MBX-C15.mex07a.mlsrvr.com> <4BD8CAEB.3070700@secure-endpoints.com> <4BDAC09B.2010303@secure-endpoints.com> <1171E06FDB4D8341937880DCD831A0E2683ED946@34093-MBX-C15.mex07a.mlsrvr.com> Message-ID: <4BDAD3D4.7060306@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms010506000700030603060400 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/30/2010 8:15 AM, Mickey Lane wrote: >> Secure Endpoints staff has attempted to replicate this problem using >> 32-bit Win7, OpenAFS 1.5.74, and MIT distributed KFW 3.2.2. >> >> Attempts were made with the machine in standalone mode and joined to a= >> domain. Both with domain and non-domain logon credentials. >> >> In no manner were we able to reproduce this issue or associate it >> with KB980408. >> >> >> Is there anyone else who has seen this issue? >> >> Is SNA able to provide any additional information that can be used to >> attempt a reproduction? >> >> Jeffrey Altman >> >=20 > I got an e-mail from someone who said someone else might have seen > a problem. It was pretty vague. >=20 > I used an existing virtual machine in ESXi with nothing installed on > it except AFS and the Microsoft updates. I used a restore point to get > the machine back to its install state before reinstalling and trying > anything. >=20 > I iteratively added updates, rebooted and checked AFS. Everything > worked fine until I added the one update KB980408. >=20 > I suppose it is possible that the restore did not give me what I > was thinking it would give me. I will repeat the process with a > newly installed VM and if I can reproduce the problem, will report > the exact steps used and the exact results obtained. >=20 > Mickey. A detailed report of exactly what the problem is would be helpful in attempting to reproduce it. Based on your initial e-mail there is not very much to go other than something you are doing is failing. However, you have not explained either the "what" you are doing is or the "failure" condition that has occurred other than to say that a dialog box is produced. Please include the details requested in my initial reply in any response.= Jeffrey Altman --------------ms010506000700030603060400 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MzAxMjU3NTZaMCMGCSqGSIb3DQEJBDEWBBRBwPTL b7Vr8GzNH0sSLZwkfwSQ+jBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAM2MYH7Epnur98AmGXnoIIl/iIG2MDh0pswB nz7+HoAZf39n0V5ebBHleKb0FBQlXIgjxVCxSBWH4vdJZPXNJSq/qLxQiFO8hPntARHMacYr GCtl5VKeSDNylTetGXKUd/JBshp7giRWjOb5M7rjtPjTPC8YtydzzJK0D7gFAyKpuGelxTfe zxCilEwijho8V2+GFEecxiuJ264QaaP/79VawmebHqoYT9r1zDVLAj7fbo+qdi9PbmxzH6r1 MP/LlfzUQ0aVV3TAVX5Vt/ykfY4WeMdSMzMRR7kToe9NVFqjEIgr0uRuDddMYBGk1l0alarh aHAkeA42n66tej7F09EAAAAAAAA= --------------ms010506000700030603060400-- From jaltman@secure-endpoints.com Fri Apr 30 14:01:00 2010 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Fri, 30 Apr 2010 09:01:00 -0400 Subject: [OpenAFS] Getting started with OpenAFS In-Reply-To: References: <4BDAB3D5.70005@cgv.tugraz.at> <4BDACDE2.9010207@email.unc.edu> Message-ID: <4BDAD48C.3090305@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms030401060904020606000202 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/30/2010 8:41 AM, Mike Pliskin wrote: > Todd, >=20 > Thanks a lot for clarifying, I am probably starting to understand what = OpenAFS can actually do. Well not sure if it is the solution to my proble= m then... Any chances for the 'automatic replication' or something in the= coming future?=20 >=20 > Mike Adding support for read/write replication is on the road map but it will be a couple of years at least before it is ready for production use. http://www.openafs.org/roadmap.html Jeffrey Altman --------------ms030401060904020606000202 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC AxcwggKAoAMCAQICEAMF9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoX DTEwMDgyODA0MDExOVowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQDZNscYIvF6xzGSAfa/QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6 y0zlFqSbiFwgNM8m69K6m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWL kNdaXQKk6EZVW9pfV2A4Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iE jVhVzPobuZzwD2tuepY/bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1Zp Yh8Fx+9cqsG8O4nqo26SVfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcG A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN BgkqhkiG9w0BAQUFAAOBgQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOK ifHDyLZQC4qSsCUfP7vdwAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/Z cW3icObO9FIZCSmgFMt2Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAxcwggKAoAMCAQICEAMF 9RTCGOz151fTpHLih+cwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDgyODA0MDExOVoXDTEwMDgyODA0MDExOVow czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZNscYIvF6xzGSAfa/ QUIqiElyn0EUxL2b86eKiYqe91bj0gLr/MJoErLnb+OmokxqSAH6y0zlFqSbiFwgNM8m69K6 m/6YO+x3+5zBc+u6snwTWMEWygnhx3rQ/lMhoQOgArraL+/k9aWLkNdaXQKk6EZVW9pfV2A4 Lk4DoZGFjY8tJRWWDLlFkYnxDuIEpLYwJpwakv3QHOaq/G8KW0iEjVhVzPobuZzwD2tuepY/ bsClwqxz/gfAEpUvAn/lYTqnoT7RYljZlCIdbrgcG/HSYMxAy1ZpYh8Fx+9cqsG8O4nqo26S VfYZvrYhh8m6OqW8Vakdt7vBLCTa/QhIdJ4hAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOB gQBvbvJNXUJ4atv1CExIe0J38jZqoEUTttkXOfCDT9e3mSmVboOKifHDyLZQC4qSsCUfP7vd wAXjKtjak22HbfX2sEKCUgtnOkxRqXMM2V/NW/ESNVQZF0TO7L/ZcW3icObO9FIZCSmgFMt2 Al7VPfMQmaJNlqu9SLmXSwbRFJ5b4zCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV +065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/ p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8 MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/ TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNxMIID bQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ AwX1FMIY7PXnV9OkcuKH5zAJBgUrDgMCGgUAoIIB0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDA0MzAxMzAxMDBaMCMGCSqGSIb3DQEJBDEWBBQ0oH7Y SRYuA4sTyv3urdt9UM2QiDBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBAhADBfUUwhjs9edX06Ry4ofnMIGHBgsqhkiG9w0BCRACCzF4oHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhADBfUUwhjs 9edX06Ry4ofnMA0GCSqGSIb3DQEBAQUABIIBAAPRGaCT9CuEveblapN/z3ahe/7rYPTFpNP0 Q1KQZw/AH4VgBb/Grcv6eeiBYjqF7q/rbjsgMsEf89qlHXpWMk6oXVWl5BjKftnMro8GDuZp h2rkXGImlaz+rt7M1HhYOdaC/B84X0WeX4JjWI5Lp910EmUhJorFBFdn7ANNYGQG1Dz6ouW5 s5dU8ot2qvzlPVfFo0n3whkm0RysVon8BZvEKSfc0httx1WdWy/pLao1WoILNmS5W8u52OEn yzeNKzx3qBBkhcKO3B6IkBSK99rMX4LJ0U3pPlog57rQkuJVRf2jAPYYLzrR3N3S0BiJ6JTb zH8ZolEmyNgNodIwTtMAAAAAAAA= --------------ms030401060904020606000202-- From mike@area9.dk Fri Apr 30 14:49:16 2010 From: mike@area9.dk (Mike Pliskin) Date: Fri, 30 Apr 2010 17:49:16 +0400 Subject: [OpenAFS] Getting started with OpenAFS In-Reply-To: <4BDAD036.5040601@cgv.tugraz.at> References: <4BDAB3D5.70005@cgv.tugraz.at> <4BDAD036.5040601@cgv.tugraz.at> Message-ID: T2sgdGhhbmtzIGEgdG9uIGZvciBleHBsYWluaW5nLCB0aGUgb25seSBwb2ludCBsZWZ0IGlzIHJl YWQtd3JpdGUgYW5kIHJlYWQtb25seSBhbmQgaG93IHRvIHNlcGFyYXRlIHRob3NlLiBTbyBmYXIg aXQgc291bmRzIGxpa2UgSSB3aWxsIG5lZWQgdG8gaGF2ZSBhIHNldHVwIGxpa2UNCi9hZnMvcHVi bGljL2RhdGExDQovYWZzL3B1YmxpYy9kYXRhMg0KL2Fmcy9wdWJsaWMvZGF0YTMNCi9hZnMvdXNl cjEvZGF0YTENCi9hZnMvdXNlcjIvZGF0YTIgZXRjDQoNCldoZXJlIC9hZnMvcHVibGljIGlzIGEg cmVhZC1vbmx5IHJlcGxpY2F0ZWQgJ21hc3RlcicgY29weSBhbmQgL2Fmcy91c2VyeCBpcyB1c2Vy cyBpbmRpdmlkdWFsIHJlYWQtd3JpdGUgZm9sZGVycywgYW5kIC9wdWJsaWMgbmVlZHMgdG8gYmUg c3luY2VkICJtYW51YWxseSIuIElzIHRoaXMgcmlnaHQgLSBpLmUuIGlzIHRoaXMgdGhlIGtpbmQg b2Ygc2VtYW50aWNzIHRoYXQgT3BlbkFGUyBpbXBsaWVzPw0KDQpNaWtlDQoNCi0tLS0tT3JpZ2lu YWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBvcGVuYWZzLWluZm8tYWRtaW5Ab3BlbmFmcy5vcmcgW21h aWx0bzpvcGVuYWZzLWluZm8tYWRtaW5Ab3BlbmFmcy5vcmddIE9uIEJlaGFsZiBPZiBMYXJzIFNj aGltbWVyDQpTZW50OiBGcmlkYXksIEFwcmlsIDMwLCAyMDEwIDQ6NDMgUE0NCkNjOiBvcGVuYWZz LWluZm9Ab3BlbmFmcy5vcmcNClN1YmplY3Q6IFJlOiBbT3BlbkFGU10gR2V0dGluZyBzdGFydGVk IHdpdGggT3BlbkFGUw0KDQotLS0tLUJFR0lOIFBHUCBTSUdORUQgTUVTU0FHRS0tLS0tDQpIYXNo OiBTSEExDQoNCk1pa2UgUGxpc2tpbiB3cm90ZToNCj4gRGVhciBMYXJzLA0KDQoocGxlYXNlLCBU T0ZVKQ0KDQo+IFRoYW5rcyBhIGxvdCBmb3IgdGhlIGRldGFpbGVkIHJlc3BvbnNlLCBsZXQgbWUg c2VlIHdoYXQgSSBjYW4gZG8gaW4gdGVybXMgb2YgcGFydGl0aW9ucy4gR2VuZXJhbGx5IHRoZSB0 YXNrIEkgYW0gdHJ5aW5nIHRvIHNvbHZlIGlzIHRoZSBmb2xsb3dpbmc6DQo+ICAtIHRoZXJlIGlz IGEgMTAwLWdpZ2FieXRlIGNvbGxlY3Rpb24gb2YgbGFyZ2UgZmlsZXMgKDEwIG1iIHRvIDEgZ2Ip DQoNCk5vIHByb2JsZW0sIHdlIGhhdmUgPjUgVEIgb2YgZGF0YSBpbiBPcGVuQUZTIHdoaWNoIGlu Y2x1ZGVzIGZpbGVzIG9mIDIwR0Igc28gZmFyLiBCdXQgZm9yIGZpbGVzID40R0IgeW91IG5lZWQg YXQgbGVhc3QgYSBjbGllbnQgdmVyc2lvbiA+MS40LjAuDQoNCj4gIC0gdGhlcmUgYXJlIHNldmVy YWwgZ2VvZ3JhcGhpY2FsbHkgZGlzdHJpYnV0ZWQgc2l0ZXMgd2l0aCBwZW9wbGUgdGhhdCANCj4g bmVlZCBhY2Nlc3MNCg0KUmVhZG9ubHkgYWNjZXNzIG9yIHJlYWQvd3JpdGUgYWNjZXNzIHRoZSBz YW1lIGRhdGEgb3IgZGlmZmVyZW50IGRpcmVjdG9yaWVzPyBUaGF0cyBhIGltcG9ydGFudCBwb2lu dCBhcyBvbmx5IG9uZSByZWFkL3dyaXRlIGNvcHkgb2YgYSB2b2x1bWUvZGlyZWN0b3J5IGNhbiBl eGlzdCBpbiBvbmUgT3BlbkFGUyBjZWxsLg0KDQo+ICAtIGZpbGVzIGFyZSBvcmdhbml6ZWQgaW4g Zm9sZGVycywgYW5kIHRoZXJlIGlzIGEgZmFpcmx5IGdvb2QgDQo+IGFkbWluaXN0cmF0aXZlIHNl cGFyYXRpb24gb24gd2hvIG5lZWRzIHdoaWNoIGZpbGVzIC0gaS5lLiBjaGFuY2VzIG9mIA0KPiBw ZW9wbGUgd3JpdGluZyB0aGUgc2FtZSBmaWxlIGF0IG9uY2UgYXJlIHByZXR0eSBsb3cNCg0KWW91 IGNhbiBzZXQgQUNMcyBvbiBkaXJlY3RvcmllcyBpbiBPcGVuQUZTIC0gZmFpcmx5IHNpbXBsZSBh bmQgd29ya3MuDQoNCj4gIC0gc3BlZWQgaXMgaW1wb3J0YW50IGFzIHdlbGwgYXMgYSB3YXkgdG8g YWNjZXNzIGFueSBmaWxlIGZyb20gDQo+IGFueXdoZXJlIChidXQgb2sgdG8gZGVncmFkZSBzcGVl ZCBpZiByZXBsaWNhcyBhcmVuJ3Qgc3luY2VkIHlldCkNCg0KUmVhZG9ubHkgcmVwbGljYSBjb3Vs ZCBiZSBkb25lIHZpYSBuaWdodCBhbmQgY2xpZW50cyBjYW4gYWNjZXNzIGEgbG9jYWwgcmVhZG9u bHkgcmVwbGljYSBmb3IgZmFzdGVyIGFjY2VzcyAoaWYgYSBsb2NhbCBmaWxlc2VydmVyIGV4aXN0 cykuDQpUaGUgY2xpZW50IGNhY2hlIGNvdWxkIGRvIGEgZGlmZmVyZW5jZSwgdG8uIE5lZWRzIHRv IGJlIGJpZyBlbm91Z2ggKGZvciBiaWdnZXIgZmlsZXMpIGFuZCBwZXJzaXN0YW50IG92ZXIgcmVi b290cy4gSWYgYSBmaWxlIGNvdWxkIGJlIHNlcnZlZCBvdXQgb2YgY2xpZW50IGxvY2FsIGNhY2hl IGFuZCBub3QgZnJvbSAoc2xvdykgc2VydmVyIG92ZXJzZWFzIGZpbmUuDQoNCg0KPiBTbyB0aGUg cXVlc3Rpb24gaXMgLSBkbyB5b3UgdGhpbmsgT3BlbkFGUyBpcyBhIHJpZ2h0IHRvb2wgZm9yIHRo aXMgcHJvYmxlbT8NCg0KU28gZmFyIHllcy4gQlVUIHRoZSByZWFkL3dyaXRlIGFuZCByZWFkb25s eSBwb2ludCBpcyBzdGlsbCBvcGVuLg0KWW91IGNvdWxkIHNldHVwIG9uZSB2b2x1bWUgcGVyIGRp cmVjdG9yeSBhbmQgbW91bnQgdGhhdCBkaXJlY3RvcmllcyBhZnRlciB0aGUgcnVsZXMgb2Ygcncg YWNjZXNzIGludG8gdGhlIGZpbGV0cmVlLg0KQnV0IGlmIHlvdSBoYXZlIGUuZy4gYSAvYWZzL3Rl c3QvdXNlcmFhL2ZpbGVzLyBmaXJlY3RvcnkgZm9yIHVzZXIgYWEgb24gYSBmaWxlc2VydmVyIGlu IGRrIGFuZCBhIHVzZXIgYmIgaW4gdGhlIFVTIG5lZWRzIHRvIHdyaXRlIHRvIHRoYXQgZGlyZWN0 b3J5LCBpdCBuZWVkcyB0byBhY2Nlc3MgdGhhdCBmaWxlc2VydmVyIHRoZSBydyB2b2x1bWUgaXMg b24uDQpJZiB1c2VyIGJiIGluIHRoZSB1cyBuZWVkIG9ubHkgdG8gYWNjZXNzIGEgcmVhZG9ubHkg Y29weSBvZiB0aGF0IGRpcmVjdG9yeSwgY29weSB0aGF0IHZvbHVtZS9kaXJlY3RvcnkgdG8gdGhl IHVzIGZpbGVzZXJ2ZXIgKG92ZXIgbmlnaHQpIGFuZCB0aGUgdXNlciBiYiBjb3VsZCBhY2Nlc3Mg aXQgcmVhZG9ubHkgZnJvbSB0aGUgdXMgbG9jYWwgZmlsZXNlcnZlci4NCg0KSG9wZSBpdCBpcyBt YWRlIGNsZWFyIG5vdyB3aHkgaXQgbmVlZHMgc29tZSB0aGluay1vdmVyIHdpdGggYSBtdWx0aS1o b21pbmcgc2l0ZS4gQnV0IGl0IGlzIGFic29sdXRlIHBvc3NpYmxlIGFuZCBjb3VsZCB3b3JrIGdy ZWF0Lg0KDQo+IFRoYW5rcywNCj4gICBNaWtlDQo+DQoNCk1mRywNCkxhcnMgU2NoaW1tZXINCi0g LS0NCi0gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLQ0KVFUgR3JheiwgSW5zdGl0dXQgZsO8ciBDb21wdXRlckdyYXBoaWsgJiBXaXNz ZW5zVmlzdWFsaXNpZXJ1bmcNClRlbDogKzQzIDMxNiA4NzMtNTQwNSAgICAgICBFLU1haWw6IGwu c2NoaW1tZXJAY2d2LnR1Z3Jhei5hdA0KRmF4OiArNDMgMzE2IDg3My01NDAyICAgICAgIFBHUC1L ZXktSUQ6IDB4NEE5QjE3MjMNCi0tLS0tQkVHSU4gUEdQIFNJR05BVFVSRS0tLS0tDQpWZXJzaW9u OiBHbnVQRyB2MS40LjkgKEdOVS9MaW51eCkNCkNvbW1lbnQ6IFVzaW5nIEdudVBHIHdpdGggTW96 aWxsYSAtIGh0dHA6Ly9lbmlnbWFpbC5tb3pkZXYub3JnDQoNCmlFWUVBUkVDQUFZRkFrdmEwRFlB Q2drUW1XaHVFMHFiRnlNQkVBQ2dnTDJHWkMzMWtwWjV1OEJJb05GVWVwK24NCmlCMEFuaXhmOWx4 TzNiL1IrUWt0SlVVSDYxR1cwMUtuDQo9NllyNQ0KLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0t DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KT3BlbkFG Uy1pbmZvIG1haWxpbmcgbGlzdA0KT3BlbkFGUy1pbmZvQG9wZW5hZnMub3JnDQpodHRwczovL2xp c3RzLm9wZW5hZnMub3JnL21haWxtYW4vbGlzdGluZm8vb3BlbmFmcy1pbmZvDQo= From mike@area9.dk Fri Apr 30 14:50:02 2010 From: mike@area9.dk (Mike Pliskin) Date: Fri, 30 Apr 2010 17:50:02 +0400 Subject: [OpenAFS] Getting started with OpenAFS In-Reply-To: <4BDAD48C.3090305@secure-endpoints.com> References: <4BDAB3D5.70005@cgv.tugraz.at> <4BDACDE2.9010207@email.unc.edu> <4BDAD48C.3090305@secure-endpoints.com> Message-ID: VGhhbmtzIEplZmZyZXksIEkgc2VlIG5vdyAtIHdlbGwgaXQnZCBiZXR0ZXIgaGFwcGVuIHNvb25l ciB0aGFuIGxhdGVyIGJ1dCBvZiBjb3Vyc2UgdGhpcyBhcHBsaWVzIHRvIGV2ZXJ5IG90aGVyIGZl YXR1cmUgSSBndWVzcyA6KQ0KDQpNaWtlDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpG cm9tOiBvcGVuYWZzLWluZm8tYWRtaW5Ab3BlbmFmcy5vcmcgW21haWx0bzpvcGVuYWZzLWluZm8t YWRtaW5Ab3BlbmFmcy5vcmddIE9uIEJlaGFsZiBPZiBKZWZmcmV5IEFsdG1hbg0KU2VudDogRnJp ZGF5LCBBcHJpbCAzMCwgMjAxMCA1OjAxIFBNDQpUbzogb3BlbmFmcy1pbmZvQG9wZW5hZnMub3Jn DQpTdWJqZWN0OiBSZTogW09wZW5BRlNdIEdldHRpbmcgc3RhcnRlZCB3aXRoIE9wZW5BRlMNCg0K T24gNC8zMC8yMDEwIDg6NDEgQU0sIE1pa2UgUGxpc2tpbiB3cm90ZToNCj4gVG9kZCwNCj4gDQo+ IFRoYW5rcyBhIGxvdCBmb3IgY2xhcmlmeWluZywgSSBhbSBwcm9iYWJseSBzdGFydGluZyB0byB1 bmRlcnN0YW5kIHdoYXQgT3BlbkFGUyBjYW4gYWN0dWFsbHkgZG8uIFdlbGwgbm90IHN1cmUgaWYg aXQgaXMgdGhlIHNvbHV0aW9uIHRvIG15IHByb2JsZW0gdGhlbi4uLiBBbnkgY2hhbmNlcyBmb3Ig dGhlICdhdXRvbWF0aWMgcmVwbGljYXRpb24nIG9yIHNvbWV0aGluZyBpbiB0aGUgY29taW5nIGZ1 dHVyZT8gDQo+IA0KPiBNaWtlDQoNCkFkZGluZyBzdXBwb3J0IGZvciByZWFkL3dyaXRlIHJlcGxp Y2F0aW9uIGlzIG9uIHRoZSByb2FkIG1hcCBidXQgaXQgd2lsbA0KYmUgYSBjb3VwbGUgb2YgeWVh cnMgYXQgbGVhc3QgYmVmb3JlIGl0IGlzIHJlYWR5IGZvciBwcm9kdWN0aW9uIHVzZS4NCg0KICBo dHRwOi8vd3d3Lm9wZW5hZnMub3JnL3JvYWRtYXAuaHRtbA0KDQpKZWZmcmV5IEFsdG1hbg0KDQoN Cg== From scs@umich.edu Fri Apr 30 14:56:25 2010 From: scs@umich.edu (Steve Simmons) Date: Fri, 30 Apr 2010 09:56:25 -0400 Subject: [OpenAFS] AFS version of du In-Reply-To: <4BDA91B0.7010908@ltu.se> References: <4BDA91B0.7010908@ltu.se> Message-ID: <06563EB3-AA97-4C96-9A2E-450197B518B9@umich.edu> On Apr 30, 2010, at 4:15 AM, Staffan H=E4m=E4l=E4 wrote: > Is there a version of du that does not follow AFS mountpoints? >=20 > If I try to do a 'du -sh *' in a directory that has some AFS = mountpoints it inevitably fails after some time. It also takes a lot of = time when it has to look through things in mounted volumes (e.g. the = backup volume that I have mounted in many places). >=20 > I've tried -P and -x to make it skip mount points, but it doesn't work = (at least on CentOS 5 Linux). The short answer is that it might be coming coming, but it's going to be = a while. Here's the detailed scoop as I understand it, based on some old = mail exchanges I had with the findutils maintainer James Youngman and = discussion on the findutils mailing list. Any utility that recurses through the file system (du, find, ls, others) = has the same set of core problems - things to include or exclude, cross = or don't cross mount points, etc, etc. This is immensely complicated by = the breadth of things that can and do comprise mount points. Is a NFS = mount a mount point? An AFS? Samba shares? Repeat question for every = conceivable file system, and it becomes hellacious. Literally years ago, the developers of the GNU findutils suite decided = to bite this bullet with a common library. Their goal was to have a = function which could recurse through directories. That function would = have all the smarts described above. It would then become the core of = du, ls, etc when those things had to do recursive searches. They also set some ambitious goals. As was communicated to me at the = time (I was gently whining about the AFS support in find having been = broken for a while), they wanted the addition of AFS functionality to = have little overhead when run in a non-AFS environment. Ditto for SAMBA, = NFS, etc. They asked if I wanted to work on the AFS support. I declined = for a variety of reason, but none of them were because it was a bad = idea. :-) Instead I decided to wait and see if they could pull this off for the = core filesystem types they had set out ('native', SAMBA, NFS). If they = could, I'd look at folding in AFS support and possibly adding some = AFS-specific features. It appears that the initial work is now done. With findutils 4.4.0, much = of the functionality has been moved into a library function fts(). That = was released March 2009, since then there have been two large fix = releases followed by a long period of apparent stability - no further = releases since June 2009. I built and tested this release just a couple of days ago. When compiled = in an afs environment, it correctly implements the -fstype afs = detection. At least in my testing, all the annoying msgs about leaf = nodes, ./.. confusion, etc, seem to be gone. With respect to find itself, it now seems possible to pursue some of the = goals I had when initially looking at making find more useful with AFS. = Things I think would be useful: * An option to cross/not cross/detect and report/etc AFS volume mount = points * Take specific actions at specific mountpoints either by dir name or by = volume name, including by regexp. For example, if my home volume and = subvolumes are all named 'user.scs*', don't follow cross points which = don't match that regexp for the volume name. I was going to do this work about four years ago, and set it aside to = wait for the many issues of fts() to settle out. It appears they've done = so. Coming back to how this applies to du/ls/etc - the expectation of the = findutils developers is that when fts() becomes sufficiently stable, any = of a number of things would happen: * those utilities would adopt use of fts() and expand to use find-like = features * those utilities might get subsumed into findutils * find might be implemented with options that make it do ls-like or = du-like things * standalone utils that do ls-like or du-like things might be = implemented At this point, I can't tell if any of those four possibilities are = process. Some cursory searches of the findutils mailing lists weren't = enlightening.= From jerrymc@msu.edu Fri Apr 30 14:55:55 2010 From: jerrymc@msu.edu (Jerry McAllister) Date: Fri, 30 Apr 2010 09:55:55 -0400 Subject: [OpenAFS] Getting started with OpenAFS In-Reply-To: References: <4BDAB3D5.70005@cgv.tugraz.at> Message-ID: <20100430135555.GD4293@gizmo.acns.msu.edu> On Fri, Apr 30, 2010 at 03:07:40PM +0400, Mike Pliskin wrote: > Dear Lars, >=20 > Thanks a lot for the detailed response, let me see what I can do in terms= of partitions. Generally the task I am trying to solve is the following: > - there is a 100-gigabyte collection of large files (10 mb to 1 gb) > - there are several geographically distributed sites with people that ne= ed access > - files are organized in folders, and there is a fairly good administrat= ive separation on who needs which files - i.e. chances of people writing th= e same file at once are pretty low > - speed is important as well as a way to access any file from anywhere (= but ok to degrade speed if replicas aren't synced yet) >=20 > So the question is - do you think OpenAFS is a right tool for this proble= m? Yes! Your only 'problem' is having enough space to create a new volume in AFS where you can copy all that stuff in the old non-AFS storage. Once you have that stuff copied, you (and verified in some way) then you can use that old space for another AFS volume. ////jerry =20 >=20 > Thanks, > Mike >=20 > -----Original Message----- > From: openafs-info-admin@openafs.org [mailto:openafs-info-admin@openafs.o= rg] On Behalf Of Lars Schimmer > Sent: Friday, April 30, 2010 2:41 PM > Cc: openafs-info@openafs.org > Subject: Re: [OpenAFS] Getting started with OpenAFS >=20 > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Mike Pliskin wrote: > > Dear all, > >=20 > > First, let me state that I am a complete OpenAFS newbie. I???ve just st= arted playing with it and found some obstacles I failed to resolve myself e= ven after reading the docs ??? therefore asking for help here. > >=20 > > 1. which version to install? I need windows client support so I need = 1.5 - right? But it is not stable.. Or is it? And don't see any pre-built r= pms for it, so compiling from sources? >=20 > As the protocol is compatible with rather old versions, you can mix > client and server versions. > BUT as security and bandwidth wise you should use a 1.4.12 or newer > server on your *nix machines. > For a client use 1.5.74 on windows and 1.4.12 on *nix machines. > If you want to test and feel lucky, try the dev builds of 1.5.x on *nix > and report bugs/errors/... >=20 > > 2. tried to compile and it worked but it created a non-"mp" kernel mo= dule while my kernel needs an mp one - how to fix that? > > 3. do I really need a new fresh partition to start with or I can re-u= se an existing one and just make it available via afs? > > Actually #3 is the most important so let me explain. I have a server al= ready and willing to make a large repository available via afs. Attaching a= new hard drive or even changing partitions is hard for me as the servers i= s remote for me and has plenty of data already. So is there any way to make= afs use just a folder somewhere? Any workarounds? >=20 > You need to spend a partition exclusive for OpenAFS server. OpenAFS does > have its onw structure of files in the server-partitions (but it is not > influenced by "false" files in those partitions). >=20 > Which ends up in: you need to copy your files into the OpenAFS space > after you have created the server and volumes and the logic fs-tree > structure. > You COULD share the openAFS fileserver-partitions via NFS or else and > save extra data in those partitions (which are left alone by the OpenAFS > fileserver) but that includes horrible security issues and is absolute > NOT a way to go. >=20 > More important about a new setup are some limits,IMHO the most important > for new users are: > - -only 1 ReadWrite copy of a volume > - -no more than 64k files in a directory > - -replica only on manual/script interaction > - -only whole file locking on server > - -experimental disconnected-mode >=20 > But those are all fields which are worked on. >=20 >=20 > > Thanks a lot for the information in advance, > > Mike Pliskin >=20 > MfG, > Lars Schimmer > - -- > - ------------------------------------------------------------- > TU Graz, Institut f=FCr ComputerGraphik & WissensVisualisierung > Tel: +43 316 873-5405 E-Mail: l.schimmer@cgv.tugraz.at > Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org >=20 > iEYEARECAAYFAkvas9UACgkQmWhuE0qbFyOeoQCfU3I895CFV8BpjpbeOCNLLFKJ > E9QAn2tbqhiBWX+wf5d6OnxsN4AZ0NsO > =3Dv20Z > -----END PGP SIGNATURE----- > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info > ???????????????????????????????????????=15/???&j)b? b???zp=05K??~?????~??= ?=08m?????b??????i????????????+-?w???^????)? >=20 From stephan.wiesand@desy.de Fri Apr 30 15:12:21 2010 From: stephan.wiesand@desy.de (Stephan Wiesand) Date: Fri, 30 Apr 2010 16:12:21 +0200 Subject: [OpenAFS] is the 1.5.74 client supposed to work on RHEL6 beta? In-Reply-To: References: Message-ID: <3070EEB3-AFB3-41B8-8C14-E28A02D8EDEB@desy.de> --Apple-Mail-7-124282013 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Marc, On Apr 29, 2010, at 18:59, Marc Dionne wrote: > On Thu, Apr 29, 2010 at 12:54 PM, Stephan Wiesand = wrote: >> Quick question: is the 1.5.74 client known to cause a kernel panic on = the RHEL6 public beta (amd64) as soon as the module is loaded, or am I = doing something stupid? >>=20 > Hi Stephan, >=20 > That's a known bug, fixed in the current master by this commit: > = http://git.openafs.org/?p=3Dopenafs.git;a=3Dcommit;h=3D14195f0f48d52dd3a81= c52c4a3bc2078857d0f86 thanks, with this patch it works. And with the kernel patch from RHBZ = #584901, it even seems to work quite well. Best regards, Stephan --=20 Stephan Wiesand DESY -DV- Platanenallee 6 15738 Zeuthen, Germany --Apple-Mail-7-124282013 Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIOZDCCBCEw ggMJoAMCAQICAgDHMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNEZXV0 c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMwIQYDVQQD ExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0wNjEyMTkxMDI5MDBaFw0xOTA2MzAyMzU5 MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdERk4tUEtJ MSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3DQEBAQUA A4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAxBAuZgeKm FNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84IkQ4wcOItq aACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVgTe3RCSMq ljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sWVlZDz+HV Ez2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjgdkwgdYwcAYD VR0fBGkwZzBloGOgYYZfaHR0cDovL3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2VydmljZS9hZl9E b3dubG9hZEFSTC5jcmw/LWNybF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09UX0NBXzIwHQYD VR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1UdIwQYMBaAFDHDeRu69VPXF+CJei0XbAqz K50zMA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgECMA0GCSqGSIb3DQEBBQUAA4IB AQA74Vp3wEgX3KkY7IGvWonwvSiSpspZGBJw7Cjy565/lizn8l0ZMfYTK3S9vYCyufdnyTmieTvh ERHua3iRM347XyYndVNljjNj7s9zw7CSI0khUHUjoR8Y4pSFPT8z6XcgjaK95qGFKUD2P3MyWA0J a6bahWzAP7uNZmRWJE6uDT8yNQFb6YyC2XJZT7GGhfF0hVblw/hc843uR7NTBXDn5U2KaYMo4RMJ hp5eyOpYHgwf+aTUWgRo/Sg+iwK2WLX2oSw3VwBnqyNojWOl75lrXP1LVvarQIc01BGSbOyHxQoL BzNytG8MHVQs2FHHzL8w00Ny8TK/jM5JY6gA9/IcMIIFCzCCA/OgAwIBAgIECgIjQTANBgkqhkiG 9w0BAQUFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQMA4GA1UECxMHREZO LVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4XDTA3MDIyNjA5MTcz OVoXDTE5MDIyNTAwMDAwMFowgYIxCzAJBgNVBAYTAkRFMS4wLAYDVQQKEyVEZXV0c2NoZXMgRWxl a3Ryb25lbi1TeW5jaHJvdHJvbiBERVNZMQswCQYDVQQLEwJJVDEWMBQGA1UEAxMNREVTWSBDQSAt IEcwMjEeMBwGCSqGSIb3DQEJARYPZGVzeS1jYUBkZXN5LmRlMIIBIjANBgkqhkiG9w0BAQEFAAOC AQ8AMIIBCgKCAQEA4c1VF6YTFoC8yZufAZ+ceKaupY72FFp60pca6vE91Az3QXrlhweCcdXbi1N2 f/ZpMJEi8vakPWqKcAoLszPEWojUXZMs/RmZ8pSRh1MeF17hyV3SI84TRRIaLQrzbMzZqs2PKbhn cAiwq+nIZXbFZDgPvpsTPIDhY2/unLz81ScY+84g6HJZLMIzbqKw3ga+Ijjh/mKyTKj6jAx6Ubvt j8eKDrQHMJ8TnXDzg7CjN4inCNzFvkV+8OZ3Ez6p04wyd0ESF+4HwgJeQp+drR2MnxO1S+at6TZq hqgIAFVsvwcGqlCi4xAPyE4lJXFxclzHTmd164ZjFUkKa0RWNYjWTQIDAQABo4IBrjCCAaowDwYD VR0TAQH/BAUwAwEB/zALBgNVHQ8EBAMCAQYwHQYDVR0OBBYEFJSX58dzgIIijnL6/92eNIXjtHYU MB8GA1UdIwQYMBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBoGA1UdEQQTMBGBD2Rlc3ktY2FAZGVz eS5kZTCBiAYDVR0fBIGAMH4wPaA7oDmGN2h0dHA6Ly9jZHAxLnBjYS5kZm4uZGUvZ2xvYmFsLXJv b3QtY2EvcHViL2NybC9jYWNybC5jcmwwPaA7oDmGN2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xv YmFsLXJvb3QtY2EvcHViL2NybC9jYWNybC5jcmwwgaIGCCsGAQUFBwEBBIGVMIGSMEcGCCsGAQUF BzAChjtodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9jYWNlcnQvY2Fj ZXJ0LmNydDBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1j YS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAG2JDWDdZEMc5TmSst6Z LChNcrsn27oIT1pJn51Vxtt5bpZ07L/zrqj1um7p14Mqq/Bu2+svMu+l+Be90AGdB1DpG3++qedt 8piOjqYziD0Za9AkzIc3MWZJVU48aY0KOVR0qHAYe+JKCtAQO2Gfeq+Vnne021sGf6vzHVN8xTTG WTFOzCm5LGQd/eZ0VP/uZGex5fp4ZyW6BP0bv8Zc8QXDi5FipMllCpspr9phUKDA7mnD50coqFv8 khI1/vg8x/uFM+dQvAWpOZ9wbZ335mKT/Qxe+ELuZ/O0cnNGtakvOO5E0cZyCM5xle36NUtu+Kye QrI0SNacFZ0ahnfoe2YwggUsMIIEFKADAgECAgQOojLnMA0GCSqGSIb3DQEBBQUAMIGCMQswCQYD VQQGEwJERTEuMCwGA1UEChMlRGV1dHNjaGVzIEVsZWt0cm9uZW4tU3luY2hyb3Ryb24gREVTWTEL MAkGA1UECxMCSVQxFjAUBgNVBAMTDURFU1kgQ0EgLSBHMDIxHjAcBgkqhkiG9w0BCQEWD2Rlc3kt Y2FAZGVzeS5kZTAeFw0wOTA4MTIxMjI4MDdaFw0xMjA4MTExMjI4MDdaMGQxCzAJBgNVBAYTAkRF MS4wLAYDVQQKEyVEZXV0c2NoZXMgRWxla3Ryb25lbi1TeW5jaHJvdHJvbiBERVNZMQswCQYDVQQL EwJEVjEYMBYGA1UEAxMPU3RlcGhhbiBXaWVzYW5kMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB CgKCAQEAvmv0eaQIuKKSyi5dXs/pK29CIU/n/BP3l78FSmGKsfBM3trxX7qxcbW6b9yZrIMcMkO/ pZ2GAujlc+TCrrQAfTxbKhqc6Y3XaubaMAVs1lDnNbQHk3Vyxd+LFIagea6yKnFqNi3UHrNxBTme PR9i//tBaA9H8GbJLbN8uSKAE/RAq+CFzNzSORk6PhPiveqQlMWBkH0smt1tWdm2ANzfNHen1rg8 Uc1iQ/18CLOcbikd8fRmqXlRPqL/Cle4btOaUg/pt9jw9GisFwwRVQwJ8mhOo6N3U/2H0gndexSM E36ZrPJHrLKgL75HiycNunXggRIiBftnmXNixqgMyHsVbwIDAQABo4IBxTCCAcEwCQYDVR0TBAIw ADALBgNVHQ8EBAMCBeAwKQYDVR0lBCIwIAYIKwYBBQUHAwIGCCsGAQUFBwMEBgorBgEEAYI3FAIC MB0GA1UdDgQWBBQHYBBFOi3BuEgLoWAa4OHFqhPP1zAfBgNVHSMEGDAWgBSUl+fHc4CCIo5y+v/d njSF47R2FDAiBgNVHREEGzAZgRdzdGVwaGFuLndpZXNhbmRAZGVzeS5kZTB9BgNVHR8EdjB0MDig NqA0hjJodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Rlc3ktY2EvcHViL2NybC9nX2NhY3JsLmNybDA4 oDagNIYyaHR0cDovL2NkcDIucGNhLmRmbi5kZS9kZXN5LWNhL3B1Yi9jcmwvZ19jYWNybC5jcmww gZgGCCsGAQUFBwEBBIGLMIGIMEIGCCsGAQUFBzAChjZodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Rl c3ktY2EvcHViL2NhY2VydC9nX2NhY2VydC5jcnQwQgYIKwYBBQUHMAKGNmh0dHA6Ly9jZHAyLnBj YS5kZm4uZGUvZGVzeS1jYS9wdWIvY2FjZXJ0L2dfY2FjZXJ0LmNydDANBgkqhkiG9w0BAQUFAAOC AQEAZaf9oE7o7DyeleVE/h/uFblKmLOOvhKfbqp+ROqzNo6F7t0YVu4LRnxvIGAWC6/aIO2kTGsx CGEuH6PbU+LW/6cWchzGOkB71at2EFVLFdUx698QXuZgArz2F80A+y4KPK2JQMAVMleBEsB5w5L3 P4bt5EsHn0oXdKkRJdiape0tDXcx1GiERYtu1pueaw1yokmdqkOXMXqi5Dl8zL+baBO6iDtmsb7+ AFDH0FR8f4UnivgO0At43n++qDPlkKXFcip9YQyT6UdaBpLtSQoJROajWHCpy5aZHHAICQy/PSy7 yIBfYrYt7VKJodPi42WzUsRG+AAC60XI74sdXmlUVDGCA1QwggNQAgEBMIGLMIGCMQswCQYDVQQG EwJERTEuMCwGA1UEChMlRGV1dHNjaGVzIEVsZWt0cm9uZW4tU3luY2hyb3Ryb24gREVTWTELMAkG A1UECxMCSVQxFjAUBgNVBAMTDURFU1kgQ0EgLSBHMDIxHjAcBgkqhkiG9w0BCQEWD2Rlc3ktY2FA ZGVzeS5kZQIEDqIy5zAJBgUrDgMCGgUAoIIBnTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG CSqGSIb3DQEJBTEPFw0xMDA0MzAxNDEyMjJaMCMGCSqGSIb3DQEJBDEWBBQ4No4Bl6UvmfMlQy84 vEwYhGikXjCBnAYJKwYBBAGCNxAEMYGOMIGLMIGCMQswCQYDVQQGEwJERTEuMCwGA1UEChMlRGV1 dHNjaGVzIEVsZWt0cm9uZW4tU3luY2hyb3Ryb24gREVTWTELMAkGA1UECxMCSVQxFjAUBgNVBAMT DURFU1kgQ0EgLSBHMDIxHjAcBgkqhkiG9w0BCQEWD2Rlc3ktY2FAZGVzeS5kZQIEDqIy5zCBngYL KoZIhvcNAQkQAgsxgY6ggYswgYIxCzAJBgNVBAYTAkRFMS4wLAYDVQQKEyVEZXV0c2NoZXMgRWxl a3Ryb25lbi1TeW5jaHJvdHJvbiBERVNZMQswCQYDVQQLEwJJVDEWMBQGA1UEAxMNREVTWSBDQSAt IEcwMjEeMBwGCSqGSIb3DQEJARYPZGVzeS1jYUBkZXN5LmRlAgQOojLnMA0GCSqGSIb3DQEBAQUA BIIBAF49S8n076JSXfxSnUP2DfASfq19zO8BmJ/MUG9xAAzSWWTq07d2eAWRMDNAMxNpgDGpkQVH sdEc3f6OJgaaJYVq9xsJuHAAc/+QzbjVAQzplaWOGjw3FR6SqQ14djgGTYpkuctoCYKQ5qd6X8K3 oZ+f+Tmz8VxBLzbbXKJb8eHa78CL4PTtLxLbzisSrutAQqbQ5+aCeTEmRh3hNmp02uJvKF5rQJ1B +B0VP+ZUjczzVauaQSoBu9fLUrpB9lCoo0nZKyTEseBHiNlWY5UcYNf4iVWt+kELz3wjwRU7iYE0 KFIuBH6U/mg5HPnWin7UR2mn4GluP+RhCLzm+Z4/5IUAAAAAAAA= --Apple-Mail-7-124282013-- From dhowells@redhat.com Fri Apr 30 15:12:41 2010 From: dhowells@redhat.com (David Howells) Date: Fri, 30 Apr 2010 15:12:41 +0100 Subject: [OpenAFS] AFS version of du In-Reply-To: <06563EB3-AA97-4C96-9A2E-450197B518B9@umich.edu> References: <06563EB3-AA97-4C96-9A2E-450197B518B9@umich.edu> <4BDA91B0.7010908@ltu.se> Message-ID: <3262.1272636761@redhat.com> Steve Simmons wrote: > Any utility that recurses through the file system (du, find, ls, others) has > the same set of core problems - things to include or exclude, cross or don't > cross mount points, etc, etc. This is immensely complicated by the breadth > of things that can and do comprise mount points. Is a NFS mount a mount > point? An AFS? Samba shares? Repeat question for every conceivable file > system, and it becomes hellacious. Kafs deals with this by generating a separate superblock for each volume. This mean du works correctly. Note, even in OpenAFS, you can return a different set of filesystem stats for each dentry in the tree if you wish. The statfs superblock op takes a dentry for you to use as base. David From adeason@sinenomine.net Fri Apr 30 15:41:48 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Fri, 30 Apr 2010 09:41:48 -0500 Subject: [OpenAFS] Re: Getting started with OpenAFS References: <4BDAB3D5.70005@cgv.tugraz.at> Message-ID: <20100430094148.fe7874cf.adeason@sinenomine.net> On Fri, 30 Apr 2010 12:41:25 +0200 Lars Schimmer wrote: > > 3. do I really need a new fresh partition to start with or I can > > re-use an existing one and just make it available via afs? > > Actually #3 is the most important so let me explain. I have a > > server already and willing to make a large repository available via > > afs. Attaching a new hard drive or even changing partitions is hard > > for me as the servers is remote for me and has plenty of data > > already. So is there any way to make afs use just a folder > > somewhere? Any workarounds? > > You need to spend a partition exclusive for OpenAFS server. OpenAFS does > have its onw structure of files in the server-partitions (but it is not > influenced by "false" files in those partitions). To be clear, I think there are two things being asked here. One question is "do I need a dedicated partition/disk for an AFS partition?" The answer to that is no; you can just create new /vicepX directories, and create the file /vicepa/AlwaysAttach to use them. If you want to use some other partition, just bind-mount (or lofs-mount, etc) /vicepa to /var/foo/bar/baz. The other question is about whether you can use an existing directory structure of data, which which Lars answered. You can use an already-existing partition, but you need to copy your data into AFS; you can't just use it straight from disk. However, there is jhutz's hostafsd (and tafssrv), which does allow for serving existing data via AFS. But as far as I know those haven't been touched in awhile, aren't ready for production use, etc etc. -- Andrew Deason adeason@sinenomine.net From adeason@sinenomine.net Fri Apr 30 16:00:54 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Fri, 30 Apr 2010 10:00:54 -0500 Subject: [OpenAFS] Re: Getting started with OpenAFS References: <4BDAB3D5.70005@cgv.tugraz.at> <4BDAD036.5040601@cgv.tugraz.at> Message-ID: <20100430100054.1ce4dba6.adeason@sinenomine.net> On Fri, 30 Apr 2010 17:49:16 +0400 Mike Pliskin wrote: > Ok thanks a ton for explaining, the only point left is read-write and > read-only and how to separate those. So far it sounds like I will need > to have a setup like > /afs/public/data1 > /afs/public/data2 > /afs/public/data3 > /afs/user1/data1 > /afs/user2/data2 etc The general notion of ROs vs RWs sounds correct, but the path structure is annoying me :) Traditionally, the convention of paths goes something like this: /afs// for the RO path, and /afs//. for the RW path. (And /afs/./ provides an RW path for anything). So for example, you'd have /afs/area9.dk/.data1/, that some users can write to and fiddle around with. When someone/something decides it is time to release that data to all sites and make it 'public' via the RO paths, the data in /afs/area9.dk/.data1/ becomes synced with /afs/area9.dk/data1/. You 'decide' this by running a command (specifically 'vos release'). Then people can read the new stuff in /afs/area9.dk/data1/ by accessing one of many servers. I'm not really sure I'm clear on your usage, though... you have data which will be 'accessed' by geographically diverse clients. But it helps to clarify 'access' into 'read' and 'write'. Do you have people from multiple different sites that will be writing to the same set of data? As far as I know, that will always be slow, since you must at least contact the remote sites immediately, or you risk cache coherence problems. -- Andrew Deason adeason@sinenomine.net From Richard.Brittain@dartmouth.edu Fri Apr 30 17:44:07 2010 From: Richard.Brittain@dartmouth.edu (Richard Brittain) Date: Fri, 30 Apr 2010 12:44:07 -0400 (EDT) Subject: [OpenAFS] AFS version of du In-Reply-To: <06563EB3-AA97-4C96-9A2E-450197B518B9@umich.edu> References: <4BDA91B0.7010908@ltu.se> <06563EB3-AA97-4C96-9A2E-450197B518B9@umich.edu> Message-ID: On Fri, 30 Apr 2010, Steve Simmons wrote: > On Apr 30, 2010, at 4:15 AM, Staffan H?m?l? wrote: > >> Is there a version of du that does not follow AFS mountpoints? >> >> If I try to do a 'du -sh *' in a directory that has some AFS mountpoints it inevitably fails after some time. It also takes a lot of time when it has to look through things in mounted volumes (e.g. the backup volume that I have mounted in many places). >> >> I've tried -P and -x to make it skip mount points, but it doesn't work (at least on CentOS 5 Linux). > > The short answer is that it might be coming coming, but it's going to be > a while. Here's the detailed scoop as I understand it, based on some old > mail exchanges I had with the findutils maintainer James Youngman and > discussion on the findutils mailing list. This is very promising news. I was about to start a new thread about problems with 'find', but since it is so closely linked with this I'll just jump in here. Yesterday I was running 'find' and 'fs lsmount' across our cell to explicitly look for volume mountpoints, and got some very strange errors. On directories which exist and I had full access to, find would sometimes throw a big pile of errors like: find: ./users/a/: No such file or directory - and obviously did not recurse into that directory. It was acting like it read the directory entries but failed to later stat() them. I blamed GNU find for a while, but then observed the same behaviour from Solaris 9 and OSX. This is definitely not a permission issue (l ACL but not r), but it does seem to be related to crossing mount points, since I have never seen an error running find inside a single volume. I finally got a RHEL5 linux box to recurse my cell to the desired depth with no errors, but only as long as it was doing nothing else. Running two 'find's immediately generated errors (RHEL5 current, OpenAFS 1.4.12). My servers are a mix of 1.4.11 and 1.4.12 currently. I discovered that one user had made a mount point for a different cell's root inside his home. RHEL5/openafs 1.4.12 happily crossed over and starting searching the other cell, but I noticed that my other test system (RHEL4/openafs 1.4.11) didn't follow. It would be _really_ nice if tools didn't follow mount points to other cells, if nothing else! Richard -- Richard Brittain, Research Computing Group, Kiewit Computing Services, 6224 Baker/Berry Library Dartmouth College, Hanover NH 03755 Richard.Brittain@dartmouth.edu 6-2085 From rra@stanford.edu Fri Apr 30 17:54:55 2010 From: rra@stanford.edu (Russ Allbery) Date: Fri, 30 Apr 2010 09:54:55 -0700 Subject: [OpenAFS] AFS version of du In-Reply-To: (Richard Brittain's message of "Fri, 30 Apr 2010 12:44:07 -0400 (EDT)") References: <4BDA91B0.7010908@ltu.se> <06563EB3-AA97-4C96-9A2E-450197B518B9@umich.edu> Message-ID: <87pr1g3mow.fsf@windlord.stanford.edu> Richard Brittain writes: > Yesterday I was running 'find' and 'fs lsmount' across our cell to > explicitly look for volume mountpoints, and got some very strange > errors. On directories which exist and I had full access to, find would > sometimes throw a big pile of errors like: > find: ./users/a/: No such file or directory While this may or may not fix those problems, you may find: http://www.eyrie.org/~eagle/software/lsmounts/ http://www.eyrie.org/~eagle/software/fsr/ useful until such time as coreutils has native support for some of this sort of thing. -- Russ Allbery (rra@stanford.edu) From Richard.Brittain@dartmouth.edu Fri Apr 30 19:32:27 2010 From: Richard.Brittain@dartmouth.edu (Richard Brittain) Date: Fri, 30 Apr 2010 14:32:27 -0400 (EDT) Subject: [OpenAFS] AFS version of du In-Reply-To: <87pr1g3mow.fsf@windlord.stanford.edu> References: <4BDA91B0.7010908@ltu.se> <06563EB3-AA97-4C96-9A2E-450197B518B9@umich.edu> <87pr1g3mow.fsf@windlord.stanford.edu> Message-ID: On Fri, 30 Apr 2010, Russ Allbery wrote: > Richard Brittain writes: > >> Yesterday I was running 'find' and 'fs lsmount' across our cell to >> explicitly look for volume mountpoints, and got some very strange >> errors. On directories which exist and I had full access to, find would >> sometimes throw a big pile of errors like: >> find: ./users/a/: No such file or directory > > While this may or may not fix those problems, you may find: > > http://www.eyrie.org/~eagle/software/lsmounts/ > http://www.eyrie.org/~eagle/software/fsr/ > > useful until such time as coreutils has native support for some of this > sort of thing. THANKS!. lsmounts works beautifully, even on the machines which show the worst 'find' behaviour. This solves my immediate need, and I'll probably use your mount point database too, but begs the question of why perl's File::Find module works fine, while 'find' breaks. Underneath they are presumably making very similar system calls. Richard -- Richard Brittain, Research Computing Group, Kiewit Computing Services, 6224 Baker/Berry Library Dartmouth College, Hanover NH 03755 Richard.Brittain@dartmouth.edu 6-2085 From deengert@anl.gov Fri Apr 30 19:45:10 2010 From: deengert@anl.gov (Douglas E. Engert) Date: Fri, 30 Apr 2010 13:45:10 -0500 Subject: [OpenAFS] AFS version of du In-Reply-To: References: <4BDA91B0.7010908@ltu.se> <06563EB3-AA97-4C96-9A2E-450197B518B9@umich.edu> Message-ID: <4BDB2536.8090003@anl.gov> Richard Brittain wrote: > On Fri, 30 Apr 2010, Steve Simmons wrote: > >> On Apr 30, 2010, at 4:15 AM, Staffan H?m?l? wrote: >> >>> Is there a version of du that does not follow AFS mountpoints? >>> >>> If I try to do a 'du -sh *' in a directory that has some AFS >>> mountpoints it inevitably fails after some time. It also takes a lot >>> of time when it has to look through things in mounted volumes (e.g. >>> the backup volume that I have mounted in many places). >>> >>> I've tried -P and -x to make it skip mount points, but it doesn't >>> work (at least on CentOS 5 Linux). >> >> The short answer is that it might be coming coming, but it's going to >> be a while. Here's the detailed scoop as I understand it, based on >> some old mail exchanges I had with the findutils maintainer James >> Youngman and discussion on the findutils mailing list. > > This is very promising news. I was about to start a new thread about > problems with 'find', but since it is so closely linked with this I'll > just jump in here. > > Yesterday I was running 'find' and 'fs lsmount' across our cell to > explicitly look for volume mountpoints, and got some very strange > errors. On directories which exist and I had full access to, find would > sometimes throw a big pile of errors like: > find: ./users/a/: No such file or directory I have been working on an AFS audit tool written in Perl since find has too many issues. The heart of this uses File::Find and if a directory is found AFS::FS::lsmount( $rname ) is used to test if its a mount point and set File::Find::prune = 1; The Perl module AFS-2.6.2 was released on 4/1, and is working well! This same combination could be used to write a Perl du command that would not cross mount points. A list of volumes is input to the tool, and each volume is mounted temporarily. Using the AFS::ACL module ACLs are examined and if a sub directory has the same ACL as its parent, it is reported with the parent. (the ACL entries are sorted before the compare.) So our 2000 volumes with 600,000 directories get reduced down to 8000 entries to look at. These are further examined based on the type of volume and the uses and rights listed in the ACLs. If all the volumes in the cell are scanned, one can find volumes that have no mount points as well as volumes with multiple mount points. > > - and obviously did not recurse into that directory. It was acting like > it read the directory entries but failed to later stat() them. I blamed > GNU find for a while, but then observed the same behaviour from Solaris > 9 and OSX. > > This is definitely not a permission issue (l ACL but not r), but it does > seem to be related to crossing mount points, since I have never seen an > error running find inside a single volume. I finally got a RHEL5 linux > box to recurse my cell to the desired depth with no errors, but only as > long as it was doing nothing else. Running two 'find's immediately > generated errors (RHEL5 current, OpenAFS 1.4.12). > > My servers are a mix of 1.4.11 and 1.4.12 currently. > > I discovered that one user had made a mount point for a different cell's > root inside his home. RHEL5/openafs 1.4.12 happily crossed over and > starting searching the other cell, but I noticed that my other test > system (RHEL4/openafs 1.4.11) didn't follow. It would be _really_ nice > if tools didn't follow mount points to other cells, if nothing else! > > Richard -- Douglas E. Engert Argonne National Laboratory 9700 South Cass Avenue Argonne, Illinois 60439 (630) 252-5444 From adeason@sinenomine.net Fri Apr 30 23:07:49 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Fri, 30 Apr 2010 17:07:49 -0500 Subject: [OpenAFS] Re: experience of SQLite on AFS References: <20100419115512.861a1fb3.adeason@sinenomine.net> <20100419174103.e76249d5.adeason@sinenomine.net> Message-ID: <20100430170749.9cb76e73.adeason@sinenomine.net> On Mon, 19 Apr 2010 17:41:03 -0500 Andrew Deason wrote: > On Mon, 19 Apr 2010 14:51:28 -0600 > Ken Dreyer wrote: > > > The ACLs were one of the first things I looked at, but "k" seemed to > > have no effect. I will try to build SQLite aside from PHP to see if I > > can narrow the problem further. I'll try to provide backtraces / > > cmdebug too, when I can pull them together. > > A truss would also at least help to see if it's our bug or theirs. My > guess would be that it's ours, since the only difference in the cases > you describe is RW vs RO. But it's possible sqlite is broken for > RO-fs-with-flock or something. After some offline discussion, this appears to probably be the case. sqlite opens the db file O_RDONLY, and attempts to acquire an fcntl F_WRLCK on it, to which it gets EROFS back. Trying to acquire a writelock on a file opened readonly doesn't make a lot of sense to me; can someone tell me if POSIX specifies that that should fail? In any case, I think technically fcntl should be returning EBADF here, not EROFS (I think this is our fault, but I haven't checked yet). I don't know if it makes a difference what error code sqlite gets back; I'll try later to see if it does anything differently when it gets EBADF back instead. -- Andrew Deason adeason@sinenomine.net From adeason@sinenomine.net Fri Apr 30 23:10:42 2010 From: adeason@sinenomine.net (Andrew Deason) Date: Fri, 30 Apr 2010 17:10:42 -0500 Subject: [OpenAFS] Re: experience of SQLite on AFS References: <20100419115512.861a1fb3.adeason@sinenomine.net> <20100419174103.e76249d5.adeason@sinenomine.net> <20100430170749.9cb76e73.adeason@sinenomine.net> Message-ID: <20100430171042.e38fed0d.adeason@sinenomine.net> On Fri, 30 Apr 2010 17:07:49 -0500 Andrew Deason wrote: > After some offline discussion, this appears to probably be the case. > sqlite opens the db file O_RDONLY, and attempts to acquire an fcntl > F_WRLCK on it, to which it gets EROFS back. Er, forgot to mention, at this point sqlite goes into an infinite sleep/retry loop, which is why it appears to hang. -- Andrew Deason adeason@sinenomine.net From gtb@slac.stanford.edu Fri Apr 30 23:20:08 2010 From: gtb@slac.stanford.edu (Buhrmaster, Gary) Date: Fri, 30 Apr 2010 15:20:08 -0700 Subject: [OpenAFS] Re: experience of SQLite on AFS In-Reply-To: <20100430170749.9cb76e73.adeason@sinenomine.net> References: <20100419115512.861a1fb3.adeason@sinenomine.net> <20100419174103.e76249d5.adeason@sinenomine.net> <20100430170749.9cb76e73.adeason@sinenomine.net> Message-ID: <6F51B50ECF32084788B9B3A8469A71B5D0019FE969@EXCHCLUSTER1-02.win.slac.stanford.edu> > After some offline discussion, this appears to probably be the case. > sqlite opens the db file O_RDONLY, and attempts to acquire an fcntl > F_WRLCK on it, to which it gets EROFS back. Trying to acquire a > writelock on a file opened readonly doesn't make a lot of sense to me; > can someone tell me if POSIX specifies that that should fail? Should fail with EBADF.... From: http://www.opengroup.org/onlinepubs/009695399/functions/fcntl.html Errors: [EBADF] The fildes argument is not a valid open file descriptor, or the argument cmd is F_SETLK or F_SETLKW, the type of lock, l_type, is a shared lock (F_RDLCK), and fildes is not a valid file descriptor open for reading, or the type of lock, l_type, is an exclusive lock (F_WRLCK), and fildes is not a valid file descriptor open for writing. From chee.chang.bu@accenture.com Tue Apr 27 17:57:54 2010 From: chee.chang.bu@accenture.com (chee.chang.bu@accenture.com) Date: Wed, 28 Apr 2010 00:57:54 +0800 Subject: [OpenAFS] Inquiry For OpenAFS Installation Guide For HP-UX 11.31 Message-ID: This is a multi-part message in MIME format. --_000_D508AA2510145C4E951CD6DA744689D5B8BACFCD6BAPAXM3112dirs_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable To Whom It May Concern, I am having following problem when follow the guide in = http://docs.openafs.org/QuickStartUnix/ch02s07.html. 1) I can't execute cp usr/vice/etc/afs.rc /sbin/init.d/afs as there is = no afs.rc in the ../root.client/usr/vice/etc 2) /usr/conf/master.d is not exists in my HP-UX 11.31. 3) I can only find libafs.nonfs.a and libafs64.nonfs.a in the = ../root.client/usr/bin May I know if the getting starr guide = (http://docs.openafs.org/QuickStartUnix/ch02s07.html) is for HP-UX = server that is earlier than HP-UX 11.31? If yes, can you please tell me = if there is any documentation/guide to install the OpenAFS into HP-UX = 11.31. Thanks. Bu Chee Chang __________________________ Accenture Technology Solutions Mobile: 94557661 Email: = chee.chang.bu@accenture.com This message is for the designated recipient only and may contain = privileged, proprietary, or otherwise private information. If you have = received it in error, please notify the sender immediately and delete = the original. Any other use of the email by you is prohibited. --_000_D508AA2510145C4E951CD6DA744689D5B8BACFCD6BAPAXM3112dirs_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

To Whom It May = Concern,

 

I am having following problem when = follow the guide in http://docs.openafs.org/QuickStartUnix/ch02s07.html<= /span>.

1) I can’t execute = cp usr/vice/etc/afs.rc  = /sbin/init.d/afs as there is no afs.rc in the ../root.client/usr/vice/etc

2) = /usr/conf/master.d is not exists in my HP-UX = 11.31.

3) I can only find libafs.nonfs.a and = libafs64.nonfs.a in the ../root.client/usr/bin=

 

May I know if the getting starr guide (http://docs.openafs.org/QuickStartUnix/ch02s07.html<= /span>) is for HP-UX server that is = earlier than HP-UX 11.31? If yes, can you please tell me if there is any = documentation/guide to install the OpenAFS into HP-UX = 11.31.

 

Thanks.

Bu Chee = Chang

_= _________________________

Accenture Technology Solutions
Mobile: 94557661
Email: chee.chang.bu@accenture.com
<= /o:p>

 

This message is for the designated = recipient only and may contain privileged, proprietary, or otherwise = private information. If you have received it in error, please notify the = sender immediately and delete the original. Any other use of the email = by you is prohibited.

--_000_D508AA2510145C4E951CD6DA744689D5B8BACFCD6BAPAXM3112dirs_-- From jjmpal@iki.fi Wed Apr 28 15:01:44 2010 From: jjmpal@iki.fi (Joonatan Palmu) Date: Wed, 28 Apr 2010 17:01:44 +0300 Subject: [OpenAFS] Vicepa partition over two terabytes Message-ID: <20100428170144.47e30687@neumann.tfy.utu.fi> Hello, I recently resized my /vicepa xfs-partition over two terabytes (2239707136k) which lead to vos partinfo message: "Free space on partition /vicepa: 149840764 K blocks out of total -2055260160". Can you tell me how critical this situation is and which would be the right way to fix it? I run openafs-fileserver version 1.4.7.dfsg1-6+lenny1 on Debian servers and there is a problem partition only on one machine. Best regards, Joonatan Palmu -------------------------------------- Joonatan Palmu, Sysadmin of Theoretical Physics Department of Physics and Astronomy, University of Turku FIN-20014 Turku, Finland phone: +358-2-3335964 -------------------------------------- From John.Lobaugh@morganstanley.com Fri Apr 30 16:59:04 2010 From: John.Lobaugh@morganstanley.com (Lobaugh, John) Date: Fri, 30 Apr 2010 11:59:04 -0400 Subject: [OpenAFS] PriorityClass registry setting in OpenAFS 1.4.2.0 Message-ID: --_000_A379AD613A086A42B1929461E6700A488B0815F7NYWEXMBX2130msa_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Is the reg setting HKLM\SYSTEM\CurrentControlSet\Services\transarcafsdaeomon/PriorityClass used with version 1.4.2.0 ? We have been struggling with a deadlock issue on two Windows 2003 = servers where this setting is not present. The issue is not occuring on = some other servers where the setting is present. John Lobaugh -------------------------------------------------------------------------= - NOTICE: If received in error, please destroy, and notify sender. Sender = does not intend to waive confidentiality or privilege. Use of this email = is prohibited when received in error. We may monitor and store emails to = the extent permitted by applicable law. --_000_A379AD613A086A42B1929461E6700A488B0815F7NYWEXMBX2130msa_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Is the = reg setting=20
 
HKLM\SYSTEM\CurrentControlSet\Services\transar= cafsdaeomon/PriorityClass=20
 
used = with version=20 1.4.2.0 ?
 
We = have been=20 struggling with a deadlock issue on two Windows 2003 servers where this = setting=20 is not present. The issue is not occuring on some other servers where = the=20 setting is present.
 
John=20 Lobaugh
 
 
 
 
  

NOTICE: If received in error, please destroy, = and notify sender. Sender does not intend to waive confidentiality or = privilege. Use of this email is prohibited when received in = error. We may monitor and = store emails to the extent permitted by applicable = law.

--_000_A379AD613A086A42B1929461E6700A488B0815F7NYWEXMBX2130msa_--