Applying the Custom File System Layout

6.12.2 Applying the Custom File System Layout

After you create the JSON file (fslayout.json) containing the custom file system layout, you can apply it to your Exadata database servers during system imaging. In all imaging modes (PXE, NFS, and ISO imaging), fslayout.json is fetched and validated during the initrd stage. If validation succeeds, imaging continues to apply the custom file system layout. If validation fails, imaging stops and prints errors to the serial console so you can fix the file and retry.

The following describes how to apply fslayout.json using each imaging mode.

PXE imaging

Place fslayout.json in the same directory with the preconf.csv file on an NFS or HTTP server that is accessible from the server being imaged using PXE boot.

Instruct initrd to fetch fslayout.json at boot time by adding fs-layout=.../fslayout.json to the PXE append line.

For example:

append initrd=initrd.img root=/dev/ram0 ramdisk_size=150000 \
preconf=http://198.51.100.91/export/exadata_images/config/preconf.csv \
fs-layout=http://198.51.100.91/export/exadata_images/config/fslayout.json

Boot the server using PXE.

NFS-based imaging (using DHCP)

Place preconf.csv and fslayout.json in the same NFS directory as the imaging ISO.

For example:
```
/export/exadata_images/config/
  preconf.csv
  fslayout.json
```
When the imaging process detects preconf.csv, it automatically looks for fslayout.json in the same directory. If found, the file is validated and applied.

ISO-based imaging (no DHCP)

Include preconf.csv and fslayout.json in the ISO image.

For example:

# mkisofs -l -input-charset ascii -o preconf.iso preconf.csv fslayout.json

Attach the ISO as virtual media and boot the server. During boot, initrd reads the ISO, detects fslayout.json, and then proceeds to validate and apply it.

Parent topic: Customizing the Database Server File System Layout