[LU-6848] The Incorrect block size value of the restored files

• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Affects Version/s: Lustre 2.5.3

Environment

1 Server with mounted mgt, mdt, ost targets:
 packages:
    lustre-osd-ldiskfs-2.7.0-2.6.32_504.8.1.el6_lustre.x86_64.x86_64
    lustre-2.7.0-2.6.32_504.8.1.el6_lustre.x86_64.x86_64
    kernel-2.6.32-358.18.1.el6_lustre.x86_64
    kernel-2.6.32-504.8.1.el6_lustre.x86_64
1 Client node:
 packages:
     kernel-2.6.32-358.18.1.el6_lustre.x86_64
     lustre-client-2.7.0-2.6.32_504.8.1.el6.x86_64.x86_64
     lustre-client-modules-2.7.0-2.6.32_504.8.1.el6.x86_64.x86_64

• Severity: 3
• Project: HSM
• Assignee: John Hammond
• Reporter: Pavel Papou (Inactive)

Description

The block size of restored files is equal 1.
Issue is reproduced on virtual environment that consists:
-client based on CentOS release 6.6 (Final)
-server node with mgs, mds, oss roles

Steps to reproduce:
-run the lhsmtool_posix -A 5 -p /tmp/ /mnt/testfs/

• archive file: lfs hsm_archive /mnt/testfs/test_ag
• release file:[client3]# lfs hsm_release /mnt/testfs/test_ag
  [client3 ]# lfs hsm_state /mnt/testfs/test_ag
  /mnt/testfs/test_ag: (0x0000000d) released exists archived, archive_id:5
  [client3 ~]# stat /mnt/testfs/test_ag
  File: `/mnt/testfs/test_ag'
  Size: 5242880 Blocks: 1 IO Block: 4194304 regular file
  Device: 4b620ee0h/1264717536d Inode: 144115205255725082 Links: 1
  .....

• restore file: [client3]# lfs hsm_restore /mnt/testfs/test_ag

[client3 ~]# lfs hsm_state /mnt/testfs/test_ag
/mnt/testfs/test_ag: (0x00000009) exists archived, archive_id:5
[client3 ~]# stat /mnt/testfs/test_ag
File: `/mnt/testfs/test_ag'
Size: 5242880 Blocks: 1 IO Block: 4194304 regular file
Device: 4b620ee0h/1264717536d Inode: 144115205255725082 Links: 1

Actual result:
File's block size=1.

Issue Links

• is related to: LU-3833 HSM POSIX copytool sparse file handling

Comments

[John Hammond]

What you are seeing is likely due to the fact the the POSIX copytool does not attempt to detect or preserve sparseness during archive and restore.

[Joseph Gmitter (Inactive)]

Hi John,

Could you look into this issue - appears to be HSM related.

Thanks.
Joe