| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | blktrace and xfs_db block offset mismatch |
| From: | Sushma R <gsushma@xxxxxxxxx> |
| Date: | Sat, 27 Sep 2014 00:32:21 -0700 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Xxb0OtVQCfiNhArb/N5ZlDEq4duLF487+crdOIP9s5M=; b=MvwcCnwqa8ylrCY/GzP70rwrhQrxDWOtq7oueWSi3wmYX4KekLM0QZgfCRZfWXjuus X3By2LK8IoCi9xBgsFmI6C7rkKoco1od1z7vHOe6K+cygjZ5ejSo+mvkYuq0D1htukZi 7ohkveDF2KZQ9uLmKGf4GLKxhcXMqtUTMynPnGY2ONLkJekcyz4gTdkUs96ZEBnrcNM1 QRDRA0pI04Mcj5BAjYM8e0e3t2zRQ8dVelfg62i01vtlHJtYa/0cCCLetM4j5wfrEcRk Hw6QxGF/wfcnLpwk8uzpuFu3NbBNQLJvT+fDfKLZ3UWFzbjvvSsmgm5f3aZ5WjypXtbb YI+A== |
|
Hi,
I ran blktrace while reading a file on XFS partition and here's it's output. 8,17 Â 3 Â Â Â Â1 Â Â22.065944956 Â5489 ÂD Â R 20973896 + 8 [cat] Using xfs_db, I dumped the inode for the same file and it shows the following as its data extents. u.bmx[0] = [startoff,startblock,blockcount,extentflag] 0:[0,2621481,1,0] I understand that blktrace reports in 512-byte sectors while xfs_db in filesystem block size (which is the default 4KB on my setup). Converting blktrace offset to fs block =Â2621737 which is close to the data extent startblock (2621481), but still off by 256 fs blocks. Could someone please help understand the reason for this mismatch? Thanks, Sushma |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 2/5] xfs: recovery of XLOG_UNMOUNT_TRANS leaks memory, Dave Chinner |
|---|---|
| Next by Date: | Re: blktrace and xfs_db block offset mismatch, Brian Foster |
| Previous by Thread: | [PATCH] xfs/053: test for stale data exposure via falloc/writeback interaction, Brian Foster |
| Next by Thread: | Re: blktrace and xfs_db block offset mismatch, Brian Foster |
| Indexes: | [Date] [Thread] [Top] [All Lists] |