This is happening on several box's now, i386/64 selinux off/on, doesn't seem to matter.
"ext2online: ext2_ioctl: No space left on device" With 60+GB left, another box has 11GB and another has 80+GB.
$ df -h /home Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol02 42G 35G 5.0G 88% /home
# vgdisplay --- Volume group --- VG Name VolGroup00 System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 20 VG Access read/write VG Status resizable MAX LV 0 Cur LV 8 Open LV 8 Max PV 0 Cur PV 1 Act PV 1 VG Size 148.91 GB PE Size 32.00 MB Total PE 4765 Alloc PE / Size 2716 / 84.88 GB Free PE / Size 2049 / 64.03 GB VG UUID FIl4bH-o9Zi-0zfE-m3by-ieZ2-RaJJ-IVVss0
# lvextend -L+10G /dev/VolGroup00/LogVol02 Extending logical volume LogVol02 to 60.00 GB Logical volume LogVol02 successfully resized
# ext2online -d /dev/VolGroup00/LogVol02 ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b ext2_open ext2_bcache_init ext2_determine_itoffset setting itoffset to +1027 ext2_get_reserved Found 1021 blocks in s_reserved_gdt_blocks
343 old groups, 3 blocks 480 new groups, 4 blocks checking for group block 32772 in Bond checking for group block 98308 in Bond checking for group block 163844 in Bond checking for group block 229380 in Bond checking for group block 294916 in Bond checking for group block 819204 in Bond checking for group block 884740 in Bond checking for group block 1605636 in Bond checking for group block 2654212 in Bond checking for group block 4096004 in Bond checking for group block 7962628 in Bond ext2_ioctl: EXTEND group to 11239424 blocks
using itoffset of 1027 new block bitmap is at 0xab8401 new inode bitmap is at 0xab8402 new inode table is at 0xab8403-0xab8802 new group has 30717 free blocks new group has 32768 free inodes (1024 blocks) ext2_ioctl: ADD group 343 ext2online: ext2_ioctl: No space left on device
ext2online: unable to resize /dev/mapper/VolGroup00-LogVol02
<SNIP>
# ext2online -d /dev/VolGroup00/LogVol02 ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b ext2_open ext2_bcache_init ext2_determine_itoffset setting itoffset to +1027 ext2_get_reserved Found 1021 blocks in s_reserved_gdt_blocks
343 old groups, 3 blocks 480 new groups, 4 blocks checking for group block 32772 in Bond checking for group block 98308 in Bond checking for group block 163844 in Bond checking for group block 229380 in Bond checking for group block 294916 in Bond checking for group block 819204 in Bond checking for group block 884740 in Bond checking for group block 1605636 in Bond checking for group block 2654212 in Bond checking for group block 4096004 in Bond checking for group block 7962628 in Bond ext2_ioctl: EXTEND group to 11239424 blocks
using itoffset of 1027 new block bitmap is at 0xab8401 new inode bitmap is at 0xab8402 new inode table is at 0xab8403-0xab8802 new group has 30717 free blocks new group has 32768 free inodes (1024 blocks) ext2_ioctl: ADD group 343 ext2online: ext2_ioctl: No space left on device
ext2online: unable to resize /dev/mapper/VolGroup00-LogVol02
# tail /var/log/messages <SNIP> May 30 11:20:51 morpheus kernel: JBD: ext2online wants too many credits (2050 > 2048)
On 5/30/05, Justin Conover justin.conover@gmail.com wrote:
<SNIP> > # ext2online -d /dev/VolGroup00/LogVol02 > ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b > ext2_open > ext2_bcache_init > ext2_determine_itoffset > setting itoffset to +1027 > ext2_get_reserved > Found 1021 blocks in s_reserved_gdt_blocks > > 343 old groups, 3 blocks > 480 new groups, 4 blocks > checking for group block 32772 in Bond > checking for group block 98308 in Bond > checking for group block 163844 in Bond > checking for group block 229380 in Bond > checking for group block 294916 in Bond > checking for group block 819204 in Bond > checking for group block 884740 in Bond > checking for group block 1605636 in Bond > checking for group block 2654212 in Bond > checking for group block 4096004 in Bond > checking for group block 7962628 in Bond > ext2_ioctl: EXTEND group to 11239424 blocks > > using itoffset of 1027 > new block bitmap is at 0xab8401 > new inode bitmap is at 0xab8402 > new inode table is at 0xab8403-0xab8802 > new group has 30717 free blocks > new group has 32768 free inodes (1024 blocks) > ext2_ioctl: ADD group 343 > ext2online: ext2_ioctl: No space left on device > > ext2online: unable to resize /dev/mapper/VolGroup00-LogVol02 > # tail /var/log/messages <SNIP> May 30 11:20:51 morpheus kernel: JBD: ext2online wants too many credits (2050 > 2048)
Anyone have a problem extending partions, (3 box's = no go)?
Can I go to the bank and buy more credits.........
Hi,
On Mon, 2005-05-30 at 17:26, Justin Conover wrote:
This is happening on several box's now, i386/64 selinux off/on, doesn't seem to matter.
"ext2online: ext2_ioctl: No space left on device" With 60+GB left, another box has 11GB and another has 80+GB.
Works for me; do you have a bugzilla open for this? Please open one if not.
May 30 11:20:51 morpheus kernel: JBD: ext2online wants too many credits (2050 > 2048)
I've never seen this before; I'm wondering if there's something odd about how the fs was created. Did you initialise it with an unusually large number of inodes, for example?
--Stephen
On 6/7/05, Stephen C. Tweedie sct@redhat.com wrote:
Hi,
On Mon, 2005-05-30 at 17:26, Justin Conover wrote:
This is happening on several box's now, i386/64 selinux off/on, doesn't seem to matter.
"ext2online: ext2_ioctl: No space left on device" With 60+GB left, another box has 11GB and another has 80+GB.
Works for me; do you have a bugzilla open for this? Please open one if not.
May 30 11:20:51 morpheus kernel: JBD: ext2online wants too many credits (2050 > 2048)
I've never seen this before; I'm wondering if there's something odd about how the fs was created. Did you initialise it with an unusually large number of inodes, for example?
--Stephen
Nope, this was normal install and I've had it happen on another box too. When I get home, I'll recreate it and file a bug.
On 6/7/05, Stephen C. Tweedie sct@redhat.com wrote:
Hi,
On Mon, 2005-05-30 at 17:26, Justin Conover wrote:
This is happening on several box's now, i386/64 selinux off/on, doesn't seem to matter.
"ext2online: ext2_ioctl: No space left on device" With 60+GB left, another box has 11GB and another has 80+GB.
Works for me; do you have a bugzilla open for this? Please open one if not.
May 30 11:20:51 morpheus kernel: JBD: ext2online wants too many credits (2050 > 2048)
I've never seen this before; I'm wondering if there's something odd about how the fs was created. Did you initialise it with an unusually large number of inodes, for example?
--Stephen
Sorry, works has been kicking my buttttt!
Happened again, I'll fill a bug.
vgdisplay Free PE / Size 2765 / 86.41 GB
# lvextend -L+5G /dev/VolGroup00/LogVol02 Extending logical volume LogVol02 to 47.00 GB Logical volume LogVol02 successfully resized
# ext2online -d /dev/VolGroup00/LogVol02 ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b ext2_open ext2_bcache_init ext2_determine_itoffset setting itoffset to +1027 ext2_get_reserved <BLAH BLAH BLAH> using itoffset of 1027 new block bitmap is at 0xab8401 new inode bitmap is at 0xab8402 new inode table is at 0xab8403-0xab8802 new group has 30717 free blocks new group has 32768 free inodes (1024 blocks) ext2_ioctl: ADD group 343 ext2online: ext2_ioctl: No space left on device
ext2online: unable to resize /dev/mapper/VolGroup00-LogVol02
#dmesg <blah> JBD: ext2online wants too many credits (2050 > 2048)
On 6/7/05, Stephen C. Tweedie sct@redhat.com wrote:
Hi,
On Mon, 2005-05-30 at 17:26, Justin Conover wrote:
This is happening on several box's now, i386/64 selinux off/on, doesn't seem to matter.
"ext2online: ext2_ioctl: No space left on device" With 60+GB left, another box has 11GB and another has 80+GB.
Works for me; do you have a bugzilla open for this? Please open one if not.
May 30 11:20:51 morpheus kernel: JBD: ext2online wants too many credits (2050 > 2048)
I've never seen this before; I'm wondering if there's something odd about how the fs was created. Did you initialise it with an unusually large number of inodes, for example?
--Stephen
[Bug 160612] ext2online wants to many credits, can't resize logical volume
The other day I decided to mv my laptop (work) to fc4 instead of running rawhide all the time an it did the samething too. So I blew it out again and just left lvm off of it and just used standard file systems. I still have 2 box's i386/amd64 that run rawhide.
On 6/15/05, Justin Conover justin.conover@gmail.com wrote:
On 6/7/05, Stephen C. Tweedie sct@redhat.com wrote:
Hi,
On Mon, 2005-05-30 at 17:26, Justin Conover wrote:
This is happening on several box's now, i386/64 selinux off/on, doesn't seem to matter.
"ext2online: ext2_ioctl: No space left on device" With 60+GB left, another box has 11GB and another has 80+GB.
Works for me; do you have a bugzilla open for this? Please open one if not.
May 30 11:20:51 morpheus kernel: JBD: ext2online wants too many credits (2050 > 2048)
I've never seen this before; I'm wondering if there's something odd about how the fs was created. Did you initialise it with an unusually large number of inodes, for example?
--Stephen
[Bug 160612] ext2online wants to many credits, can't resize logical volume
The other day I decided to mv my laptop (work) to fc4 instead of running rawhide all the time an it did the samething too. So I blew it out again and just left lvm off of it and just used standard file systems. I still have 2 box's i386/amd64 that run rawhide.
Another test, I decided to scrap my rawhide 64 box and install fc4........ same problem ;(
ext2online: unable to resize /dev/mapper/VolGroup00-LogVol01
dmesg output's the same thing JBD: ext2online wants too many credits (2050 > 2048)
On 6/16/05, Justin Conover justin.conover@gmail.com wrote:
On 6/15/05, Justin Conover justin.conover@gmail.com wrote:
On 6/7/05, Stephen C. Tweedie sct@redhat.com wrote:
Hi,
On Mon, 2005-05-30 at 17:26, Justin Conover wrote:
This is happening on several box's now, i386/64 selinux off/on, doesn't seem to matter.
"ext2online: ext2_ioctl: No space left on device" With 60+GB left, another box has 11GB and another has 80+GB.
Works for me; do you have a bugzilla open for this? Please open one if not.
May 30 11:20:51 morpheus kernel: JBD: ext2online wants too many credits (2050 > 2048)
I've never seen this before; I'm wondering if there's something odd about how the fs was created. Did you initialise it with an unusually large number of inodes, for example?
--Stephen
[Bug 160612] ext2online wants to many credits, can't resize logical volume
The other day I decided to mv my laptop (work) to fc4 instead of running rawhide all the time an it did the samething too. So I blew it out again and just left lvm off of it and just used standard file systems. I still have 2 box's i386/amd64 that run rawhide.
Another test, I decided to scrap my rawhide 64 box and install fc4........ same problem ;(
ext2online: unable to resize /dev/mapper/VolGroup00-LogVol01
dmesg output's the same thing JBD: ext2online wants too many credits (2050 > 2048)
ODD, I just extended /usr another 2 GB!
Could there be a size limit problem happeneing? I know before that I was doing this on /home and it was pretty large, 40-80GB and now my home on this install today strated at 40GB and I tried to increase it another 5GB.
/usr was 8GB and I just extended it to 10GB
ODD, I just extended /usr another 2 GB!
Could there be a size limit problem happeneing? I know before that I was doing this on /home and it was pretty large, 40-80GB and now my home on this install today strated at 40GB and I tried to increase it another 5GB.
/usr was 8GB and I just extended it to 10GB
Just some more notes, /usr/local was 4GB and is now 10GB no problem.
# vgdisplay | grep Free I Free PE / Size 2349 / 73.41 GB
Tried to create a 40GB with ext3 /TESTLVM slice # system-config-lvm Incorrect metadata area header checksum Incorrect metadata area header checksum Incorrect metadata area header checksum Incorrect metadata area header checksum Incorrect metadata area header checksum Incorrect metadata area header checksum << Another 80+lines >>>> Disk /dev/md0 doesn't contain a valid partition table <<< same stuff >>>>>> Incorrect metadata area header checksum Incorrect metadata area header checksum Incorrect metadata area header checksum Disk /dev/md0 doesn't contain a valid partition table Incorrect metadata area header checksum Incorrect metadata area header checksum Incorrect metadata area header checksum Incorrect metadata area header checksum
ERROR displayed on screen: =
mkfs command failed. Command attempted: "/sbin/mkfs -t ext3 /dev/VolGroup00/LogVol07" - System Error Message: mke2fs 1.37 (21-Mar-2005) Could not stat /dev/VolGroup00/LogVol07 --- Permission denied
# /sbin/mke2fs -j /dev/VolGroup00/LogVol07 mke2fs 1.37 (21-Mar-2005) Could not stat /dev/VolGroup00/LogVol07 --- Permission denied
# /sbin/mke2fs /dev/mapper/VolGroup00-LogVol07 mke2fs 1.37 (21-Mar-2005) Could not stat /dev/mapper/VolGroup00-LogVol07 --- Permission denied
# id -Z root:system_r:unconfined_t
]# id uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel) context=root:system_r:unconfined_t
Well, i'm going to relabel and see if that does anything.
Hi,
On Fri, 2005-06-17 at 04:55, Justin Conover wrote:
ODD, I just extended /usr another 2 GB!
Could there be a size limit problem happeneing? I know before that I was doing this on /home and it was pretty large, 40-80GB and now my home on this install today strated at 40GB and I tried to increase it another 5GB.
Not sure. Have you filed a bug yet? If so, please attach "tune2fs -l" information for one of the filesystems in question.
Thanks, Stephen
On 6/17/05, Stephen C. Tweedie sct@redhat.com wrote:
Hi,
On Fri, 2005-06-17 at 04:55, Justin Conover wrote:
ODD, I just extended /usr another 2 GB!
Could there be a size limit problem happeneing? I know before that I was doing this on /home and it was pretty large, 40-80GB and now my home on this install today strated at 40GB and I tried to increase it another 5GB.
Not sure. Have you filed a bug yet? If so, please attach "tune2fs -l" information for one of the filesystems in question.
Thanks, Stephen
On 6/17/05, Justin Conover justin.conover@gmail.com wrote:
On 6/17/05, Stephen C. Tweedie sct@redhat.com wrote:
Hi,
On Fri, 2005-06-17 at 04:55, Justin Conover wrote:
ODD, I just extended /usr another 2 GB!
Could there be a size limit problem happeneing? I know before that I was doing this on /home and it was pretty large, 40-80GB and now my home on this install today strated at 40GB and I tried to increase it another 5GB.
Not sure. Have you filed a bug yet? If so, please attach "tune2fs -l" information for one of the filesystems in question.
Thanks, Stephen
Oddness strikes again, I'm trying to extend home again to see what it does and when I type in :
lvextend -L+2G /d<hit tab> I get this
# lvextend -L+2G /dawk: {if ($2 ~ /^/d/) print $2} awk: ^ syntax error
Another note, I re-install on my other test box, this time creating /home on LogVol07 and makeing it 80GB. Updated to rawhide and now it extends just fine.
On 6/22/05, Justin Conover justin.conover@gmail.com wrote:
On 6/17/05, Justin Conover justin.conover@gmail.com wrote:
On 6/17/05, Stephen C. Tweedie sct@redhat.com wrote:
Hi,
On Fri, 2005-06-17 at 04:55, Justin Conover wrote:
ODD, I just extended /usr another 2 GB!
Could there be a size limit problem happeneing? I know before that I was doing this on /home and it was pretty large, 40-80GB and now my home on this install today strated at 40GB and I tried to increase it another 5GB.
Not sure. Have you filed a bug yet? If so, please attach "tune2fs -l" information for one of the filesystems in question.
Thanks, Stephen
Oddness strikes again, I'm trying to extend home again to see what it does and when I type in :
lvextend -L+2G /d<hit tab> I get this
# lvextend -L+2G /dawk: {if ($2 ~ /^/d/) print $2} awk: ^ syntax error
Another note, I re-install on my other test box, this time creating /home on LogVol07 and makeing it 80GB. Updated to rawhide and now it extends just fine.
This is the broken fc4 x86_64 box (forgot to include it)
lvextend -L+2G /dev/VolGroup00/LogVol01 /dev/cdrom: open failed: Read-only file system Incorrect metadata area header checksum Extending logical volume LogVol01 to 57.00 GB Logical volume LogVol01 successfully resized [root@morpheus ~]# ext2online -d /dev/VolGroup00/LogVol01 ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b ext2_open ext2_bcache_init ext2_determine_itoffset setting itoffset to +1027 ext2_get_reserved Found 1021 blocks in s_reserved_gdt_blocks <cut> using itoffset of 1027 new block bitmap is at 0xab8401 new inode bitmap is at 0xab8402 new inode table is at 0xab8403-0xab8802 new group has 30717 free blocks new group has 32768 free inodes (1024 blocks) ext2_ioctl: ADD group 343 ext2online: ext2_ioctl: No space left on device
ext2online: unable to resize /dev/mapper/VolGroup00-LogVol01
JBD: ext2online wants too many credits (2050 > 2048)
# df -h /home Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol01 42G 27G 14G 67% /home
Hi,
On Thu, 2005-06-23 at 04:35, Justin Conover wrote:
Oddness strikes again, I'm trying to extend home again to see what it does and when I type in :
lvextend -L+2G /d<hit tab> I get this
# lvextend -L+2G /dawk: {if ($2 ~ /^/d/) print $2} awk: ^ syntax error
Shell completion is *definitely* not ext3's problem. :-)
Cheers, Stephen
-
Justin Conover -
Stephen C. Tweedie