[comments in-line]

Quoting Rick Byers (30-Oct-01 21:24:25):

> I don't know what the difference is between ntfs4 and 5,

NTFS5 has 5 major improvements (journaling, encryption, ...). It's
used by Win2000. As soon as Win2000 "sees" an NTFS4 (WinNT) partition,
it converts it into a NTFS5 partition.

> but NetBSD
> doesn't appear to make a distinction.

It propably reads/writes NTFS5, but doesn't make use of the additional
NTFS5 features I mentionned above. This is the same what WinNT makes
with NTFS5. It is able to handle NTFS5 (in terms of reading and
writing), but doesn't use the additional functionalities of NTFS5.

> I can read my Windows 2000
> NTFS partition (presumably "ntfs5") no problem under NetBSD-current.

If Win2000 acccesses this partition, it's for sure NTFS5.
I guess there's no write support yet for NTFS5?
Do you know whether NetBSD 1.5 is able to do read NTFS5?

BTW, is your NTFS partition primary or logical?
When trying to mount a logical NTFS partition, I get the error ...

dimension# mount -t ntfs /dev/wd1g /mnt/dimension/Data
mount_ntfs: /dev/wd1g on /mnt/dimension/Data: Argument list too long
<date> dimension /netbsd: ntfs_readntvattr_plain: POSSIBLE RUN ERROR
<date> dimension /netbsd: ntfs_readattr_plain: ntfs_readntvattr_plain_
    failed: o: 0, s: 320048
<date> dimension /netbsd: ntfs_readattr_plain: attrib: 0 - 78

I changed the in-core to the correct data (see f):

----- cut here -----
dimension# disklabel wd1
# /dev/rwd1d:
type: unknown
disk: mydisk
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 16383
total sectors: 90069840
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0# microseconds
track-to-track seek: 0# microseconds
drivedata: 0

8 partitions:
#        size   offset     fstype   [fsize bsize   cpg]
  a:   614400 81947565     4.2BSD     1024  8192    16   # (Cyl. 81297*- 81906*)
  b:   614400 82561965       swap                        # (Cyl. 81906*- 82516*)
  c:  8122275 81947565     unused        0     0         # (Cyl. 81297*- 89354)
  d: 90069840        0     unused        0     0         # (Cyl.    0 - 89354)
  e:  6893475 83176365     4.2BSD     1024  8192    16   # (Cyl. 82516*- 89354)
  f: 20482812  2056383       NTFS                        # (Cyl. 2040*- 22360*)
----- cut here -----

PartitionMagic showed the logical partition at:
2.056.383 - 22.539.194 (20.482.811)
[ As per convention, I have to add 1 to the size in NetBSD. ]

This way of proceeding (taking the sectirs from PartitionMagic) works
perfectly for primary NTFS partitions as well as for primary FAT
partitions. Why not for logical partitions?

> The ntfs read support is supposed to be very stable (although I
> have crashed my machine by experimenting with some of the attribute
> access stuff).

Ok.

> According to the mount_ntfs manpage, there is "limited support for
> writing" (although the limitations seem minor),  but it isn't
> extensively tested.  I mount my ntfs partition read-only for now,
> just to be safe.

That's what I intended as well.

Thanks for your help!

Georges

-- 

> Rick

> On 30 Oct 2001, Georges Heinesch wrote:

>> Date: 30 Oct 2001 20:47:12 +0100
>> From: Georges Heinesch <geohei-ml@geohei.lu>
>> To: port-i386@netbsd.org
>> Subject: Does i386 support NTFS5 now?
>>
>> The i386 FAQs say that the filesystem BTFS5 was not supported at
>> the time the FAQ was written. The kernel source says NTFS4
>> experimental.
>>
>> Can someone tell me the current state.
>>
>> I presume ... NTFS4 - read only
>>               NTFS5 - not supported at all ?!
>>
>> Is that correct?
>>
>> --
>> Cu  Georges Heinesch, Luxembourg
>>     geohei@geohei.lu
>>     http://www.geohei.lu
>>     PGP RSA & DH/DSS public key on request and on public servers
>>
>> ... Amiga - Why use Windows, since there is a door ...