Hi again all, I apologize for not asking this in my first message; I just remembered the question after sending. On Sun, Jun 01, 2014 at 07:43:12PM -0700, Keith Keller wrote: > > On Sun, Jun 01, 2014 at 09:05:09PM -0400, Theodore Ts'o wrote: > > Unfortunately, there has been a huge number of bug fixes for ext4's > > online resize since 2.6.32 and 1.42.11. It's quite possible that you > > hit one of them. > > Would this scenario be explained by these bugs? I'd expect that if a > resize2fs failed, it would report a problem pretty quickly. (But > perhaps that's the nature of some of these bugs.) I have a very similar second server which has undergone a similar chain of events, an initial ~2.5tb fs followed by a resize later. I believe that it has been fsck'd since the resize (but don't quote me on that). Am I likely to run into this issue with this fs? And if I do, what steps should I do differently (e.g., use the latest e2fsck right away; don't e2fsck, get files off quickly, and mke2fs; something else)? --keith -- kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ Ext3-users mailing list Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
