| DESCRIPTION The Early Release Patch (ERP) announced in
this Engineering Advisory (EA) fixes four potential AdvFS hangs.
Two hangs have been fixed previously in kit
T64KIT0025601-V51BB26-E-20050513. The kit announced here
combines the previous fixes with fixes for two additional 5.1B-3
AdvFS hangs.
Descriptions of the hangs follow. (Hangs 1 and 2 are new; hangs 3
and 4 have been fixed previously.)
1. AdvFS clone mounted and a file is being extended using Direct
I/O (new)
This hang could be seen by customers with an AdvFS clone mounted and
a file is being extended using Direct I/O. A forced crash during the
hang produces the following stack trace.
0 thread_block
1 sleep_prim
2 mpsleep
3 insert_actRange_onto_list
4 cow_get_locks
5 bs_cow_pg
6 bs_cow
7 bs_pinpg_clone
8 bs_pinpg_ftx
9 copy_and_del_frag
10 fs_write_add_stg
11 fs_write
12 msfs_write
13 vn_pwrite
14 prwuio
15 pwrite
16 syscall
17 _Xsyscall
2. AdvFS clone mounted and a file is being truncated using Direct
I/O (new)
This hang could be seen by customers with an AdvFS clone mounted and
a file is being truncated using Direct I/O. A forced crash during
the hang produces the following stack trace.
0 thread_block
1 sleep_prim
2 mpsleep
3 insert_actRange_onto_list
4 fs_setattr
5 msfs_setattr
6 cfs_comm_setattr
7 cfscall_setattr
8 cfs_setattr
9 vn_open
10 copen
11 syscall
12 _Xsyscall
3. Use of vfast or defragment on an AdvFS domain in a cluster
(fixed previously)
This hang can be seen by customers running vfast or defragment on an
AdvFS domain, if the system is in a cluster. A forced crash during
the hang produces the following two stack traces.
0 thread_block
1 sleep_prim
2 mpsleep
3 insert_actRange_onto_list
4 msfs_flush_and_invalidate
5 cfs_comm_open
6 cfscall_open
7 cfs_open
8 vn_open
9 copen
10 syscall
11 _Xsyscall
and
0 thread_block
1 lock_write2 cfs_condio_cc_excl_mode_enter
3 migrate_get_clu_locks
4 migrate_normal
5 mig_migrate
6 bs_migrate
7 ss_vd_migrate
8 ss_move_file
9 ss_work_thd_pool
4. AdvFS clone mounted and at least two threads doing memory
mapping to the same file (fixed previously)
This hang can be seen by customers with an AdvFS clone mounted and
at least two threads doing memory mapping to the same file. A forced
crash during the hang produces the following two stack traces.
0 thread_block
1 lock_read
2 cow_get_locks
3 bs_cow_pg
4 bs_cow
5 bs_pinpg_clone
6 bs_pinpg_get
7 msfs_getpage
8 u_vp_fault
9 u_map_fault
10 vm_fault
11 trap
12 _XentMM
and
0 thread_block
1 lock_write
2 msfs_mmap
3 smmap
4 syscall
5 _Xsyscall
|
