xfs
[Top] [All Lists]

bad block number and bad nblocks after simple file operations.

To: linux-xfs@xxxxxxxxxxx
Subject: bad block number and bad nblocks after simple file operations.
From: Pavel Kiryukhin <savl@xxxxxxxxxxxxx>
Date: Wed, 15 Sep 2004 20:52:19 +0400
Cc: Pavel Kiryukhin <savl@xxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
Hi,
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> ncheck
       131 testdir/.
       132 testfile
       134 testdir/testfile1
xfs_db> log stop

After that I can mount again and work with XFS, read/write/create files etc.
My platform is MIPS (LE and BE), 2.4.20 kernel
--
Thank you,
Pavel Kiryukhin


<Prev in Thread] Current Thread [Next in Thread>