In message <[EMAIL PROTECTED]>, Brooks Davis writes:
>> I saw similarly bogus sector (block) numbers when I first debugged this >> problem. They were caused by missing prototypes. 32-bit block numbers >> were passed to unprototyped functions that expected daddr_t block numbers. >> When daddr_t was changed to 64 bits, there was garbage in the top 32 bits. >>=20 >> dump doesn't compile cleanly at a high WARNS level, so now would be a good >> time to WARNSify it. > >That sounds like a good idea. If someone else doesn't get there first, >I'll take a look at that soon. If nothing else, there's the plane trip >down to SFO for USENIX. Please, if you do so, do it relative to the UFS2 patch, there is little point in making it harder for both yourself and Kirk than absolutely necessary... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
