From: "Dilger, Andreas" <andreas.dilger@intel.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: "make check" broken on maint branch?
Date: Fri, 1 Nov 2013 18:24:09 +0000 [thread overview]
Message-ID: <CE98BD77.7C15F%andreas.dilger@intel.com> (raw)
In-Reply-To: <20131101032115.GA14263@thunk.org>
On 2013/10/31 9:21 PM, "Theodore Ts'o" <tytso@mit.edu> wrote:
>On Fri, Nov 01, 2013 at 10:35:56AM +0800, Zheng Liu wrote:
>> Hi Andreas,
>>
>> On Thu, Oct 31, 2013 at 09:35:25PM +0000, Dilger, Andreas wrote:
>> > I tried to add in a "truncate -s $SIZE_2 $TMPFILE", but it complains
>>that
>> > it isn't able to truncate the file in /tmp to 2TB:
>> >
>> > truncating `/tmp/e2fsprogs-tmp.OGxb09' at 2199023255552 bytes: File
>>too
>> > large
>> >
>> > Testing manually, it seems I'm not allowed to create a file in tmpfs
>>larger
>> > than 256GB. How large does this file need to be for this test to be
>>valid?
>> >
>> > Anyone else seen these problems, or do I need to dig in further?
>>
>> Yes, I also can see these problems.
>
>Hmm.... it works for me. Run while r_64bit_big_expand is running:
>
>% ls -l tmp
>...
>24896 -rw-r--r--. 1 tytso tytso 2199023255552 Oct 31 23:17
>e2fsprogs-tmp.pkOcCc
>...
>
>% df /tmp
>Filesystem 1K-blocks Used Available Use% Mounted on
>tmpfs 3216420 26008 3190412 1% /tmp
>
>What version of the kernel are you running? I am using 3.12-rc5 plus
>the ext4 dev tree, so I'm using a pretty recent kernel.
It was in the original email - the failing systems are both RHEL6,
2.6.32-358.11.1.el6 (w/4GB RAM) and 2.6.32-279.5.1.el6 (w/ 2GB RAM).
Both fail to create files in tmpfs larger than 256GB.
>Maybe this is a relatively new feature of tmpfs? If so, I should
>probably change the test so that it's a bit more portable on people
>using older kernels.
Looking at the s_maxbytes value in current kernels shows me that it was
changed in v3.0-7280-g285b2c4 and has not been backported to the RHEL 6
kernel that I'm using at least.
Cheers, Andreas
--
Andreas Dilger
Lustre Software Architect
Intel High Performance Data Division
prev parent reply other threads:[~2013-11-01 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 21:35 "make check" broken on maint branch? Dilger, Andreas
2013-11-01 2:35 ` Zheng Liu
2013-11-01 3:21 ` Theodore Ts'o
2013-11-01 13:12 ` Zheng Liu
2013-11-01 16:48 ` Theodore Ts'o
2013-11-04 6:20 ` Zheng Liu
2013-11-01 18:24 ` Dilger, Andreas [this message]
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=CE98BD77.7C15F%andreas.dilger@intel.com \
--to=andreas.dilger@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).