ext4 resize/fsck

[Curtis Doty]

9:45pm Eric Sandeen said:

> Curtis Doty wrote:
>> 9:09pm Eric Sandeen said:
>>
>>> Curtis Doty wrote:
>>>> Horsing around with ext4 again...on F-10.
>>>>
>>>> This time a fsck was required after both an offline shrink and an online
>>>> grow. Why?
>>> Could you please try again with 1.41.4 from rawhide (or koji:
>>> http://kojipkgs.fedoraproject.org/packages/e2fsprogs/1.41.4/2.fc11/ -
>>> might need to rebuild if there are any library dependency problems) and
>>> see if this persists or is fixed?  Several resize fixes went into 1.41.4
>>> that should take care of this.
>>>
>>> I'll probably push 1.41.4 to f10 testing soon, if people are hitting
>>> these problems.
>>>
>>
>> Is this an improvement or luck? Fewer issues, but still a ghost dir.
>>
>> 19:30]stratus~# lvextend -L6G foo/bar
>>    Extending logical volume bar to 6.00 GB
>>    Logical volume bar successfully resized
>>
>> 19:31]stratus~# resize2fs -p /dev/foo/bar
>> resize2fs 1.41.4 (27-Jan-2009)
>> Filesystem at /dev/foo/bar is mounted on /home; on-line resizing required
>> old desc_blocks = 1, new_desc_blocks = 1
>> Performing an on-line resize of /dev/foo/bar to 1572864 (4k) blocks.
>> The filesystem on /dev/foo/bar is now 1572864 blocks long.
>>
>> 19:31]stratus~# umount /home
>> 19:32]stratus~# fsck.ext4 -C0 -f /dev/foo/bar
>> e2fsck 1.41.4 (27-Jan-2009)
>> Pass 1: Checking inodes, blocks, and sizes
>> Pass 2: Checking directory structure
>> Pass 3: Checking directory connectivity
>> Pass 4: Checking reference counts
>> Pass 5: Checking group summary information
>> Directories count wrong for group #37 (1, counted=0).
>> Fix<y>? yes
>>
>> bar: ***** FILE SYSTEM WAS MODIFIED *****
>> bar: 43188/153600 files (0.1% non-contiguous), 294524/1572864 blocks
>>
>> ../C
>>
>
> I hope it's an improvement ;)
>
> If you can reproduce it, you might capture an e2image of the fs prior to
> resize, and we could probably investigate the issue pretty easily...
>

Ak. Just re-shrunk offline and then re-grew online. With e2images in 
between each time. However, nothing was inconsistent these times!

Could it be that one ghost dir was indeed missed by 1.41.3 and 
caught/cleaned by 1.41.4? The symptom appears gone here now.

../C