Anyone working on PFS3 ??

[Karlos]

• TD_GETGEOMETRY and RDB use 32bit unsigned value to store block numbers. The maximum block number they can represent is 2^32 -1 or 4294967295.
• 3TB HDD uses block size of 512(*). The capacity reported is around 3 * 1000 * 1000 * 1000 * 1000 / 512 blocks or 5859375000.
• The value 5859375000 is larger than 4294967295. Thus it cannot be represented with a 32bit unsigned integer data type. Ergo TD_GETMEOMETRY or RDB cannot properly report/handle such device.

You'd actually need 43 bits to represent that value (unsigned). Logarithms FTW ;)

[Karlos]

Actually 33 bits. TD_GETGEOMETRY and RDB use block offsets, not byte offsets.

That's bizarre, I just did the exact same calculation on my CFX-9850G+ and it comes to 33 (as above), but when I did it the first time, it came to 43. I wonder what the hell I missed out? Even neglecting the /512 leaves you with 42 when rounded up

-edit-

I probably got 42 the first time and chucked on an extra bit to ensure sign couldn't be an issue.

[Karlos]

Guys, this is getting stupid, arguing for the sake of argument's sake.

Stick to the topic. The question was, is PFS3 being worked on?

MorphOS: Yes, Harry is working on that.
AROS: ?
OS4: ?
OS3: ?

The drive capacity supported by SFS is irrelevant to this discussion, but to offer my 2p worth, if the maximum number of 512K blocks is represented by a 32-bit integer anywhere in the system, then you are definitely out of luck once that integer wraps round. No amount of shouting is going to change that.

[Karlos]

Currently almost all changes are generic. Of course the OS3 version is directly benefiting from the changes being made. There's only one SVN tree that has everything. Assuming the file system is ported to AROS and OS4 it'd be highly desirable to have those changes in the same SVN as well.

Anyone wishing to contribute should contact mr Pelt over sourceforge.

Sounds good. I was meaning to take a peek myself but I have very little free time presently.