Date: Tue, 26 Sep 2006 09:43:14 -0400 From: Vivek Khera <vivek@khera.org> To: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: ffs snapshot lockup Message-ID: <F3975646-1B79-4B8C-A7D0-7E5093CFDEA6@khera.org> In-Reply-To: <20060925185824.GA33068@icarus.home.lan> References: <917B087C-5E13-4D7F-94FA-95CB0E5C1884@khera.org> <20060922190328.GA64849@xor.obsecurity.org> <555B84D2-520F-44D6-84D6-CF9CE7EE47C7@khera.org> <20060922203654.GA65693@xor.obsecurity.org> <A53470AA-50AF-4CB4-96BC-12B11729BB6C@khera.org> <20060925185824.GA33068@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-2-582368420 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Sep 25, 2006, at 2:58 PM, Jeremy Chadwick wrote: > This problem sounds awfully like what I reported in a recent PR. > Now I'm starting to have my doubts as to whether or not my hardware > was indeed at fault... > > http://www.freebsd.org/cgi/query-pr.cgi?pr=103435 I think my issue is a bit different -- the FS is the only thing locked up, and only the single FS that mksnap_ffs is running on. The rest of the system continues to run quite nicely as long as the process doesn't attempt to access the locked file system. In my case it has been the home directory partition, which is easy to avoid if you're root. I don't observe ethernet timeouts, etc. --Apple-Mail-2-582368420--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F3975646-1B79-4B8C-A7D0-7E5093CFDEA6>