mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: quintaq@yahoo.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem creating filesystems (and othe operations) under 2.4.10
Date: Mon, 8 Oct 2001 16:16:47 +0100 (BST)	[thread overview]
Message-ID: <E15qc99-0000qB-00@the-village.bc.nu> (raw)
In-Reply-To: <20011008145018Z276906-760+22140@vger.kernel.org> from "quintaq@yahoo.co.uk" at Oct 08, 2001 03:50:17 PM

> I have just installed a Maxtor 30GB drive as /dev/hdc in my SuSE 7.0 system
> which has a vanilla 2.4.10 kernel.  I found that I could write the
> partition table and create a small ext2 partition for /boot plus 768MB of
> swap.  Creation of the main ext2 filesystem on /hdc7 failed (before the
> inode tables even began to be written), with "file size limit exceeded".
> The same problem recurred every time I tried - and I did try various
> combinations of partition size.  I see the same error message when trying
> to change partition table flags.  The problem is identical using fdisk,
> cfdisk and parted.  I have no file limits set in ulimit and I do not think
> that this is the problem. 
> 
> I eventually put the same drive as /dev/hdc in another box running a stock
> SuSE 2.2.16 kernel and creation of the filesystems completed without any
> problem.  I have also verified this by booting this box using SuSE's 2.2.16
> rescue kernel.
> 
> Any ideas?

Obvious one to check would be to see if when 2.4.10 acquired the page cache 
changes someone backed out the device picks up underlying file size limit bug 
fix that the -ac tree has and went to Linus.

It really sounds like that happened.

Alan


      reply	other threads:[~2001-10-08 15:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-08 14:50 quintaq
2001-10-08 15:16 ` Alan Cox [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=E15qc99-0000qB-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quintaq@yahoo.co.uk \
    /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

all inboxes | Powered by JetHome®