4:23 a.m.
What does this mean?
[root@cobra ~]# /usr/sbin/ext2online /dev/cobra/root
ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b
ext2online: group 0, block 2 not reserved
ext2online: unable to resize /dev/mapper/cobra-root
--
Ivan Gyurdiev <ivg2(a)cornell.edu>
Cornell University
7:03 a.m.
On 7/7/05, Ivan Gyurdiev <ivg2(a)cornell.edu> wrote:
What does this mean?
[root@cobra ~]# /usr/sbin/ext2online /dev/cobra/root
ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b
ext2online: group 0, block 2 not reserved
ext2online: unable to resize /dev/mapper/cobra-root
Did you increase the size first?
lvextend -L+NG /dev/vg/lv
7:12 a.m.
Justin Conover wrote:
On 7/7/05, Ivan Gyurdiev <ivg2(a)cornell.edu> wrote:
> What does this mean?
>
> [root@cobra ~]# /usr/sbin/ext2online /dev/cobra/root
> ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b
> ext2online: group 0, block 2 not reserved
>
> ext2online: unable to resize /dev/mapper/cobra-root
>
Did you increase the size first?
lvextend -L+NG /dev/vg/lv
My experience is that when you get the "block N not reserved" message it
is because you are attempting to increase the size of the filesystem
beyond what can be done online.
An EXT[2|3] filesystem, when created, has a hard limit on the size to
which it can grow while mounted - to grow beyond this size requires the
file system to be unmounted so that additional data structures can be
created within it. I believe the rule of thumb is that you can double
the size of the file system from what it was originally while it is
mounted, but you cannot go beyond that without unmounting it and
extending it.
XFS does not have this restriction, and IIRC neither does ReiserFS.
So, the upshot is that the file system will have to be unmounted and
extended. If this is the rootfs then this will have to be done from a
rescue disk or from the initrd (what I have done is to create an initrd
that extends the partition to the maximum size of the partition it is
in, and then I can simply invoke that initrd when needed.)
7:24 a.m.
My experience is that when you get the "block N not
reserved" message it
is because you are attempting to increase the size of the filesystem
beyond what can be done online.
I doubt that, because I am trying to resize the root fs by 3-4G,
and earlier I resized my home fs by 10G without a problem.
An EXT[2|3] filesystem, when created, has a hard limit on the size to
which it can grow while mounted - to grow beyond this size requires the
file system to be unmounted so that additional data structures can be
created within it. I believe the rule of thumb is that you can double
the size of the file system from what it was originally while it is
mounted, but you cannot go beyond that without unmounting it and
extending it.
In which case my resize should have worked... it's a minor increase,
about 25% of the current size.
XFS does not have this restriction, and IIRC neither does ReiserFS.
So, the upshot is that the file system will have to be unmounted and
extended. If this is the rootfs then this will have to be done from a
rescue disk or from the initrd (what I have done is to create an initrd
that extends the partition to the maximum size of the partition it is
in, and then I can simply invoke that initrd when needed.)
I can try the rescue disk, but the "block reserved" message is not
helpful at all when trying to determine the cause of the problem.
--
Ivan Gyurdiev <ivg2(a)cornell.edu>
Cornell University
8:05 a.m.
On 7/7/05, Ivan Gyurdiev <ivg2(a)cornell.edu> wrote:
> My experience is that when you get the "block N not reserved" message it
> is because you are attempting to increase the size of the filesystem
> beyond what can be done online.
I doubt that, because I am trying to resize the root fs by 3-4G,
and earlier I resized my home fs by 10G without a problem.
How large was your / fs to begin with?
Also, do you see anything in dmesg like this:
""JBD: ext2online wants too many credits (2050 > 2048)"
8:43 a.m.
On Thu, 2005-07-07 at 08:05 -0500, Justin Conover wrote:
On 7/7/05, Ivan Gyurdiev <ivg2(a)cornell.edu> wrote:
>
> > My experience is that when you get the "block N not reserved" message
it
> > is because you are attempting to increase the size of the filesystem
> > beyond what can be done online.
>
> I doubt that, because I am trying to resize the root fs by 3-4G,
> and earlier I resized my home fs by 10G without a problem.
How large was your / fs to begin with?
It's about 14 G, and I want to resize it go 18.
Also, do you see anything in dmesg like this:
""JBD: ext2online wants too many credits (2050 > 2048)"
No.
9:04 a.m.
On Thu, 2005-07-07 at 09:43 -0400, Ivan Gyurdiev wrote:
On Thu, 2005-07-07 at 08:05 -0500, Justin Conover wrote:
> How large was your / fs to begin with?
It's about 14 G, and I want to resize it go 18.
From 'man ext2online':
With no filesystem preparation, it is always possible to
resize to the
next 256MB boundary for 1k filesystems, the next 2GB boundary for for
2k filesystems, and the next 16GB boundary for 4k filesystems. By
using the ext2prepare(8) program on an unmounted filesystem, it is pos-
sible for ext2online to increase the size of a mounted ext2 filesystem
to almost any size.
Sounds like you have a 4k filesystem, which means the most you could do
unprepared is 16GB.
--
Ignacio Vazquez-Abrams <ivazquez(a)ivazquez.net>
http://fedora.ivazquez.net/
gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72
9:10 a.m.
> using the ext2prepare(8) program on an unmounted
filesystem, it is pos-
> sible for ext2online to increase the size of a mounted ext2 filesystem
> to almost any size.
So I need to unmount the filesystem in order to do an online
resize? That's... rather strange :)
And I need to find out about it from a manpage... not very friendly.
10:12 a.m.
On Thu, 2005-07-07 at 10:10 -0400, Ivan Gyurdiev wrote:
And I need to find out about it from a manpage... not very friendly.
Where else would you expect to find usage information about a command?
--
Jesse Keating RHCE (geek.j2solutions.net)
Fedora Legacy Team (www.fedoralegacy.org)
GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub)
Was I helpful? Let others know:
http://svcs.affero.net/rm.php?r=jkeating
10:22 a.m.
On Wed, 2005-07-06 at 08:12 -0700, Jesse Keating wrote:
On Thu, 2005-07-07 at 10:10 -0400, Ivan Gyurdiev wrote:
> And I need to find out about it from a manpage... not very friendly.
>
Where else would you expect to find usage information about a command?
I would expect an error message that makes more sense to
be printed by the application. It should check if I'm trying
to do something like that, and warn that it won't work.
10:45 a.m.
On Thu, 2005-07-07 at 11:22 -0400, Ivan Gyurdiev wrote:
I would expect an error message that makes more sense to
be printed by the application. It should check if I'm trying
to do something like that, and warn that it won't work.
We all wish errors could be more verbose. Bugzilla is available to you
for RFEs.
--
Jesse Keating RHCE (geek.j2solutions.net)
Fedora Legacy Team (www.fedoralegacy.org)
GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub)
Was I helpful? Let others know:
http://svcs.affero.net/rm.php?r=jkeating
10:13 a.m.
On Thu, 2005-07-07 at 10:10 -0400, Ivan Gyurdiev wrote:
So I need to unmount the filesystem in order to do an online
resize? That's... rather strange :)
Try resizing to say 15.5 gigs or something. Below the 16GB mark to
prove/disprove this theory.
--
Jesse Keating RHCE (geek.j2solutions.net)
Fedora Legacy Team (www.fedoralegacy.org)
GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub)
Was I helpful? Let others know:
http://svcs.affero.net/rm.php?r=jkeating
10:22 a.m.
On Wed, 2005-07-06 at 08:13 -0700, Jesse Keating wrote:
On Thu, 2005-07-07 at 10:10 -0400, Ivan Gyurdiev wrote:
> So I need to unmount the filesystem in order to do an online
> resize? That's... rather strange :)
Try resizing to say 15.5 gigs or something. Below the 16GB mark to
prove/disprove this theory.
The theory is correct.. it stops working exactly at 16G
10:45 a.m.
On 7/7/05, Ivan Gyurdiev <ivg2(a)cornell.edu> wrote:
On Wed, 2005-07-06 at 08:13 -0700, Jesse Keating wrote:
> On Thu, 2005-07-07 at 10:10 -0400, Ivan Gyurdiev wrote:
> > So I need to unmount the filesystem in order to do an online
> > resize? That's... rather strange :)
>
> Try resizing to say 15.5 gigs or something. Below the 16GB mark to
> prove/disprove this theory.
The theory is correct.. it stops working exactly at 16G
Does Fedora do 4k by default? Does this also mean that after he added
another 15.5, if he wanted to increase again he can go up to 15.5 or
am I reading that incorrectly?
5:30 p.m.
On 7/7/05, Justin Conover <justin.conover(a)gmail.com> wrote:
Does Fedora do 4k by default? Does this also mean that after he
added
another 15.5, if he wanted to increase again he can go up to 15.5 or
am I reading that incorrectly?
Pretty sure you are reading that incorrectly.
think of it as a head room limit associated with filesystem metadata.
For any filesystem of size X, where X is between (n)*16 Gb and
(n+1)*16 Gb where n is an a positive integer, the same amount of
headroom is avaliable for filesystem metadata. The online resize can
move the value of X only up to the (n+1)*16 Gb limit, no matter what X
actually is. Anything beyond that boundary requires additional
metadata headroom which can only be added offline.
So a 14 Gig filesystem and a 15.5 Gig filesystem, can both only be
online resized upto 16 Gig. Similarly a 23 and a 17 Gig filesystem
can only be brought up to 32Gig, which is the next 16 Gig increment.
-jef"yeah for algebra!"spaleta
7:38 p.m.
On 7/7/05, Jeff Spaleta <jspaleta(a)gmail.com> wrote:
On 7/7/05, Justin Conover <justin.conover(a)gmail.com> wrote:
> Does Fedora do 4k by default? Does this also mean that after he added
> another 15.5, if he wanted to increase again he can go up to 15.5 or
> am I reading that incorrectly?
Pretty sure you are reading that incorrectly.
think of it as a head room limit associated with filesystem metadata.
For any filesystem of size X, where X is between (n)*16 Gb and
(n+1)*16 Gb where n is an a positive integer, the same amount of
headroom is avaliable for filesystem metadata. The online resize can
move the value of X only up to the (n+1)*16 Gb limit, no matter what X
actually is. Anything beyond that boundary requires additional
metadata headroom which can only be added offline.
So a 14 Gig filesystem and a 15.5 Gig filesystem, can both only be
online resized upto 16 Gig. Similarly a 23 and a 17 Gig filesystem
can only be brought up to 32Gig, which is the next 16 Gig increment.
-jef"yeah for algebra!"spaleta
Well I guess I'm still confused :)
If you run vgdisplay and you have lets say 200GB free, you can still
extend an lv to any size you want up to 200GB, correct?
7:53 p.m.
On 7/7/05, Justin Conover <justin.conover(a)gmail.com> wrote:
Well I guess I'm still confused :)
If you run vgdisplay and you have lets say 200GB free, you can still
extend an lv to any size you want up to 200GB, correct?
What does vgdisplay have anything to do with the limitations of ext2online?
No wonder you are confused, you aren't even sure which program the
rest of the people in the thread are talking about.
-jef
11:23 p.m.
On 7/7/05, Jeff Spaleta <jspaleta(a)gmail.com> wrote:
On 7/7/05, Justin Conover <justin.conover(a)gmail.com> wrote:
> Well I guess I'm still confused :)
>
> If you run vgdisplay and you have lets say 200GB free, you can still
> extend an lv to any size you want up to 200GB, correct?
What does vgdisplay have anything to do with the limitations of ext2online?
No wonder you are confused, you aren't even sure which program the
rest of the people in the thread are talking about.
-jef
What I am simply saying is if you have a large some of free space,
lvextend a lv and then run ext2online lv what does the 16GB limit
doing? I know I have lvextend a 100GB lv to 200GB on my server at
home. So I'm simply trying to understand what the 16GB limit is?
If it helps, I've been in the office since 7:30am and it is now
11:30pm and I'm still working on db2/ldap/websphere stuff so my brain
is almost fried, if it is still actually there ;)
12:21 a.m.
On Thu, 2005-07-07 at 23:23 -0500, Justin Conover wrote:
What I am simply saying is if you have a large some of free space,
lvextend a lv and then run ext2online lv what does the 16GB limit
doing? I know I have lvextend a 100GB lv to 200GB on my server at
home. So I'm simply trying to understand what the 16GB limit is?
It's for, as the subject says, ext2online, which is responsible for
resizing the actual filesystem.
--
Ignacio Vazquez-Abrams <ivazquez(a)ivazquez.net>
http://fedora.ivazquez.net/
gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72
5:40 p.m.
On Thu, 2005-07-07 at 23:23 -0500, Justin Conover wrote:
On 7/7/05, Jeff Spaleta <jspaleta(a)gmail.com> wrote:
> On 7/7/05, Justin Conover <justin.conover(a)gmail.com> wrote:
> > Well I guess I'm still confused :)
> >
> > If you run vgdisplay and you have lets say 200GB free, you can still
> > extend an lv to any size you want up to 200GB, correct?
>
> What does vgdisplay have anything to do with the limitations of ext2online?
> No wonder you are confused, you aren't even sure which program the
> rest of the people in the thread are talking about.
>
> -jef
>
What I am simply saying is if you have a large some of free space,
lvextend a lv and then run ext2online lv what does the 16GB limit
doing? I know I have lvextend a 100GB lv to 200GB on my server at
home. So I'm simply trying to understand what the 16GB limit is?
You can extend the LV, sure. But you can't extend the filesystem past
16GB, because the block map inside the file system can't be resized (at
least not while the filesystem is mounted, no idea about otherwise), and
it can only address 16GB.
--
Peter
7:21 a.m.
On Thu, 2005-07-07 at 07:03 -0500, Justin Conover wrote:
On 7/7/05, Ivan Gyurdiev <ivg2(a)cornell.edu> wrote:
> What does this mean?
>
> [root@cobra ~]# /usr/sbin/ext2online /dev/cobra/root
> ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b
> ext2online: group 0, block 2 not reserved
>
> ext2online: unable to resize /dev/mapper/cobra-root
>
Did you increase the size first?
lvextend -L+NG /dev/vg/lv
Yes.. that's why I'm attempting to resize the fs.
By the way, if I hadn't done that, it would say "same size" on
attempted resize - I tried it earlier.
6888
days inactive
6890
days old
20 comments
7 participants
participants (7)
-
David Hagood -
Ignacio Vazquez-Abrams -
Ivan Gyurdiev -
Jef Spaleta -
Jesse Keating -
Justin Conover -
Peter Jones