Wow, vger categorically refuses HTML e-mail! On Tue, Oct 19, 2010 at 4:41 PM, David Nicol <davidnicol@gmail.com> wrote:> > the inode number is an "unsigned long" which on a 32 bit system may be merely 32 bits, yet btrfs allows a full 64 bits of files in a file system (which is impossible; but ZFS allows 128 bits of files, which is just silly.) > My question is, how are inode number collisions prevented on a 32-bit system, with a fs with five billion files?-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Which is a really good thing! HTML e-mails are useless and nobody should use them! I''m sure they came directly from hell. David Nicol schrieb:> Wow, vger categorically refuses HTML e-mail! > > On Tue, Oct 19, 2010 at 4:41 PM, David Nicol <davidnicol@gmail.com> wrote: >> the inode number is an "unsigned long" which on a 32 bit system may be merely 32 bits, yet btrfs allows a full 64 bits of files in a file system (which is impossible; but ZFS allows 128 bits of files, which is just silly.) >> My question is, how are inode number collisions prevented on a 32-bit system, with a fs with five billion files? > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html