Re: ext2fs_test_block_bitmap (): Unknown code ext2 47 #0, etc.

[Ivan Shmakov <ivan@gray.siamics.net>]

>>>>> Ted Ts'o <tytso@mit.edu> writes:
>>>>> On Thu, Aug 18, 2011 at 11:27:30PM +0700, Ivan Shmakov wrote:

[…]

 >> However, I'm getting the following message on stderr upon a call
 >> (only the first one?) to ext2fs_test_block_bitmap ():

 >> --cut--
 >> Unknown code ext2 47 #0 for block bitmap for /dev/stdin
 >> --cut--

 > You're not getting a human-readable error message because you need to
 > add the following at the beginning of your program:

 > add_error_table(&et_ext2_error_table);

	Thanks for the suggestion!

[…]

 > The 47th error message in the ext2 error table, which would have been
 > printed if you had called add_error_table(), is:

 > Illegal block number passed to ext2fs_test_block_bitmap

 > This means you've passed in a block number which is out-of-range for
 > the block bitmap.

	Do I understand it correctly that the block #0 isn't covered by
	any bitmap?  (I guess it's reserved for bootloaders, etc.)

 >> Also, do I understand it correctly that I need to call
 >> ext2fs_read_block_bitmap () before accessing the block_map member of
 >> the ext2_filsys structure?

 > Yes, or if you are going to need to read in both the block and inode
 > bitmaps, you can use ext2fs_read_bitmaps(), which will be more
 > optimal for reading in the block bitmaps.

	ACK.  Thanks.

-- 
FSF associate member #7257	Coming soon: Software Freedom Day
http://mail.sf-day.org/lists/listinfo/ planning-ru (ru), sfd-discuss (en)

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html