== sanity-pcc test 28: RW-PCC attach should fail when the file has cluster-wide openers ========================================================== 06:11:29 (1713348689)
50+0 records in
50+0 records out
52428800 bytes (52 MB) copied, 0.0572138 s, 916 MB/s
mke2fs 1.46.2.wc5 (26-Mar-2022)
Suggestion: Use Linux kernel >= 3.18 for improved stability of the metadata and journal checksum features.
Discarding device blocks:  1024/51200           done                            
Creating filesystem with 51200 1k blocks and 12824 inodes
Filesystem UUID: 97ec993b-efc0-4c3b-8fc0-3191129f8154
Superblock backups stored on blocks: 
	8193, 24577, 40961

Allocating group tables: 0/7   done                            
Writing inode tables: 0/7   done                            
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/7   done

/tmp/f28.sanity-pcc: Linux rev 1.0 ext4 filesystem data, UUID=97ec993b-efc0-4c3b-8fc0-3191129f8154 (extents) (64bit) (large files) (huge files)
Starting copytool 'agt1' on 'oleg317-client.virtnet' with cmdline 'lhsmtool_posix --archive-format=v1 --hsm-root=/mnt/pcc.d28.sanity-pcc/d28.sanity-pcc --daemon --pid-file=/var/run/lhsmtool_posix.pid --archive 2  "/mnt/lustre"'
multiop /mnt/lustre/f28.sanity-pcc vO_c
TMPPIPE=/tmp/multiop_open_wait_pipe.9543
client oleg317-client.virtnet multiop_bg started multiop_pid=9553
lfs pcc pcc: cannot get WRITE lease, ext 0: Device or resource busy (16)
lfs pcc pcc: cannot get lease: Device or resource busy (16)
attach: cannot attach '/mnt/lustre/f28.sanity-pcc' to PCC with attach ID '2': Device or resource busy
Stopping multiop_pid=9553 (kill 9553 on oleg317-client.virtnet)
multiop /mnt/lustre2/f28.sanity-pcc vO_c
TMPPIPE=/tmp/multiop_open_wait_pipe.7527
lfs pcc pcc: cannot get WRITE lease, ext 0: Device or resource busy (16)
lfs pcc pcc: cannot get lease: Device or resource busy (16)
attach: cannot attach '/mnt/lustre/f28.sanity-pcc' to PCC with attach ID '2': Device or resource busy