[Coco] NitrOS-9 Directory Issue

[Mike Rowen]

I am using a CoCo 3 with 512k, 6309 and two floppy drives. I am booting from
"stock" images that I grabbed from the NitrOS-9 page.
That's NitrOS-9/6309 Level 2 V3.2.9

I created a directory called /D0/MIKE and then created some files in this
directory with both build and edit. One of the files contained a list of
edit commands that I intended
to redirect as an input file for the EDIT command. However, I failed to
include a "q" as the last line of this file, so when I
ran this:

edit file1 < editcommands  , EDIT worked fine until it reached the end of
the command list where I had omitted the "q" to quit and save.

At this point, the screen continually scrolled the E: prompt from EDIT with
the message "MACRO IS OPEN". This was run from /term so there
was no way to break out of this loop except to hit reset and reboot.

After this event,  if I attempt to edit any file in this directory, I get an
ERROR #218 (File Already Exists). Its not too useful to have an
editor that won't work with existing files. :)

I can create new files in /D0/MIKE with EDIT, but if I exit EDIT with a "q"
and then try to edit that new file, I'll get the ERROR #218 again.

I can edit files in other directories fine. So, I created a new directory
called /D0/NEWSTUFF and copied files from /D0/MIKE and I could then edit
them without issue.

Whatever is happening here seems to be isolated to the /D0/MIKE directory. I
know that I had to reboot with an open file in play. I'm interested in
figuring out if the
directory is corrupted or in some odd state because of the messed up EDIT
session.

I ran dcheck /d0 and it reports 18 clusters in allocation map but not in
file structure. I couldn't readily find much info on dcheck to even know if
this means this is an issue or normal.
Just looking for any insights from the experts here on the best strategy for
troubleshooting and correcting the problem. The bute force way is probably
to delete the directory and
start fresh, but this seems like a good learning opportunity. :)

Cheers,
-Mike Rowen