From: David Nicol <davidnicol@gmail.com>
To: BTRFS MAILING LIST <linux-btrfs@vger.kernel.org>
Subject: Re: newbie question about inode numbers
Date: Wed, 20 Oct 2010 08:51:22 -0500 [thread overview]
Message-ID: <AANLkTimHQfszXJs9wEff-j9L4+kcOaG385qACK0wzkLs@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinE03sBL=K3xfL41VZyFLhafNxHooheTv1PSQTD@mail.gmail.com>
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?
next parent reply other threads:[~2010-10-20 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinE03sBL=K3xfL41VZyFLhafNxHooheTv1PSQTD@mail.gmail.com>
2010-10-20 13:51 ` David Nicol [this message]
2010-10-20 13:55 ` newbie question about inode numbers Felix Blanke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimHQfszXJs9wEff-j9L4+kcOaG385qACK0wzkLs@mail.gmail.com \
--to=davidnicol@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).