Date: Wed, 26 Apr 2006 11:23:43 -0600 From: secmgr <security@jim-liesl.org> To: Chris Dillon <cdillon@wolves.k12.mo.us> Cc: stable@freebsd.org Subject: Re: fsck_ufs locked in snaplk Message-ID: <444FAC9F.7080209@jim-liesl.org> In-Reply-To: <20060425080932.1rv9hq0rcws4wc84@www.wolves.k12.mo.us> References: <20060423193208.N1187@woozle.rinet.ru> <20060423201732.GA74905@xor.obsecurity.org> <20060424091803.L20593@woozle.rinet.ru> <20060424215650.P36233@woozle.rinet.ru> <20060424181531.GA13774@xor.obsecurity.org> <20060425001751.S44618@woozle.rinet.ru> <20060424202859.GA18457@xor.obsecurity.org> <20060425004405.G44618@woozle.rinet.ru> <20060424205026.GA18844@xor.obsecurity.org> <20060425134418.J57625@woozle.rinet.ru> <20060425080932.1rv9hq0rcws4wc84@www.wolves.k12.mo.us>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Dillon wrote: > > I had problems with snapshots and hangs in 5.x. For that, a daily > reboot would keep the problems at bay. I upgraded to 6.0 and the > problems completely disappeared. I kept 6.0-STABLE running for weeks. > Somewhere along the line, as 6.1 approached, similar problems > re-appeared, but not exactly the same as what I had in 5.x. Now > instead of a complete system hang, individual processes will hang > while attempting to access a certain filesystem. I'm running 5.5-pre #5 and dumps using the snap option. No quotas, low usage. Nightly dumps hung last weekend, and any new dumps (till I rebooted) hung. Other process' access to the drives seemed ok, but hung dump processes were unkillable. Sorry, didn't have any debug stuff turned on, so I realize this info is of limited or maybe even no use. Hadn't seen this before. If it crops up again, I'll build a new kernel for debugging and try and get more data. thanks jim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?444FAC9F.7080209>