The following table lists the bugs fixed in Data ONTAP 5.3.2.
Bug ID
|
Title
|
|---|
6893
|
Sometimes a disk scrub may not run as scheduled
|
10186
|
CIFS terminate aborted due to a hung CIFS I/O operation
|
10658
|
dump via NDMP can leave inomap buffer locked
|
11454
|
Changes to /etc/symlinks.translations file require cifs shutdown
|
13263
|
CIFS options not preserved after takeover
|
13450
|
Update of code page causes panic on readonly volumes
|
14194
|
Clustered Filer crashes during boot during partner giveback
|
14301
|
Failure to giveback cluster when using /etc/symlink.translations
|
14430
|
Failure to giveback cluster when using /etc/symlink.translations
|
14991
|
Machine check may occur during revert_to operation
|
15123
|
SnapMirror stops transferring when snap create exceeds 3:47
|
15311
|
Aborting a volcopy in progress causes a panic
|
15499
|
Panic when accessing a file that is being closed
|
15717
|
Enabling pcnfsd multiple times can cause system failure
|
15736
|
GPF when using open dialog with Win95 client and Lotus Word Pro
|
15751
|
SnapMirror Transfers couldn't be terminated at times
|
15833
|
Restarted restore accepts tapes in non-sequential order.
|
15849
|
Do not restore a 5.3 dump tape on older systems
|
15927
|
ONTAP 5.3 cannot communicate with locally attached ADIC libraries
|
The following table lists the bugs fixed in Data ONTAP 5.3.1.
Bug ID
|
Title
|
|---|
10469
|
Modifying /etc/sm/monitor or /etc/sm/notify can lead to a crash
|
11602
|
misconfigured DOS CIFS clients can cause filer to hang
|
12424
|
Dump is slow in writing a small qtree to tape.
|
12760
|
System hang caused by a loop in CIFS internal structure lists
|
12833
|
Creation of 24 volumes on a filer will cause a panic during subsequent boot.
|
12841
|
Increase ROOLR instances from 6 to 20.
|
13252
|
F520 and F540 system failures running 5.3 or 5.3.1
|
13258
|
Usermap file not reloaded after cifs terminate/cifs restart
|
13387
|
Network lock manager test result bug.
|
14066
|
cifs.perm_check_use_gid option not persistent
|
14164
|
Possible data inconsistency due to mishandling of write errors.
|
