Veritas Storage Foundation Release Notes
Veritas Storage Foundation⢠Release Notes: HP-UX - Symantec Veritas Storage Foundation⢠Release Notes: HP-UX - Symantec
58 Storage Foundation Release Notes Known issues ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ vx_event_wait vx_delay2 vx_ireuse vx_iget vx_ialloc vx_dirmakeinode vx_dircreate vx_dircreate_tran vx_do_create vx_create1 vx_create0 vx_create Workaround: There is no workaround for this issue. vxresize fails while shrinking a file system with the "blocks are currently in use" error (2437138) The vxresize shrink operation may fail when active I/Os are in progress on the file system and the file system is being shrunk to a size closer to its current usage. You see a message similar to the following example: UX:vxfs fsadm: ERROR: V-3-20343: cannot shrink /dev/vx/rdsk/dg1/vol1 - blocks are currently in use. VxVM vxresize ERROR V-5-1-7514 Problem running fsadm command for volume vol1, in diskgroup dg1 Workaround: Rerun the shrink operation after stopping the I/Os. Debug kernel panics with spin_deadlock_failure panic string while enabling auxiliary swap space (2521695) The debug kernel panics with a spin_deadlock_failure panic string while enabling auxiliary swap space. The following example is of the relevant part of the stack trace: spinlock+0x50 vx_inactive+0x140 vx_vn_inactive+0x30
Storage Foundation Release Notes Known issues 59 vn_rele_inactive+0x1e0 vx_dnlc_getpathname+0x12b0 System hang when using ls, du and find (2584531) The system sometimes hangs when using the ls, du, or find commands. The hang occurs in the following stack: schedule_timeout vx_iget vx_dirlook vx_lookup do_lookup do_path_lookup Workaround: There is no workaround for this issue. Expanding a 100% full file system can cause a panic (2599590) Expanding a 100% full file system can cause a panic with the following stack trace: bad_kern_reference() $cold_vfault() vm_hndlr() bubbledown() vx_logflush() vx_log_sync1() vx_log_sync() vx_worklist_thread() kthread_daemon_startup() Workaround: There is no workaround for this issue. Not all partitioned directory entries display after exporting a VxFS file system over an HP-UX NFS server (2623412) After you export a VxFS file system over an HP-UX NFS server, the file system might not list all of the entries in partitioned directories if accessed by NFS clients. This issue is specific to HP-UX NFS servers and VxFS disk layout Version 8 and later. Workaround: There is no workaround for this issue.
- Page 7 and 8: Storage Foundation Release Notes Th
- Page 9 and 10: Storage Foundation Release Notes Ab
- Page 11 and 12: Storage Foundation Release Notes Ch
- Page 13 and 14: Storage Foundation Release Notes Ch
- Page 15 and 16: Storage Foundation Release Notes Ch
- Page 17 and 18: Storage Foundation Release Notes Ch
- Page 19 and 20: Storage Foundation Release Notes Ch
- Page 21 and 22: Storage Foundation Release Notes Ch
- Page 23 and 24: Storage Foundation Release Notes Ch
- Page 25 and 26: Storage Foundation Release Notes Ch
- Page 27 and 28: Storage Foundation Release Notes Ch
- Page 29 and 30: Storage Foundation Release Notes Sy
- Page 31 and 32: Storage Foundation Release Notes Fi
- Page 33 and 34: Storage Foundation Release Notes Fi
- Page 35 and 36: Storage Foundation Release Notes Fi
- Page 37 and 38: Storage Foundation Release Notes Fi
- Page 39 and 40: Storage Foundation Release Notes Fi
- Page 41 and 42: Storage Foundation Release Notes Fi
- Page 43 and 44: Storage Foundation Release Notes Fi
- Page 45 and 46: Storage Foundation Release Notes Kn
- Page 47 and 48: Storage Foundation Release Notes Kn
- Page 49 and 50: Storage Foundation Release Notes Kn
- Page 51 and 52: Storage Foundation Release Notes Kn
- Page 53 and 54: Storage Foundation Release Notes Kn
- Page 55 and 56: Storage Foundation Release Notes Kn
- Page 57: Storage Foundation Release Notes Kn
- Page 61 and 62: Storage Foundation Release Notes Kn
- Page 63 and 64: Storage Foundation Release Notes Kn
- Page 65 and 66: Storage Foundation Release Notes Kn
- Page 67 and 68: Storage Foundation Release Notes Kn
- Page 69 and 70: Storage Foundation Release Notes Kn
- Page 71 and 72: Storage Foundation Release Notes Kn
- Page 73 and 74: Storage Foundation Release Notes So
- Page 75 and 76: Storage Foundation Release Notes Do
- Page 77 and 78: Storage Foundation Release Notes Do
58<br />
<strong>Storage</strong> <strong>Foundation</strong> <strong>Release</strong> <strong>Notes</strong><br />
Known issues<br />
■<br />
■<br />
■<br />
■<br />
■<br />
■<br />
■<br />
■<br />
■<br />
■<br />
■<br />
■<br />
vx_event_wait<br />
vx_delay2<br />
vx_ireuse<br />
vx_iget<br />
vx_ialloc<br />
vx_dirmakeinode<br />
vx_dircreate<br />
vx_dircreate_tran<br />
vx_do_create<br />
vx_create1<br />
vx_create0<br />
vx_create<br />
Workaround: There is no workaround for this issue.<br />
vxresize fails while shrinking a file system with the "blocks are<br />
currently in use" error (2437138)<br />
The vxresize shrink operation may fail when active I/Os are in progress on the<br />
file system and the file system is being shrunk to a size closer to its current usage.<br />
You see a message similar to the following example:<br />
UX:vxfs fsadm: ERROR: V-3-20343: cannot shrink /dev/vx/rdsk/dg1/vol1 -<br />
blocks are currently in use.<br />
VxVM vxresize ERROR V-5-1-7514 Problem running fsadm command for volume<br />
vol1, in diskgroup dg1<br />
Workaround: Rerun the shrink operation after stopping the I/Os.<br />
Debug kernel panics with spin_deadlock_failure panic string<br />
while enabling auxiliary swap space (2521695)<br />
The debug kernel panics with a spin_deadlock_failure panic string while<br />
enabling auxiliary swap space. The following example is of the relevant part of<br />
the stack trace:<br />
spinlock+0x50<br />
vx_inactive+0x140<br />
vx_vn_inactive+0x30
Change language