[Info-vax] MOUNT and filesystems, was: Re: RMS record metadata, was: Re: Re; Spiralog, RMS Journaling (was

[Michael Moroney]

lawrencedo99 at gmail.com writes:

>On Monday, June 27, 2016 at 12:44:13 AM UTC+12, Michael Moroney wrote:
>> For the theoretical FAT32 filesystem, you'd need a /FAT32
>> paramater to tell MOUNT this is a FAT32 filesystem, for it to validate the
>> filesystem and launch an ACP to deal with the file system.

>Actually, most of the time in Linux, I don't need to worry about this.
>It is capable of automatically sniffing the filesystem format as part of
>the mount process.

I accidentally produced something that would confound this.  I put an ODS-5
VMS filesystem on a thumb drive.  Later I stuck the drive in a PC and
formatted it.  The PC then saw it as an (empty) FAT-32 drive.  I don't think
I put anything on the drive from the PC. Later I put it back into a VMS
system intending to init it with a VMS file system again but I $ MOUNTED it
with no problem.  All the necessary VMS bits to mount it were still there. I
did an $ ANALYZE/DISK expecting something to be corrupted, yet it passed.  
The VMS file system structure was still there. Back to the PC and it was
still FAT...

What should a file system agnostic MOUNT do with this?  I should try to
see if I can recreate it and see what is in block 0/the GPT blocks ...