[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Second Block on Partition overwritten with 0xFF
- From: "Tomas Pospisek ML" <tpo2 sourcepole ch>
- To: ext3-users redhat com
- To: "ext3-users redhat com" <ext3-users redhat com>
- Subject: Re: Second Block on Partition overwritten with 0xFF
- Date: Thu, 06 Sep 2007 10:09:12 +0000
On 9/6/2007, "Theodore Tso" <tytso mit edu> wrote:
>On Wed, Sep 05, 2007 at 08:58:15AM +0000, Tomas Pospisek ML wrote:
>>
>> Can anybody here give me a hint about the problem? Particulary:
>>
>> > My question is: does the ext3 driver _ever_ write outside of its own
>> > space on disk - i.e into 0x000-0x400? That is can we exclude with
>> > certainity that it's _not_ the ext3 driver causing the problem?
>
>The ext3 driver physically can not write outside of its space on disk,
>since it accesses it via some device whose boundaries are defined by
>the partition table, for example, /dev/hda2.
Yes, however, as I read in [1] *each* partition with an ext2/3 FS on it
starts with a boot sector, and the first block group starts (per
default) at 0x400. Thus as I understand it, it *would* be possible for
the ext3 driver to pysically write to those first sectors inside its
partition.
Does the ext2/3 driver *ever* touch anything before the first block group?
>>From what you describe, I would certainly be suspicious of the CF
>hardware.
Well I certainly am, however I am not able to find any way forward to be
able to point my finger on it.
*t
[1] http://web.mit.edu/tytso/www/linux/ext2intro.html (chapter "Physical
Structure")
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]