Date: Thu, 20 May 2010 19:19:52 +0200 From: Jan Henrik Sylvester <me@janh.de> To: Derrick Brashear <shadow@gmail.com> Cc: afs-list freebsd <freebsd-afs@freebsd.org>, Benjamin Kaduk <kaduk@mit.edu> Subject: Re: AFS on FreeBSD 8? Message-ID: <4BF56F38.4040008@janh.de> In-Reply-To: <AANLkTin_RGNLOzP2X2WaJwwq8Ae7pKJQbA6P6Wbth4U3@mail.gmail.com> References: <558186334.2619.1271175586732.JavaMail.root@thunderbeast.private.linuxbox.com> <4BC4A5F1.6050406@janh.de> <alpine.GSO.1.10.1004131314070.29136@multics.mit.edu> <4BC5EEB5.5050109@janh.de> <alpine.GSO.1.10.1004141242470.29136@multics.mit.edu> <4BE01AF0.3080309@janh.de> <alpine.GSO.1.10.1005041225120.29136@multics.mit.edu> <4BF2B962.50408@janh.de> <alpine.GSO.1.10.1005181201010.29136@multics.mit.edu> <4BF2D461.8030302@janh.de> <AANLkTin_RGNLOzP2X2WaJwwq8Ae7pKJQbA6P6Wbth4U3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/18/10 20:14, Derrick Brashear wrote: > On Tue, May 18, 2010 at 1:54 PM, Jan Henrik Sylvester<me@janh.de> wrote: >> On amd64, the listing of the directories was instant unlike on i386. Reading >> (small) files caused no problems, but I was able to crash the machine >> accessing some weird entry (some object that OpenAFS on Linux shows with "?" >> for the file permissions) and -- more realistically -- deadlock all access >> to afs upon trying to copy a large file to afs. > > does > cmdebug (yourhost) > return anything? - change to some afs-directory cmdebug: nothing - change to some afs-directory that uses krb login cmdebug: crashes the machine instantly - repeat both steps after reboot cmdebug: nothing - copying a small file cmdebug: reports something (I lost it, looked as if it was expected) - eventually copying of the small file finished (took very long) cmdebug: nothing - copying a large file cmdebug: nothing - copying takes forever (does nothing after a second, no reading) cmdebug: nothing >>> I expect that you will find AFS more usable if you set >>> kern.smp.disabled=1 in /boot/loader.conf, which will make your machine >>> effectively single-processor. >> >> I just tried that and copying a large file to afs caused a deadlock of afs, >> too. I guess it is not just SMP. The "protocol" above was with SMP enabled. I could repeat it with SMP disabled if you expect anything from it. (I did observe the same behavior with SMP disabled.) On a different machine, I was just changing afs directories and listing them calling cmdebug a few times in between. Nothing happened, but when I came back to the machine a few minutes later, it had deadlocked completely -- without copying data at all. I just found the first machine that I tried to reboot with its stalled copy process is now hanging completely, too. I would have tried to narrow down the circumstances that cause deadlocks, if both of the machines in front of me were not crashing so often... Cheers, Jan Henrik
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BF56F38.4040008>