* We hit ext3_warning (inode->i_sb, "ext3_block_to_path", "block < 0");
@ 2006-05-03 12:54 Ingo Oeser
0 siblings, 0 replies; only message in thread
From: Ingo Oeser @ 2006-05-03 12:54 UTC (permalink / raw)
To: ext3-users; +Cc: sct, akpm, adilger, linux-kernel
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-05-03 12:55 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-03 12:54 We hit ext3_warning (inode->i_sb, "ext3_block_to_path", "block < 0"); Ingo Oeser
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox