We hit ext3_warning (inode->i_sb, "ext3_block_to_path", "block < 0");

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:[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Prev by Date: Re: [PATCH] s390: Hypervisor File System
• Next by Date: Re: beta of pfmon-3.2 available
• Previous by thread: Re: [PATCH] 2.6.xx: sata_mv: another critical fix
• Next by thread: High baud rates support for Quatech DSP-100.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]