lkml.org 
[lkml]   [2006]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectWe hit ext3_warning (inode->i_sb, "ext3_block_to_path", "block < 0");
Date
Dear ext3-users,

we hit this condition in fs/ext3/inode.c:ext3_block_to_path()

if (i_block < 0) {
ext3_warning (inode->i_sb, "ext3_block_to_path", "block < 0");

occasionally on two identical PATA-IDE disks copied over per filesystem-rsync.


What is the impact of this condition?

- Kernel was 2.6.13.4, CONFIG_LBD is not set but CONFIG_HIGHMEM4G=y
(I can provide further details, if required)
- S.M.A.R.T meant everything is ok on both disks.
- Machine has been rebooted and fscked (180 days without reboot).
- Result of this fsck is not known.

The condition didn't happen after this anymore.


Regards

Ingo Oeser
--
Ingo Oeser
axxeo GmbH
Tiestestr. 16, 30171 Hannover
Tel. +49-511-4753706
Fax. +49-511-4753716

mailto:support@axxeo.de
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-05-03 14:57    [W:0.039 / U:0.360 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site