[Info-vax] VMS - The new file system. What do we know about it?...

[VAXman- at SendSpamHere.ORG]

In article <4c5b2111-eab3-4b94-bce4-bcd2c9c42371 at googlegroups.com>, clairgrant71 at gmail.com writes:
>On Friday, November 11, 2016 at 12:50:22 AM UTC-5, IanD wrote:
>> Is it time for some more information to trickle through about the new fil=
>e system?
>>=20
>> I listened to the chat put up by the Progress software folks and there wa=
>s some light chatter that let slip a few more details about it's performanc=
>e
>>=20
>> I'm still curious about the new file system
>>=20
>> What else can be let loose about it?
>>=20
>> - Will existing RMS work with it?
>>=20
>> - Will VSI release any of the development tools / utilities used for test=
>ing / creating this file system to the public? (I'm asking because these ty=
>pes of tools/utilities can help other create extensions)
>>=20
>> - Does it working across volumes? (i.e. sharding like abilities)
>>=20
>> - I understand that it's being revamped to 64 bit internals, what are the=
> limits (i.e. How does it compare to this list/ What's similar on this list=
>?)
>>=20
>> - Apart from performance, what other nice things come with it? Better sec=
>urity? snapshots ability? etc etc etc?
>>=20
>> https://en.wikipedia.org/wiki/Comparison_of_file_systems
>>=20
>> Where is there more information about this new toy other than the VSI roa=
>dmap document?
>
>There really isn=E2=80=99t much to say that we haven=E2=80=99t said already=
>.. First, and foremost, all existing file system interfaces will continue to=
> work unchanged - RMS, QIO, etc.
>
>The new FS will not be called ODS-anything. There will be some other name. =
>VMS Advanced File System (VASF) seems to be the leading candidate now.
>
>We do not have any new development tools. Existing VMS applications and reg=
>ression tests are the test vehicles. There has been work done in SDA to sup=
>port the new internal data structures.
>
>The new FS is not being =E2=80=98revamped' to 64bitness. It is 64b by desig=
>n and initial implementation. What is changing is the underlying operating =
>system, namely the I/O Exec and many device drivers to support the expanded=
> LBN field. This is serious work which is in progress now. While we are in =
>there we are also eliminating =E2=80=98disk geometry=E2=80=99 which has not=
> been relevant to the operating system for years.=20
>
>The new FS and 64b LBN work is for improved performance and the support of =
>larger volumes. Other advancements will occur in future releases.
>
>The maximum size of a file will not change. That requires changes to RMS an=
>d that is not happening.
>
>Hope that helps a little.

Whew!  I'm off the hook... for now.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.