Date: Thu, 21 Dec 2006 23:51:25 +0000 From: Chris <chrcoluk@gmail.com> To: "Kris Kennaway" <kris@obsecurity.org> Cc: Anish Mistry <mistry.7@osu.edu>, s.c.sprong@student.utwente.nl, freebsd-stable@freebsd.org Subject: Re: sshfs/nfs cause server lockup - resolved Message-ID: <3aaaa3a0612211551g3fa9c436he5a37ca2405f4b66@mail.gmail.com> In-Reply-To: <20061219215520.GA4301@xor.obsecurity.org> References: <20061123162813.L3026@volte.student.utwente.nl> <20061123192532.GA81937@xor.obsecurity.org> <3aaaa3a0612071036v2df98097ncf9c962e43e6f39d@mail.gmail.com> <200612071349.54854.mistry.7@osu.edu> <3aaaa3a0612131728t214cf77djd0a9fd47f1b12021@mail.gmail.com> <20061214013355.GA62753@xor.obsecurity.org> <3aaaa3a0612171639o1feb01c5la6f73bb1a586196a@mail.gmail.com> <20061218022132.GA77606@xor.obsecurity.org> <3aaaa3a0612191220n42534ca0w8a842bacb6085622@mail.gmail.com> <20061219215520.GA4301@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19/12/06, Kris Kennaway <kris@obsecurity.org> wrote: > On Tue, Dec 19, 2006 at 08:20:21PM +0000, Chris wrote: > > On 18/12/06, Kris Kennaway <kris@obsecurity.org> wrote: > > >On Mon, Dec 18, 2006 at 12:39:13AM +0000, Chris wrote: > > >> On 14/12/06, Kris Kennaway <kris@obsecurity.org> wrote: > > >> >On Thu, Dec 14, 2006 at 01:28:48AM +0000, Chris wrote: > > >> > > > >> >> It does make sense if thats the problem since the entire server even > > >> >> locally stops working properly, and it always follows a unexpected > > >> >> nfs/sshfs disconnection ie. network timeout. > > >> >> > > >> >> I am now running 6.2-RC that has the new file and currently at 1 day > > >> >> 11hrs uptime. > > >> > > > >> >OK, thanks for following part of the advice I gave a month ago ;) Let > > >> >us know if the problems persist. > > >> > > > >> >Kris > > >> > > > >> > > > >> > > > >> > > >> Early today the nfs hub was rebooted so had a unexpected disconnection > > >> also noted by the sshfs timeout prompt waiting for me in the terminal > > >> , was able to remount fine and no server lockup or other probolems. > > >> > > >> Current uptime is 5 days, 10:48 > > > > > >OK, good to know. > > > > > >Thanks, > > >Kris > > > > > > > > > > > > > > > > Some bad news, I was offline for a day here, then I logged in today > > reattached to screen, and was greeted with a timeout message to the > > sshfs server, at this point server still functioning fine. When I ran > > the sshfs command again it locked, with only pings responding and had > > to hard reboot it. > > > > I will setup my local machne now so I can do proper debugging for you. > > OK, it's (still) probably an sshfs bug though. > > Kris > > > Ok how to repeat the bug everytime. Works on sshfs and nfs. First. The server died again (hub having its own problems so causing lots of timeouts). This time instead of remounting I tried to ls the 2 mounts simply list empty dirs, first dir worked and 2nd dir caused lockup, so its some kind of problem with the filesystem nodes or something. With this in mind on my local box I yanked out the network cable causing a unexpected timeout, box hung, tried to do the ddb procedure but didnt work, I may have been doing it wrong. Booted local box again mounted nfs over internet and tried same thing yanked out network cable, same thing accessing the dir where nfs mount to hung server hard reboot needed. Local box using 6.2-RC as well. GENERIC kernel default make.conf. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3aaaa3a0612211551g3fa9c436he5a37ca2405f4b66>