Date: Sun, 16 Oct 2005 15:57:55 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: dillon@apollo.backplane.com Cc: freebsd-current@FreeBSD.org, obrien@FreeBSD.org Subject: Re: [PANIC] ufs_dirbad: bad dir Message-ID: <200510162257.j9GMvtIo060326@gw.catspoiler.org> In-Reply-To: <200510162244.j9GMimWx037396@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 16 Oct, Matthew Dillon wrote: > Ach. sigh. Another false alarm. Sorry. The code is fine. It's > because the 'end' block is calculated inclusively, e.g. > end_lbn = start_lbn + len - 1. I'm still investigating it. > > There is a bug if the range reallocblks is called with spans > more then two blockmaps, but I don't think that case can occur in real > life due to limitations in the range passed by the caller. Probably > worth a KASSERT, though. Is there any correlation between this problem and the file system block size? I've *never* encountered this problem, but I've only used block sizes up to 16K, and mostly just 4K and 8K. I seem to have a dim memory of a mention of problems of some sort with large block sizes.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510162257.j9GMvtIo060326>