xfs_check does not recognize fs truncation

xfs_check does not recognize fs truncation

[Jan Engelhardt]

Hi,


This I see on xfsprogs-2.10.1 with kernel 2.6.29.6:

# xfs_check /dev/loop0
# echo $?
0
# mount /dev/loop0 /mnt
Filesystem "loop0": Disabling barriers, trial barrier write failed
attempt to access beyond end of device
loop0: rw=0, want=3670016, limit=3649536
I/O error in filesystem ("loop0") meta-data dev loop0 block 0x37ffff
("xfs_read_buf") error 5 buf count 512
XFS: size check 2 failed

The fs is truncated (my fault/intention), but xfs_check returning 0 is 
unexpected.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfs_check does not recognize fs truncation

[Christoph Hellwig]

On Mon, Aug 24, 2009 at 12:12:59PM +0200, Jan Engelhardt wrote:
> Hi,
> 
> 
> This I see on xfsprogs-2.10.1 with kernel 2.6.29.6:

What does xfs_repair -n say?

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfs_check does not recognize fs truncation

[Jan Engelhardt]

On Monday 2009-08-24 16:47, Christoph Hellwig wrote:
>On Mon, Aug 24, 2009 at 12:12:59PM +0200, Jan Engelhardt wrote:
>> 
>> This I see on xfsprogs-2.10.1 with kernel 2.6.29.6:
>
>What does xfs_repair -n say?

Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 1
        - agno = 0
        - agno = 2
        - agno = 3
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.


You can get the image at
http://dev.medozas.de/files/linux-hist.img.lzma [179MB->1782MB]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfs_check does not recognize fs truncation

[Jan Engelhardt]

On Monday 2009-08-24 18:04, Jan Engelhardt wrote:
>On Monday 2009-08-24 16:47, Christoph Hellwig wrote:
>>On Mon, Aug 24, 2009 at 12:12:59PM +0200, Jan Engelhardt wrote:
>>> 
>>> This I see on xfsprogs-2.10.1 with kernel 2.6.29.6:
>>
>>What does xfs_repair -n say?
>
>[success]
>
>You can get the image at
>http://dev.medozas.de/files/linux-hist.img.lzma [179MB->1782MB]
>

If I pad the image with at least 20480*512 NUL bytes to a total of
1879048192 bytes, xfs (kernel side) starts to accept the image and
will mount it.

The steps to return to the previous problematic size is as follows:
# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/loop0             1824768   1274824    549944  70% /mnt/linux-hist
# truncate --size=$((1824768*1024)) linux-hist.img

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs