From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: strange 3.16.3 problem
Date: Tue, 21 Oct 2014 09:50:37 +0000 (UTC) [thread overview]
Message-ID: <pan$87a32$ab14c0c8$d31af00$391cbfd4@cox.net> (raw)
In-Reply-To: 54456EB0.9020503@inwind.it
Goffredo Baroncelli posted on Mon, 20 Oct 2014 22:21:04 +0200 as
excerpted:
> On 10/20/2014 07:37 PM, Robert White wrote:
>> On 10/18/2014 04:41 PM, Russell Coker wrote:
> [...]
>> Also you said that you are using a 32bit user space "copied from
>> another server" under a 64bit kernel. Is the "ls" command a 32 bit
>> executable then?
>
> 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.
@ Russ, are you mounting with inode_cache? If so, definitely try running
without it and see if it changes the results.
(FWIW I wish that mount option would just go away as it would definitely
remove an invitation to a Russian roulette party with their data for the
unwary, but I suppose there's someone paying some bills somewhere that
wants it kept for some specific use-case where the performance gain must
be worth the calculated risk, thus continuing that invitation to data
Russian roulette for everyone else.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-10-21 9:50 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 [this message]
2014-10-21 10:16 ` inode_cache " Roman Mamedov
2014-10-21 12:08 ` Duncan
2014-10-21 16:40 ` Goffredo Baroncelli
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='pan$87a32$ab14c0c8$d31af00$391cbfd4@cox.net' \
--to=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.