All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Tackaberry <tack@auc.ca>
To: linux-kernel@vger.kernel.org
Subject: File size limit exceeded with mkfs
Date: 20 Nov 2001 11:02:18 -0500	[thread overview]
Message-ID: <1006272138.1263.3.camel@somewhere.auc.ca> (raw)

Hi everyone.  Please CC any responses to me as I'm not subscribed to
this list.

I just installed a shiny new 80GB disk as primary slave and decided to
upgrade to 2.4.14+ext3 patch.  It appears that with this kernel, and
also with 2.4.15-pre7, when trying to mkfs partitions greater than 2GB,
I get "file size limit exceeded" and mkfs aborts.  I can successfully
mkfs partitions <= 2GB.

I do not have this problem with 2.4.7; all works well.  Wondering if the
difference was ext3, I tried compiling 2.4.15-pre7 without ext3 support
and the same problem occured.

The disk is

   hdb: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63

on a dual PIII-800 (SMP kernel).  Please let me know if I can supply
additional information.

Cheers,
Jason.

-- 
Academic Computing Support Specialist         Assistant Section Editor
Algoma University College                     http://linux.com/develop
Sault Ste. Marie, Ontario                 
705-949-2301 x330                                   Personal Home Page
http://www.auc.ca                                     http://sault.org


             reply	other threads:[~2001-11-20 16:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-20 16:02 Jason Tackaberry [this message]
2001-11-20 18:33 ` File size limit exceeded with mkfs Andreas Dilger
2001-11-20 20:29   ` Jason Tackaberry
2001-11-20 20:43     ` Matti Aarnio
2001-11-20 23:56       ` Neil Brown
2001-11-20 23:35     ` Andreas Dilger
2001-11-21  0:24       ` Mohammad A. Haque
2001-11-20 23:21   ` Horst von Brand
  -- strict thread matches above, loose matches on Subject: below --
2001-11-22 10:21 Peter Seiderer

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=1006272138.1263.3.camel@somewhere.auc.ca \
    --to=tack@auc.ca \
    --cc=linux-kernel@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.