Skip to main content

Filesystem resize issue (ext4)

Error

[root@dvgllpsmsapp12 apps]# resize2fs /dev/mapper/ORAAPPVG-LV_APPS
resize2fs 1.39 (29-May-2006)
Filesystem at /dev/mapper/ORAAPPVG-LV_APPS is mounted on /apps; on-line resizing required
Performing an on-line resize of /dev/mapper/ORAAPPVG-LV_APPS to 275251200 (4k) blocks.
resize2fs: Inappropriate ioctl for device While trying to add group #4400

Resolution

[root@dvgllpsmsapp14 ~]# lvresize -L+500g /dev/mapper/ORAAPPVG-LV_APPS
  Extending logical volume LV_APPS to 1000.00 GB
  Logical volume LV_APPS successfully resized
[root@dvgllpsmsapp14 ~]#  yum -y install e4fsprogs
Loaded plugins: downloadonly, product-id, rhnplugin, security, subscription-
              : manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
This system is receiving updates from RHN Classic or RHN Satellite.
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package e4fsprogs.x86_64 0:1.41.12-4.el5_10 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package      Arch      Version               Repository                   Size
================================================================================
Installing:
 e4fsprogs    x86_64    1.41.12-4.el5_10      sms-rhel-x86_64-server-5    1.1 M

Transaction Summary
================================================================================
Install       1 Package(s)
Upgrade       0 Package(s)

Total download size: 1.1 M
Downloading Packages:
e4fsprogs-1.41.12-4.el5_10.x86_64.rpm                    | 1.1 MB     00:00     
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing     : e4fsprogs                                                1/1 

Installed:
  e4fsprogs.x86_64 0:1.41.12-4.el5_10                                           

Complete!
[root@dvgllpsmsapp14 ~]# resize4fs /dev/mapper/ORAAPPVG-LV_APPS 
resize4fs 1.41.12 (17-May-2010)
Filesystem at /dev/mapper/ORAAPPVG-LV_APPS is mounted on /apps; on-line resizing required
old desc_blocks = 32, new_desc_blocks = 63
Performing an on-line resize of /dev/mapper/ORAAPPVG-LV_APPS to 262144000 (4k) blocks.
The filesystem on /dev/mapper/ORAAPPVG-LV_APPS is now 262144000 blocks long.

[root@dvgllpsmsapp14 ~]# df -h /apps
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/ORAAPPVG-LV_APPS
                      985G   63G  872G   7% /apps

Comments

Post a Comment

Popular posts from this blog

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...
2 comments
Read more

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.
Post a Comment
Read more

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more