Opening a local drive directory appears to hang fm2

[MarkV]

A directory I had been opening daily for years suddenly experienced a problem where it will never open & populate the right pane of files and directories.

My system becomes unresponsive & it requires a hardware reboot to regain control. I can slowly get the task list dialog but it may not populate with all running programs, and the system appears to freeze entirely.

The CPU appears to sit idle. The clock appears to continue on eCenter, when it's not entirely frozen.

The prob.log file is a log of me opening the bad directory. Sometimes when I reboot that file can be empty. And sometimes it has this content.

It will count all the files in the bad directory and total the bytes therein. But that's as far as FM2 gets.

I believe I have let it run for 5 or 10 minutes before giving up at one time. I can always retest this if needed. I have no expectations that waiting longer will yield any different results.

The problem directory is named download-bad. It was originally download, but since the problem started. The rename didn't change the problem, and the problem followed the new directory name.

The directory has one extended attribute .CLASSINFO which appears normal. dl2-bad is another copy of this same directory without the extended attribute .CLASSINFO. The problem is on that directory too. It would seem that a 7z compress of the original directory extracted to a different directory creates the problem on the new directory, It would seem that using xcopy /h/o/t/s/e/r/v to create a third version of the bad directory does not create a directory that exhibits the same problem as the original.

On reboot, JFS will take a while to run through the journal of the drive even though I've never edited or changed a file on that drive during a test of this problem. I see no evidence that JFS fixed anything during that process (meaning I don't know if fixed anything or not). It will perform a similar journal review on the O drive even though it was never referenced.

The dropbox folder is a NetDrive? based control directory but doesn't contain any of my dropbox files.

The W drive is my netdrive base. There is one USB, one samba, & one dropbox drive mapped there.

Z is a temporary ram drive.

M is a dumpfs support drive that is not completely configured yet.

[MarkV]

zip of the FM2 log results when I recreate my problem.

[MarkV]

I will retest any of the things I've noted above to confirm my recollections if you need me to.

[Gregg Young]

Reporter can no longer reproduce this issue. Please feel free to reopen this ticket if it occurs again