Looks like maybe some platform/endian issues.
How big is your filesystem? (xfs_info /mount/point)
Below, those block numbers look very big, as do the AG numbers
Can you try more recent XFS code? Where'd the XFS code come from? I'd
suggest getting XFS from CVS if you can, just to make sure we're not
chasing old bugs.
Pavel Kiryukhin wrote:
can anybody help me and answer: is it normal XFS behavior or something
is terribly wrong?
1) I have created and mounted xfs using loop device and NFS (with IDE
disk results are generally the same),
2) created file "testfile", directoty "tesdir" and file "testfile"1 in it.
3) unmounted xfs and started xfs_db
xfs_db> blockget -n
inode 132 bad block number 3870332469381120 [6291456,2048], offset 4238657
bad nblocks 1 for inode 132, counted 0
inode 134 bad block number 1759274439018496 [6815744,2048], offset 4238659
bad nblocks 1 for inode 134, counted 0
block 0/12 type unknown not expected
block 0/13 type unknown not expected
xfs_db> log stop
After that I can mount again and work with XFS, read/write/create files
My platform is MIPS (LE and BE), 2.4.20 kernel