Re: A tool for remapping bad sectors in CURRENT?

From: Miroslav Lachman <000.fbsd_at_quip.cz>
Date: Sun, 14 Mar 2010 17:18:45 +0100
Gary Jennejohn wrote:
> On Sun, 14 Mar 2010 10:55:19 +0100
> Miroslav Lachman<000.fbsd_at_quip.cz>  wrote:
>
> [big snip]
>> fsdb (inum: 3)>  blocks
>> Blocks for inode 3:
>> Direct blocks:
>> 3001 (1 frag)
>>
>> fsdb (inum: 3)>  findblk 3001
>> fsdb (inum: 3)>
>>
>>                  ^^^^^^^^ findblk did not returned inode 3!
>>
>
> This is almost guaranteed to be a file system block and not
> a disk block.

Do you mean the number 3001?
I am sorry for my ignorance, but it is not clear to me from fsdb manpage 
what "blocks" means FS block and what disk block.

And how can I use (calculate with) this numbers?

How can I get the right number to pass to findlbk command (in the 
example above) to give me back the inode 3?

If FS block is 16384 bytes, then it means 16384/512 = 32 disk blocks per 
FS block.

If 3001 is FS block, then it means 3001*32 = 96032 disk block number. Am 
I right?

fsdb (inum: 3)> findblk 96032
fsdb (inum: 3)>

Again - findblk did not returned inode 3.

So what is the exact formula to get the right findblk number and then 
right inode number as result of findblk command?

I am still lost in terms (words) and numbers :(

Miroslav Lachman
Received on Sun Mar 14 2010 - 15:18:49 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:01 UTC