Fix the

Applies to

Product: Server Migration Center (SMC)
Scenario: Migration fails with an fstab-related error

Symptom

A migration job in SMC fails with the following error:

Deprecated XFS mount options present in FSTAB

Cause

The /etc/fstab file on the migration source contains deprecated XFS mount options that were removed from the Linux kernel in version 4.0 or 4.19. After migration, the XFS file system fails to mount on the destination Elastic Compute Service (ECS) instance because the target kernel does not recognize these options.

Deprecated XFS mount options

Mount option	Removed in
`nodelaylog`	kernel 4.0
`delaylog`	kernel 4.0
`ihashsize`	kernel 4.0
`irixsgid`	kernel 4.0
`osyncisdsync`	kernel 4.0
`osyncisosync`	kernel 4.0
`nobarrier`	kernel 4.19
`barrier`	kernel 4.19

For the full list of current XFS mount options, see xfs(5) - Linux manual page.

Solution

Remove or replace the deprecated mount options in /etc/fstab, then retry the migration.

Step 1: Connect to the source server

Connect to the ECS instance whose operating system you want to migrate. For more information, see Connect to a Linux instance by using a password or key.

Step 2: Edit `/etc/fstab`

Open /etc/fstab in a text editor:
```
   vim /etc/fstab
```
Press the I key to enter Insert mode. Locate the XFS file system entry. The mount options appear in the fourth column. For example:
```
   /dev/vdb1  /data  xfs  nobarrier,noatime  0  0
```
Remove any deprecated mount options listed in the table above. Keep only the valid options. For the example above:
```
   /dev/vdb1  /data  xfs  noatime  0  0
```
If all mount options in the fourth column are deprecated, replace them with defaults:
```
   /dev/vdb1  /data  xfs  defaults  0  0
```
Press the ESC key, enter :wq, and then press the ENTER key to save and close the file.

Step 3: Verify the mount configuration

Run the following command to mount all file systems defined in /etc/fstab:

mount -a

If this command completes without errors, the configuration is correct.

Step 4: Retry the migration

Run the SMC client and retry the migration job. For more information, see Run the SMC client.