| To: | Eric Sandeen <sandeen@xxxxxxx> |
|---|---|
| Subject: | Re: bad block number and bad nblocks after simple file operations. |
| From: | Pavel Kiryukhin <savl@xxxxxxxxxxxxx> |
| Date: | Fri, 17 Sep 2004 16:46:47 +0400 |
| Cc: | linux-xfs@xxxxxxxxxxx, Pavel Kiryukhin <savl@xxxxxxxxxxxxx> |
| In-reply-to: | <4149C14B.9070907@sgi.com> |
| References: | <41487343.5010009@dev.rtsoft.ru> <4149C14B.9070907@sgi.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 |
Looks like maybe some platform/endian issues. Yes! It looks like that: platform: - there is no problem with ARM LE and the same kernel + XFS version (1.3) endian: more complicated. for both BE and LE tests like bonnie++ are passed. Bad things happens in case of, say, system crash. For MIPS LE fs can not recovered. This was tested on two different mips LE boards. Currently I found that bmx field of inode get corrupted (all tests for mips le): xfs_db> blockget -n inode 132 bad block number -1 [0,-1], offset 0 bad nblocks 1 for inode 132, counted 0 block 0/12 type unknown not expected xfs_db> ncheck 131 nullfile 132 testfile xfs_db> agf 0 xfs_db> inode 132 xfs_db> p core.size core.size = 120 xfs_db> p u.bmx u.bmx[0] = [startoff,startblock,blockcount,extentflag] 0:[0,0,0,0] ------- Here I don't understand how fs contines to operate (open and read) with this file? It looks like some cache issues: I create file with size 0. blockget -n does not complain. I write to this file 2 bytes, blockget -n does not complain. I leave xfs_db, issue sync twice - have xfs_db> blockget -n inode 131 bad block number -1 [0,-1], offset 0 bad nblocks 1 for inode 131, counted 0 block 0/12 type unknown not expected xfs_db> q root@xxxxxxxxxxxxx:/mnt# cat /mnt/xfs/testfile t root@xxxxxxxxxxxxx:/mnt# umount /mnt/xfs/ root@xxxxxxxxxxxxx:/mnt# mount /dev/ide/host0/bus0/target0/lun0/part1 /mnt/xfs/ XFS mounting filesystem ide0(3,1) root@xxxxxxxxxxxxx:/mnt# cat ./xfs/testfile root@xxxxxxxxxxxxx:/mnt# root@xxxxxxxxxxxxx:/mnt# ls -l ./xfs/ total 4 -rw-r--r-- 1 root root 2 Jan 1 00:39 testfile ---------- Actually I get my 2 bytes corrupted.
Well, I'm using 1.3.1 version now. The same problem can be reproduced for 1.3. --- As I am totally new to xfs could you please recommend the place to start looking at. Even general hints like "buffer cache" will be highly appreciated! ------- Thank you, Pavel Kiryukhin
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] Re: Major XFS problems..., Jakob Oestergaard |
|---|---|
| Next by Date: | Re: bad block number and bad nblocks after simple file operations., Christoph Hellwig |
| Previous by Thread: | Re: bad block number and bad nblocks after simple file operations., Eric Sandeen |
| Next by Thread: | Re: bad block number and bad nblocks after simple file operations., Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |