Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 Aug 2002 11:05:01 +1000
From:      Gregory Bond <gnb@itga.com.au>
To:        Danny Carroll <danny-bgtrk@dannysplace.net>
Cc:        stable@FreeBSD.ORG
Subject:   Re: Bug in Zoo? Or is it in ls or ffs? 
Message-ID:  <200208140105.LAA06018@lightning.itga.com.au>
In-Reply-To: Your message of 13 Aug 2002 15:43:00 %2B0200.

next in thread | raw e-mail | index | archive | help
> As you can see the size is not taken up in disk space so I suspect the
> bug is in ls.  DU, DF and the left hand column of LS looks OK.

No, it's a probably a bug in zoo, lseek()ing to a negative offset and/or
getting long <-> long long conversions wrong.  This gets turned into a large
positive offset.  (4294967352 is 2^32 + 56)

Then when zoo writes a single byte, the filesystem has to allocate single and
double-indirect blocks, plus the data, which is where the 40 used blocks comes
from. This behaviour doesn't force the filesystem to allocate of all the 4G of
intervening holes.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200208140105.LAA06018>