Steve,
Anton and I have been going over this offline and it looks like he's
close to having it nailed on the W2K issues. There's some special bits
in the volume attribute field that have to be set correctly when going
back and forth between Nt$ and W2K. On the W2K partition issue, I think
Anton's close to having it figured out.
:-)
Jeff
Steve Dodd wrote:
>
> On Sun, Jul 09, 2000 at 06:08:03PM +0100, Anton Altaparmakov wrote:
> > At 16:24 09/07/2000, Steve Dodd wrote:
>
> > >I inferred from something Jeff said a while back that the volume management
> > >stuff was storing data in blocks that were marked free in the block bitmap.
> >
> > I don't think so. This would cause corruption by the WinNT4 driver as
> > well... (Unless there is a safe-guard in NT4 we are missing in linux.)
>
> I may have inferred wrongly ;-) I also thought you had to update the NTFS
> driver in WinNT4 to read (maybe certain sorts of) Win2K volumes?
>
> > > From what I know of the on-disk structures, there's 8 bytes of "magic"
> > > in the boot sector,
> >
> > That's news to me! - Which bytes (offsets?) are you referring to exactly?
>
> [rearranged a bit:]
> > Byte Ofs Length e.g. Meaning
> > (bytes) Value
> > 0x03 8 NTFS OEM Identifier
>
> Interestingly, the current Linux NTFS code only checks the first 4 bytes
> ("NTFS")..
>
> > My understainding of the boot sector is at the bottom of the email - it is
> > described in the MS WinNT4 ws resource kit book along with the partition
> > and mbr structures, I have integrated it into one structure for easier
> > reading. - It doesn't have any magic AFAICS.
>
> I meant "magic" in the sense of "unique type identifier"..
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jul 15 2000 - 21:00:15 EST