Re: [OpenAFS] Re: 1.5.77 debian client hangs at new ip address

2010-10-10 Thread Simon Wilkinson
> Lock afsdb_client_loc status: (none_waiting, write_locked(pid:2766 at:685)) This means that we're in the middle of a call out to the user-space DNS helper. Are you relying on the DNS for information about your cell location? Since you changed the IP address of your machine, can you still perfo

Re: [OpenAFS] Re: 1.5.77 debian client hangs at new ip address

2010-10-10 Thread Gémes Géza
2010-10-11 04:03 keltezéssel, Andrew Deason írta: > On Sun, 10 Oct 2010 19:37:54 +0200 > Gémes Géza wrote: > > >> I have a debian squeeze box with 1.5.75 (only the client parts from >> debs) installed. Everything works fine until I give a new IP address to >> the box. Then the afsd seems to han

Re: [OpenAFS] MacOS AppleDouble excretions

2010-10-10 Thread Brandon S Allbery KF8NH
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/10/10 15:24 , Adam Megacz wrote: > Unfortunately it seems like there is no way to get MacOS to refrain from > writing the second kind of file, and it seems like Apple deliberately > doesn't want there to be one. ...because if OSX wants a resourc

[OpenAFS] Re: bos killed fileserver before it was shut down cleanly.

2010-10-10 Thread Andrew Deason
On Sun, 10 Oct 2010 12:36:09 -0700 Russ Allbery wrote: > Adam Megacz writes: > > > Just curious, is this "stall" a bug in the fileserver, or something > > which happens for a good reason? If so, what is the reason? > > It happens, in my experience, when there are hundreds of thousands of > ope

[OpenAFS] Re: 1.5.75 debian client hangs at new ip address

2010-10-10 Thread Andrew Deason
On Sun, 10 Oct 2010 19:37:54 +0200 Gémes Géza wrote: > I have a debian squeeze box with 1.5.75 (only the client parts from > debs) installed. Everything works fine until I give a new IP address to > the box. Then the afsd seems to hang (after about 20-30 seconds /afs > becomes unavailable: eg. ls

Re: [OpenAFS] MacOS AppleDouble excretions

2010-10-10 Thread Derrick Brashear
They have a valid point. You should look at this year's GSoC projects for more details Derrick On Oct 10, 2010, at 3:25 PM, Adam Megacz wrote: > > MacOS seems to litter network shares with two kinds of files: > > .DS_Store (Finder data) > ._filename (AppleDouble resource fork) > >

Re: [OpenAFS] MacOS AppleDouble excretions

2010-10-10 Thread Thomas Briggs
On Oct 10, 2010, at 3:24 PM, Adam Megacz wrote: > The more sophisticated approach would probably be to claim to MacOS that > /afs/ supports resource forks, and report permission-denied when an > attempt to write a resource fork is made. This has the advantage of not > being filename-based and no

Re: [OpenAFS] Re: bos killed fileserver before it was shut down cleanly.

2010-10-10 Thread Russ Allbery
Adam Megacz writes: > Russ Allbery writes: >> The problem is that it's also not uncommon for the fileserver to >> completely or nearly completely stall when shutting down, > Just curious, is this "stall" a bug in the fileserver, or something > which happens for a good reason? If so, what is th

[OpenAFS] MacOS AppleDouble excretions

2010-10-10 Thread Adam Megacz
MacOS seems to litter network shares with two kinds of files: .DS_Store (Finder data) ._filename (AppleDouble resource fork) There's a MacOS setting to disable the first kind of litter. Unfortunately it seems like there is no way to get MacOS to refrain from writing the second kind of

[OpenAFS] Re: bos killed fileserver before it was shut down cleanly.

2010-10-10 Thread Adam Megacz
Russ Allbery writes: > The problem is that it's also not uncommon for the fileserver to > completely or nearly completely stall when shutting down, Just curious, is this "stall" a bug in the fileserver, or something which happens for a good reason? If so, what is the reason? In general, I find

[OpenAFS] 1.5.75 debian client hangs at new ip address

2010-10-10 Thread Gémes Géza
Hi, I have a debian squeeze box with 1.5.75 (only the client parts from debs) installed. Everything works fine until I give a new IP address to the box. Then the afsd seems to hang (after about 20-30 seconds /afs becomes unavailable: eg. ls /afs never returns). What may be worth mentioning, is tha

Re: [OpenAFS] bos killed fileserver before it was shut down cleanly.

2010-10-10 Thread Anders Magnusson
I was probably a little bit too tired yesterday when I couldn't see the difference between 9 and 11, as other pointed out :-( Anyway, the annoying thing with fileserver getting terminated hard while still offlining volumes is a problem. A simple way to fix it would be to have a pipe between

Re: [OpenAFS] Re: OpenAFS failing rmdir performance

2010-10-10 Thread Derrick Brashear
Pretty sure either the Solaris VM system paging or Irix's had the original 'kills the fileserver RPCing in a tight loop' that resulted in this. Derrick On Oct 9, 2010, at 4:04 PM, Brandon S Allbery KF8NH wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 10/8/10 17:43 , Simon Wi

Re: [OpenAFS] bos killed fileserver before it was shut down cleanly.

2010-10-10 Thread Derrick Brashear
I'll echo the call for the backtrace, which is the potentially RT-Bug-worthy thing here. Derrick On Oct 9, 2010, at 10:38 AM, Anders Magnusson wrote: > I noticed an annoying thing yesterday; if fileserver takes more than 30*60 > seconds to > shutdown, it is killed by bos, even though it is