From: Goffredo Baroncelli <kreijack@inwind.it>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: strange 3.16.3 problem
Date: Tue, 21 Oct 2014 18:40:19 +0200 [thread overview]
Message-ID: <54468C73.1070108@inwind.it> (raw)
In-Reply-To: <pan$87a32$ab14c0c8$d31af00$391cbfd4@cox.net>
On 10/21/2014 11:50 AM, Duncan wrote:
> Goffredo Baroncelli posted on Mon, 20 Oct 2014 22:21:04 +0200 as
> excerpted:
>
[...]
>> >
>> > Could this be related to the inode overflow in 32 bit system (see
>> > inode_cache options) ? If so running a 64bit "ls -i" should work....
> Good point. Russell might just owe you a beverage of choice. =:^)
>
> The inode_cache mount option isn't recommended for any bitness.
Hi Ducan,
could you elaborate this sentence ? From my understanding
inode_cache is *needed* on 32bit system in order to avoid inode number
overflow. Why are you saying that it is not recommended ?
Even if there are bugs, these have to be corrected. A bugs cannot be
a reason to remove a needed option.
Inode exhaustion is worse than a slowness... Otherwise BTRFS would be not
suitable to a 32 bit system... But please tell me your opinion because may
be I misunderstood something...
BR
G.Baroncelli
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2014-10-21 16:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 3:54 strange 3.16.3 problem Russell Coker
[not found] ` <CAHGunUkzXZ-ybUR_y3tHzGwtn_45gq8YQJyEqteBX3zqWzUakA@mail.gmail.com>
2014-10-18 10:29 ` Russell Coker
2014-10-18 13:33 ` Robert White
2014-10-18 23:41 ` Russell Coker
2014-10-19 5:37 ` Duncan
2014-10-19 10:19 ` Duncan
2014-10-20 17:37 ` Robert White
2014-10-20 20:21 ` Goffredo Baroncelli
2014-10-21 9:50 ` Duncan
2014-10-21 10:16 ` inode_cache " Roman Mamedov
2014-10-21 12:08 ` Duncan
2014-10-21 16:40 ` Goffredo Baroncelli [this message]
2014-10-22 7:12 ` Duncan
2014-10-19 10:46 ` Chris Samuel
2014-10-20 4:38 ` Duncan
2014-10-20 13:02 ` Zygo Blaxell
2014-10-20 13:19 ` Austin S Hemmelgarn
2014-10-21 10:13 ` Russell Coker
2014-10-21 10:42 ` Russell Coker
2014-10-21 15:23 ` strange 3.16.3 problem (er... never mind 8-) Robert White
2014-10-21 12:25 ` strange 3.16.3 problem Duncan
2014-10-21 15:10 ` Robert White
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=54468C73.1070108@inwind.it \
--to=kreijack@inwind.it \
--cc=1i5t5.duncan@cox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.