[Bug 216141] New: xfs corrupted directly after sized mkfs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=216141

            Bug ID: 216141
           Summary: xfs corrupted directly after sized mkfs
           Product: File System
           Version: 2.5
    Kernel Version: v5.19-rc2
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: XFS
          Assignee: filesystem_xfs@xxxxxxxxxxxxxxxxxxxxxx
          Reporter: zlang@xxxxxxxxxx
        Regression: No

I suddently hit xfstests generic/096 fails on a striped XFS. It's easy to
reproduce on my system manually by below steps:

# git lo | head -1
8c642e6f xfsprogs: Release v5.18.0
# ./mkfs/mkfs.xfs -f -d size=$((512*1024*1024)) /dev/sda5
meta-data=/dev/sda5              isize=512    agcount=8, agsize=16384 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=1    bigtime=1 inobtcount=1
data     =                       bsize=4096   blocks=131072, imaxpct=25
         =                       sunit=64     swidth=64 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=16320, version=2
         =                       sectsz=512   sunit=64 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
# echo $?
0
# ./repair/xfs_repair -n /dev/sda5
Phase 1 - find and verify superblock...
        - reporting progress in intervals of 15 minutes
Phase 2 - using internal log
        - zero log...
        - 21:35:03: zeroing log - 16320 of 16320 blocks done
        - scan filesystem freespace and inode maps...
agf_freeblks 58, counted 0 in ag 4
sb_fdblocks 114696, counted 114638
        - 21:35:03: scanning filesystem freespace - 8 of 8 allocation groups
done
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - 21:35:03: scanning agi unlinked lists - 8 of 8 allocation groups done
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 7
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - 21:35:03: process known inodes and inode discovery - 64 of 64 inodes
done
        - process newly discovered inodes...
        - 21:35:03: process newly discovered inodes - 8 of 8 allocation groups
done
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - 21:35:03: setting up duplicate extent list - 8 of 8 allocation groups
done
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 4
        - agno = 2
        - agno = 3
        - agno = 5
        - agno = 7
        - agno = 6
        - agno = 1
        - 21:35:03: check for inodes claiming duplicate blocks - 64 of 64
inodes done
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...
        - 21:35:04: verify and correct link counts - 8 of 8 allocation groups
done
No modify flag set, skipping filesystem flush and exiting.
# echo $?
1

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.



[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux