[LU-9403] HSM archive copy leaked when dirty file is re-archived to a different archive Created: 26/Apr/17 Updated: 09/May/17 Resolved: 09/May/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.10.0 |
| Fix Version/s: | Lustre 2.10.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | John Hammond | Assignee: | John Hammond |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | hsm | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
FS has archives 1 and 2 at /tmp/arc1 and /tmp/arc2. A dirty archived file can be re-archived to a different archive leaking the original archive copy: m:lustre# echo 111 > f1 m:lustre# lfs hsm_archive --archive=1 f1 m:lustre# lfs hsm_state f1 f1: (0x00000009) exists archived, archive_id:1 m:lustre# m:lustre# lfs hsm_archive --archive=2 f1 ## Ignored since f1 is up to date in archive. m:lustre# lfs hsm_state f1 f1: (0x00000009) exists archived, archive_id:1 m:lustre# cat /tmp/arc1/0004/0000/0401/0000/0002/0000/0x200000401\:0x4\:0x0 111 m:lustre# ls /tmp/arc2 ## Empty. m:lustre# echo 222 > f1 m:lustre# lfs hsm_state f1 f1: (0x0000000b) exists dirty archived, archive_id:1 m:lustre# lfs hsm_archive --archive=2 f1 m:lustre# lfs hsm_state f1 f1: (0x00000009) exists archived, archive_id:2 m:lustre# cat /tmp/arc1/0004/0000/0401/0000/0002/0000/0x200000401\:0x4\:0x0 111 m:lustre# cat /tmp/arc2/0004/0000/0401/0000/0002/0000/0x200000401\:0x4\:0x0 222 |
| Comments |
| Comment by Gerrit Updater [ 27/Apr/17 ] |
|
John L. Hammond (john.hammond@intel.com) uploaded a new patch: https://review.whamcloud.com/26866 |
| Comment by Gerrit Updater [ 09/May/17 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/26866/ |
| Comment by Peter Jones [ 09/May/17 ] |
|
Landed for 2.10 |