From: Theodore Ts'o <tytso@mit.edu>
To: "Dilger, Andreas" <andreas.dilger@intel.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: "make check" broken on maint branch?
Date: Thu, 31 Oct 2013 23:21:15 -0400 [thread overview]
Message-ID: <20131101032115.GA14263@thunk.org> (raw)
In-Reply-To: <20131101023556.GA28605@gmail.com>
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.
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.
- Ted
next prev parent reply other threads:[~2013-11-01 3:21 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 [this message]
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
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=20131101032115.GA14263@thunk.org \
--to=tytso@mit.edu \
--cc=andreas.dilger@intel.com \
--cc=linux-ext4@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.