I have just tried this patch (to resize2fs.c. There is another patch for resize.c, but I dont have a resize.c in the 1.42.11 src tree), but it didn't work out the way I'd like.
It seems to went all okay: /dev/sdb 29T 26T 2.1T 93% /backups root@dione:/usr/local/e2fsprogs/sbin# umount /backups/ root@dione:/usr/local/e2fsprogs/sbin# ./resize2fs -fp /dev/sdb resize2fs 1.42.11 (09-Jul-2014) Resizing the filesystem on /dev/sdb to 8775931648 (4k) blocks. Begin pass 2 (max = 11703) Relocating blocks XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Begin pass 3 (max = 238018) Scanning inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Begin pass 5 (max = 1) Moving inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX The filesystem on /dev/sdb is now 8775931648 blocks long. root@dione:/# mount -a root@dione:/# df -h /dev/sdb 33T 26T 5.5T 83% /backups However: root@dione:/backups# ls -la total 0 As shown, this disk contains 26 terabytes of data, but according to 'ls' the disk is empty. I am trying to see if this can be fixed with e2fsck.. But this is scary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321958 Title: resize2fs does not start to actually grow an ext4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321958/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
