From: Andrew Morton <akpm@zip.com.au>
To: "H . J . Lu" <hjl@lucon.org>
Cc: tytso@thunk.org, linux-mips@oss.sgi.com
Subject: Re: Does e2fsprogs-1.26 work on mips?
Date: Sat, 23 Mar 2002 16:21:50 -0800 [thread overview]
Message-ID: <3C9D1C1D.E30B9B4B@zip.com.au> (raw)
In-Reply-To: 20020323140728.A4306@lucon.org
"H . J . Lu" wrote:
>
> I got
>
> [root@localhost e2fsprogs-1.26]# ./e2fsck/e2fsck -f /dev/hda1
> e2fsck 1.26 (3-Feb-2002)
> Pass 1: Checking inodes, blocks, and sizes
> File size limit exceeded
>
> on Linux/mipsel. /dev/hda1 is a 7GB ext3 partition. e2fsprogs-1.23
> works fine. Strace
>
>
Common problem - it's due to internal API changes in resource
limits. You need to ensure that your maximum file size
is set to `unlimited'. Kernel is currently applying file
size limits to block devices (which is broken) and I
think e2fsprogs' attempt to set sile size limits to
RLIM_INFINITY gets broken by a consipiracy between the
kernel change and glibc headers.
next prev parent reply other threads:[~2002-03-24 0:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-23 22:07 Does e2fsprogs-1.26 work on mips? H . J . Lu
2002-03-24 0:21 ` Andrew Morton [this message]
[not found] ` <20020323221627.A10953@lucon.org>
[not found] ` <3C9D7A42.B106C62D@zip.com.au>
2002-03-24 9:28 ` H . J . Lu
2002-03-25 5:31 ` Theodore Tso
2002-03-25 5:43 ` Andrew Morton
2002-03-26 6:54 ` Theodore Tso
2002-03-26 10:51 ` Paul Mackerras
2002-03-26 10:51 ` Paul Mackerras
2002-03-25 17:17 ` H . J . Lu
-- strict thread matches above, loose matches on Subject: below --
2002-03-25 10:52 Peter Hartley
2002-03-25 17:07 ` H . J . Lu
2002-03-25 19:00 Peter Hartley
2002-03-25 19:11 ` H . J . Lu
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=3C9D1C1D.E30B9B4B@zip.com.au \
--to=akpm@zip.com.au \
--cc=hjl@lucon.org \
--cc=linux-mips@oss.sgi.com \
--cc=tytso@thunk.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.