No replication

When there is no replication, the system metadata has been lost and the file system is basically irrecoverable. You may be able to salvage some of the user data, but it will take work and time. A forced unmount of the file system will probably already have occurred. If not, it probably will very soon if you try to do any recovery work. You can manually force the unmount yourself:

1. Mount the file system in read-only mode (see Read-only mode mount). This will bypass recovery errors and let you read whatever you can find. Directories may be lost and give errors, and parts of files will be missing. Get what you can now, for all will soon be gone. On a single node, issue:

   mount -o ro /dev/fs1

2. If you read a file in block-size chunks and get an EIO return code that block of the file has been lost. The rest of the file may have useful data to recover or it can be erased. To save the file system parameters for recreation of the file system, issue:

   mmlsfs fs1   > fs1.saveparms

   Note: This next step is irreversible!
   To delete the file system, issue:

   mmdelfs fs1

3. To repair the disks, see your disk vendor problem determination guide. Follow the problem determination and repair actions specified.
4. Delete the affected NSDs. Issue:

   mmdelnsd nsdname

   The system displays output similar to this:

   mmdelnsd: Processing disk nsdname
   mmdelnsd: 6027-1371 Propagating the cluster configuration data to all
     affected nodes.  This is an asynchronous process.

5. Create a disk descriptor file for the disks to be used. This will include recreating NSDs for the new file system.
6. Recreate the file system with either different parameters or the same as you used before. Use the disk descriptor file.
7. Restore lost data from backups.