From: Frank van Maarseveen <frankvm@frankvm.com>
To: linux-kernel@vger.kernel.org
Subject: JBD: ext2online wants too many credits (744 > 256)
Date: Mon, 7 May 2007 00:26:26 +0200 [thread overview]
Message-ID: <20070506222626.GA25632@janus> (raw)
2.6.20.6, FC4:
I created a 91248k ext3 fs with 4k blocksize:
| mke2fs -j -b 4096 /dev/vol1/project
| mke2fs 1.38 (30-Jun-2005)
| Filesystem label=
| OS type: Linux
| Block size=4096 (log=2)
| Fragment size=4096 (log=2)
| 23552 inodes, 23552 blocks
| 1177 blocks (5.00%) reserved for the super user
| First data block=0
| Maximum filesystem blocks=25165824
| 1 block group
| 32768 blocks per group, 32768 fragments per group
| 23552 inodes per group
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Next, I tried to resize it to about 3G using ext2online while mounted:
| # ext2online /dev/vol1/project
| 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
At that time the kernel said:
|JBD: ext2online wants too many credits (744 > 256)
What is the limitation I should be aware of? Has it something to do with
the journal log size?
The size actually did increase a bit, to 128112k.
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)
--
Frank
next reply other threads:[~2007-05-06 22:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 22:26 Frank van Maarseveen [this message]
2007-05-07 4:40 ` JBD: ext2online wants too many credits (744 > 256) Andrew Morton
2007-05-07 13:53 ` Frank van Maarseveen
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=20070506222626.GA25632@janus \
--to=frankvm@frankvm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox