Anyone working on PFS3 ??

[gertsy]

It would be very nice if he would accomplish this! :biglaugh: But the chances are really zero.
Maybe some other smart person will make such a program...

Dave Hanie is a hardware engineer not a magician damn it Jim.

[AmiDude]

Dave Hanie is a hardware engineer not a magician damn it Jim.

He did make DiskSalv though... He doesn't have to be a magician for that!

[orange]

I don't need to test it. I know it's technically impossible to partition a >2TB drive reporting 512 byte block size (that's what current drives do due to compatibility reasons). These drives will report more than 2^32-1 sectors and you cannot fit such number into 32bit data type (used by both TD_GETGEOMETRY and RDB itself).

hm, I wonder if that compatibility mode could be turned off;
because, with 4096 byte blocks, the limit would be 8*2Gb ?

I mean at least some new OS/software would be able to use largest drives without requiring new controllers?

plus the drives might be a bit faster.

[Cosmos Amiga]

Pfs3ds_000 v18.4

 - 68000+
 - Compiled with SAS/C 6.58
 - Last version by Harry Sintonen


Here : http://eab.abime.net/showpost.php?p=762029&postcount=96

[Cosmos Amiga]

@Piru

This new version of Pfs3 give uninitialised partitions beyond the 4 Gb border : "Write Error -3 on block 0" when used with the scsi 43.45 (Boing Bag 2) burned on eprom...

I'll try with the v18.5 on Aminet, but I think I'll get the same result !




!

[Cosmos Amiga]

v18.3ds on Aminet => All partitions are working fine
v18.4ds => All partitions beyond the 4 Gb border are uninitialised
v18.5ds => All partitions beyond the 4 Gb border are uninitialised


(CF 16 Gb on A600 with ACA030 used with the scsi v43.45 into an eeprom)

[Piru]

@Cosmos

Use the bug tracker, please. Also, please include output from check4gb.

[Cosmos Amiga]

I cannot register on SourceForge : "Username must begin with a letter"...




check4gb

[Piru]

@Piru

This new version of Pfs3 give uninitialised partitions beyond the 4 Gb border : "Write Error -3 on block 0" when used with the scsi 43.45 (Boing Bag 2) burned on eprom...

For whatever reason this device doesn't appear to have a working HD_SCSICMD interface (DirectSCSI). This is indicated by the Check4GB output as well (no S).

This doesn't explain why old PFS3 supposedly works. I suspect some problem with your testing method rather than that the old PFS3 would actually be working.

[Cosmos Amiga]

Unbelievable... The v18.3 is working fine, YOU made some changes and bump to v18.4...

v18.4 give now partitions uninitialised beyond the 4 Gb border, and it's ME the culprit... Whaou...


Whaou, whaou, whaou...

[Piru]

Unbelievable... The v18.3 is working fine, YOU made some changes and bump to v18.4...

I did not bump the filesystem version.

Code: [Select]

    2   michielp #define REVISION "18.4"
     2   michielp #define REVDATE  "11.09.99"
     2   michielp #define REVTIME  "18:02:53"
     2   michielp #define AUTHOR   "Michiel Pelt"
     2   michielp #define VERNUM   18
     2   michielp #define REVNUM   4


v18.4 give now partitions uninitialised beyond the 4 Gb border, and it's ME the culprit...

v18.5 is the official PFS3 without any of my changes. If it fails then I can't see how this could be my fault.

Finally: The svn version is a work in progress. Anyone using this snapshot is doing so with the knowledge that things may be in flux. I strongly suggest you avoid using random svn builds and rather use the official v18.5 for now.

[Piru]

used with the scsi 43.45 (Boing Bag 2)

Really? Isn't that 43.45 some unofficial patch from aminet?
http://aminet.net/package/driver/media/SCSI4345p

Code: [Select]

THIS PATCH IS COMPLETELY UNOFFICIAL. IT HAS NOT BEEN APPROVED BY AMIGA INC.
OR BY HAAGE & PARTNER. BY USING IT ON YOUR SYSTEM, YOU ACCEPT THE ENTIRE
RISK AS TO ITS QUALITY AND PERFORMANCE.

[Cosmos Amiga]

I believed the src version on Aminet was v18.3... My mistake, it's the v18.4...

When coders add some new changes on some sources, they bump the version or the revision numbers...

Anyway, the v18.4 on Aminet compiled with SAS/C 6.58 give the same error than the last files updated on SourceForge...

[ChaosLord]

So the conclusion is that this is not Piru's fault.
Correct?

[Cosmos Amiga]

Yes !

Pfs3 versions uploaded on Aminet in 2011 :

- binaries => v18.3
- sources => v18.4

[Piru]

When coders add some new changes on some sources, they bump the version or the revision numbers...

The source committed to SVN was for earlier PFS3 version (iirc PFS3 5.2 aka 18.4), since the very last src were lost. The source code has since been brought up to date and the current SVN should match the PFS3 5.3 (18.5) in features. See here: http://sourceforge.net/tracker/?func=detail&aid=3285730&group_id=532591&atid=2163218

The SVN "trunk" version is work in progress (and as such the revision hasn't been touched yet). The SVN trunk version isn't guaranteed to be stable at any given moment. Obviously there's nothing we can do to prevent anyone from releasing snapshot builds, but I would appreciate it if any such release would be accompanied with a warning about it being only a snapshot build.