Date: Mon, 12 May 2003 20:24:20 -0400 (EDT) From: Garrett Wollman <wollman@lcs.mit.edu> To: Kirk McKusick <mckusick@beastie.mckusick.com> Cc: freebsd-current@freebsd.org Subject: Re: large ufs2 partitions and 'df' Message-ID: <200305130024.h4D0OKxK018085@khavrinen.lcs.mit.edu> In-Reply-To: <200305130011.h4D0BlTh038399@beastie.mckusick.com> References: <Pine.BSF.4.21.0305121435260.92065-100000@InterJet.elischer.org> <200305130011.h4D0BlTh038399@beastie.mckusick.com>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Mon, 12 May 2003 17:11:47 -0700, Kirk McKusick <mckusick@beastie.mckusick.com> said: > them in that order. Also Solaris have now done some renaming: > f_bsize => f_frsize > f_iosize => f_bsize > And Solaris has added: > f_favail /* free inodes avail to non-superuser */ > f_namemax /* maximum filename length */ Compatibility cruft for SVR4/SUS. (That's what those fields are called in `struct statvfs'; I assume Sun just uses the same structure.) f_namemax is particularly bogus. (sysconf() should be used instead, but applications must in any case be prepared for the possibility that there is no such limit.) > u_int_64 f_blocks; /* total data blocks in filesystem */ > u_int_64 f_bfree; /* free blocks in filesystem */ > int_64 f_bavail; /* free blocks avail to non-superuser */ > u_int_64 f_files; /* total file nodes in filesystem */ > u_int_64 f_ffree; /* free file nodes in filesystem */ > int_64 f_favail; /* free nodes avail to non-superuser */ SUSv3 defines explicit types, fsblkcnt_t and fsfilcnt_t, for the analogous entries in `struct statvfs', but does not appear to consider that some of them may have different signedness. It's not clear that this even makes sense, but 2**63 is a long way away. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305130024.h4D0OKxK018085>