MFS shell commands and multiple MFS file systems

[pbanta]

With MQX 3.8.1 on a K70 I have two MFS filesystems created in this order:

1.  a: is installed on a RAM disk

2.  c: is installed on an SD card

Through a telnet shell I'm trying to use the MFS shell commands to test file creation/read/write/delete on the SD card.  The only command that seems to recognize the c: filesystem is df.  Other commands, like "create" and "dir" seem to only work with the first file system they find. See the shell output below.

shell> df a:

Free disk space on a:

2033 clusters, 512 bytes each

1016 KB

shell> df b

Error, file system not mounted

shell> df c:

Free disk space on c:

975594 clusters, 4096 bytes each

3902376 KB

shell> create a:test.txt

Error, unable to open file a:test.txt.

shell> create c:test.txt

Error, unable to open file c:test.txt.

shell> create test.txt

shell> dir

TEST.TXT            0 01-01-1980 00:03:16      A TEST.TXT

shell> dir a:

shell> dir c:

shell>

A little background:

I have partitioned and formatted the SD card with MQX/MFS.  I know that in my SD card init function I can create a file successfully.  I can then put the card in a PC and see the file I created.  It's just that from the MQX shell that not all of the MFS shell commands seem to work.  I must have something mis-configured. 

Any ideas?

Paul

[BryGuyH · Accepted solution]

The shell functions don't accept absolute paths. Change directories first using cd to the root directory of the drive you're interested in.

[pbanta]

Bingo.  Thank you so much.

Maybe I spoke too soon...

I can change directory and see files on the SD card using "dir", but I still can't create files.  The file system can't be read-only because I can create a file during the init, but not later.

Message was edited by: Paul Banta

[BryGuyH]

Try to copy or compare two files on the drive to see if at least you can read from it.

[pbanta]

I can't read from a file.  I put an s-record file on the SD card using the card reader attached to my PC.  I tried the "type" command to dump the file and my board crashed.  I'll keep looking.