From: Eric Sandeen <sandeen@sandeen.net>
To: aurfalien <aurfalien@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: inode64 and Firefox
Date: Tue, 09 Jul 2013 09:09:16 -0500 [thread overview]
Message-ID: <51DC198C.70106@sandeen.net> (raw)
In-Reply-To: <C7F53623-AA6A-4FD2-90A6-52BBA6562D10@gmail.com>
On 7/9/13 9:08 AM, aurfalien wrote:
>
> On Jul 9, 2013, at 6:54 AM, Eric Sandeen wrote:
>
>> On 7/9/13 8:37 AM, aurfalien wrote:
>>> Before I dig deeper, wondering if any one has issues running Firefox v22 from an XFS file system mounted using inode64 option?
>>
>> I've not tried it, but first question - 32-bit or 64-bit firefox?
>
> Its 32 bit FF. Thunderbird also has issues. Too bad :(
Ok, below was for 64-bit, even!
I'd file a bug w/ them, it can't be that hard to fix. Modern filesystems have 64 bit inodes, they should handle it!
-Eric
> Stuck in the stone age. Got a 24TB fs functioning as a home dir for ~100 pplz that I would like to modernize.
>
>> However, this isn't encouraging:
>>
>> $ file /usr/lib64/firefox/firefox
>> /usr/lib64/firefox/firefox: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, stripped
>>
>> $ ./summarise_stat.pl /usr/lib64/firefox/firefox
>> 1 100.0% use 32-bit stat() family interfaces only
>>
>> sooo if my perl script is to be believed, it may be problematic, depending on how serious a stat() failure is.
>>
>> -Eric
>
> Thanks for the feedback.
>
> - aurf
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-07-09 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 13:37 inode64 and Firefox aurfalien
2013-07-09 13:54 ` Eric Sandeen
2013-07-09 14:08 ` aurfalien
2013-07-09 14:09 ` Eric Sandeen [this message]
2013-07-09 14:35 ` Stan Hoeppner
2013-07-09 14:54 ` aurfalien
2013-07-10 3:42 ` inode64 and Firefox - update aurfalien
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=51DC198C.70106@sandeen.net \
--to=sandeen@sandeen.net \
--cc=aurfalien@gmail.com \
--cc=xfs@oss.sgi.com \
/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