All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank van Maarseveen <frankvm@frankvm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Frank van Maarseveen <frankvm@frankvm.com>,
	linux-kernel@vger.kernel.org,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: JBD: ext2online wants too many credits (744 > 256)
Date: Mon, 7 May 2007 15:53:10 +0200	[thread overview]
Message-ID: <20070507135309.GA32476@janus> (raw)
In-Reply-To: <20070506214014.8b7451ba.akpm@linux-foundation.org>

On Sun, May 06, 2007 at 09:40:14PM -0700, Andrew Morton wrote:
> On Mon, 7 May 2007 00:26:26 +0200 Frank van Maarseveen <frankvm@frankvm.com> wrote:
> 
> > Steps to reproduce:
> > Create a 3G partition, say /dev/vol1/project
> > mke2fs -j -b 4096 /dev/vol1/project 22812
> > mount it
> > ext2online /dev/vol1/project said:
> > 
> > | ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b
> > | ext2online: ext2_ioctl: No space left on device
> > | 
> > | ext2online: unable to resize /dev/mapper/vol1-project
> > 
> > kernel said:
> > 
> > | JBD: ext2online wants too many credits (721 > 256)

There's a threshold for the problem depending on the initial
size. This one fails:

	mke2fs -j -b 4096 /dev/<3GB-blockdev> 32768
	(mount + ext2online or resize2fs)
	kernel: JBD: resize2fs wants too many credits (1034 > 1024)

Add one block to the initial mke2fs (32768+1 == 32769) and the
problem is gone.

Without the -b 4096 there's another resize problem

	mke2fs -j /dev/loop1 2048
	mount /dev/loop1 /1
	resize2fs /dev/loop1

says:
	resize2fs 1.40-WIP (14-Nov-2006)
	Filesystem at /dev/loop1 is mounted on /1; on-line resizing required
	old desc_blocks = 1, new_desc_blocks = 12
	Performing an on-line resize of /dev/loop1 to 3072000 (1k) blocks.
	resize2fs: Invalid argument While trying to add group #256

and the kernel says:

May  7 15:36:08 lokka EXT3-fs warning (device loop1): verify_reserved_gdb: 
May  7 15:36:08 lokka reserved GDT 10 missing grp 1 (8202)
May  7 15:36:08 lokka  

After that, the filesystem has been resized to 2GB. I recall a 2G
(?) limit for ext3 resizing with 1k blocksize but trying the above with
4096 1k blocks seems to work. fsck says it's ok all the time.

-- 
Frank

  reply	other threads:[~2007-05-07 13:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-06 22:26 JBD: ext2online wants too many credits (744 > 256) Frank van Maarseveen
2007-05-07  4:40 ` Andrew Morton
2007-05-07 13:53   ` Frank van Maarseveen [this message]
2007-05-07 18:51   ` Andreas Dilger
2007-05-07 14:27 ` Theodore Tso
2007-05-07 14:46   ` david
2007-05-07 15:50     ` Theodore Tso
2007-05-07 21:06       ` Andreas Dilger

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=20070507135309.GA32476@janus \
    --to=frankvm@frankvm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ext4@vger.kernel.org \
    --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.