[OpenAFS] Re: creating and deleting user accounts

2012-02-28 Thread Andrew Deason
On Tue, 28 Feb 2012 20:22:31 -0500 "Lewis, Dave" wrote: > Last night when I created the user account, I got "No such device" > errors when trying to access the home directory on some computers. > The errors remained after I did syncvldb and syncserv and after I ran > fs flush commands. But when

Re: [OpenAFS] Re: Best way to debug "Lost contact with file server"

2012-02-28 Thread Andrew Deason
On Tue, 28 Feb 2012 18:56:30 -0600 Benjamin Kaduk wrote: > Er, I would have thought that this would cause a group of clients > deployed near each other to all prefer the same replica, which is not > really "random". That is, though from the point of view of a single > client the choice may be r

[OpenAFS] creating and deleting user accounts

2012-02-28 Thread Lewis, Dave
Hi, I got some errors while creating a new account for a user whose account I had deleted. (The reason I deleted it was that I needed to re-create the account with a different UID.) I used 'uss add' and a template file for account creation and 'uss delete' for account removal. I know that uss i

Re: [OpenAFS] Re: Best way to debug "Lost contact with file server"

2012-02-28 Thread Russ Allbery
Benjamin Kaduk writes: > Er, I would have thought that this would cause a group of clients > deployed near each other to all prefer the same replica, which is not > really "random". That is, though from the point of view of a single > client the choice may be random, from the point of view of ma

Re: [OpenAFS] Re: Best way to debug "Lost contact with file server"

2012-02-28 Thread Benjamin Kaduk
On Mon, 27 Feb 2012, Andrew Deason wrote: On Fri, 24 Feb 2012 02:51:48 -0800 Ken Elkabany wrote: Off-email question: If a volume has N read replicas, how do clients choose which one to use? By default, it's effectively random. Technically the client also takes into account the ip addresses

Re: [OpenAFS] Fedora 16 and Openafs

2012-02-28 Thread Ken Dreyer
On Tue, Feb 28, 2012 at 9:55 AM, Berthold Cogel wrote: > Hello! > > I'm trying to get openafs to work on Fedora 16. The rpms from rpmfusion > did work with older kernel versions but failed totally with recent > kernels. Hmm, what's the error you get with RPM Fusion's RPMs? I'd like to fix that if

Re: [OpenAFS] Fedora 16 and Openafs

2012-02-28 Thread Derrick Brashear
On Tue, Feb 28, 2012 at 11:55 AM, Berthold Cogel wrote: > Hello! > > I'm trying to get openafs to work on Fedora 16. The rpms from rpmfusion > did work with older kernel versions but failed totally with recent > kernels. So I've build my own rpms. > I took the source packages for 1.6.1-0.pre2 and

[OpenAFS] Fedora 16 and Openafs

2012-02-28 Thread Berthold Cogel
Hello! I'm trying to get openafs to work on Fedora 16. The rpms from rpmfusion did work with older kernel versions but failed totally with recent kernels. So I've build my own rpms. I took the source packages for 1.6.1-0.pre2 and build an source rpm with the makesrpm.pl. Build and install worked w

[OpenAFS] Re: OpenAFS freeze problems

2012-02-28 Thread Andrew Deason
On Mon, 27 Feb 2012 20:00:29 -0600 John Tang Boyland wrote: > ] About every few hours or so, AFS "freezes" on a write: > ] the attempt to write blocks for about 30 seconds or so. Others answered most of this, but briefly... > As suspected, there is no problem with the number of threads; the > r

Re: [OpenAFS] Re: OpenAFS freeze problems

2012-02-28 Thread Jeffrey Altman
On 2/27/2012 9:01 PM, John Tang Boyland wrote: > ] About every few hours or so, AFS "freezes" on a write: > ] the attempt to write blocks for about 30 seconds or so. > > ... > > As suspected, there is no problem with the number of threads; the rxdebug > command shows 0 threads used out of 11 whil

Re: [OpenAFS] Re: OpenAFS freeze problems

2012-02-28 Thread Derrick Brashear
On Mon, Feb 27, 2012 at 9:00 PM, John Tang Boyland wrote: > ] About every few hours or so, AFS "freezes" on a write: > ] the attempt to write blocks for about 30 seconds or so. > > ... > > As suspected, there is no problem with the number of threads; the rxdebug > command shows 0 threads used out