4-30 Dell PowerVault 720N, 740N, and 760N System Administrator and Command Reference Guide
:KHUHWR/RRNIRU'DWDEDVH)LOH9HULILFDWLRQ,QVWUXFWLRQV
See the documentation for your specific database software for instructions about
examining database file validity.
(UURU0HVVDJH([DPSOH
When you enable nvfail and the filer encounters NVRAM errors, the message sent
to the console and the /etc/messages file looks like the following:
$OOILOHKDQGOHVKDYHEHHQLQYDOLGDWHGGXHWRSUHYLRXV195$0
IDLOXUH
$OOILOHV\VWHPVPXVWEHUHPRXQWHGE\WKHFOLHQWV
If you created an nvfail_rename file, you receive an additional message:
5HQDPLQJILOHVLQHWFQYIDLOBUHQDPH
QYIDLOBUHQDPHROGBILOHBQDPHQHZBILOHBQDPH

7DEOH(QDEOLQJWKHQYIDLO2SWLRQ

,I 7KHQ
The filer detects no NVRAM errors File service starts normally.
The filer detects NVRAM errors and
you use the optional
nvfail_rename file
a) The filer returns a stale filehandles
(ESTALE) error to NFS clients trying
to access the database, causing the
application to hang, crash, or shut
down, and sends an error message to
the filer console and log file.
b) The filer renames database files
specified in the nvfail_rename file
by appending .nvfail to the original
file name, making those files unavail-
able to both CIFS and NFS clients.
The filer detects NVRAM errors and
you do not use the optional
nvfail_rename file
a) The filer returns a stale filehandles
(ESTALE) error to NFS clients trying
to access the database, causing the
application to hang, crash, or shut
down, and sends an error message to
the filer console and log file.
b) No database files are renamed.
When the application restarts, files
are available to both CIFS and NFS cli-
ents, even if you have not verified
that they are valid.