https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-6709 Lustre <p>Implement support in rsync to copy the <tt>lustre.lov</tt> xattr (Lustre striping) from the source file and store it on the target file <em>before</em> the file is opened in order to preserve the layout. This should be enabled if the <tt>--xattrs</tt> option is used.</p> <p>This is similar to the work done for the RHEL tar utility to preserve the file layout, which basically removed the filtering of <tt>lustre.<b></tt> xattrs and then restored all xattrs at the time the file is created. Note that the <tt>lustre.lov</tt> and <tt>trusted.lov</tt> xattrs are aliases for the same xattr, because non-root users cannot access the <tt>trusted.</b></tt> xattrs, but this should be opaque to tar.</p> <p>Any failure to apply <tt>lustre.<b></tt> or <tt>trusted.</b></tt> xattrs on the target file should not be considered a fatal error, in case rsync is writing to a non-Lustre filesystem.</p> LU-6709

modify rsync utility to copy Lustre file striping

Improvement Minor Open Unresolved WC Triage Andreas Dilger Wed, 10 Jun 2015 22:04:27 +0000 Thu, 11 Jun 2015 01:16:13 +0000 0 5 <p>As Malcolm pointed out recently, <a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=kolano" class="user-hover" rel="kolano">kolano</a> published a similar patch for rsync (and a few other common tools) here: <a href="http://people.nas.nasa.gov/~kolano/projects/retools.html" class="external-link" target="_blank" rel="nofollow noopener">http://people.nas.nasa.gov/~kolano/projects/retools.html</a><br/> However, instead of copying existing striping information, his approach is to determine appropriate striping for files based on file size, which might be more appropriate for general purpose use.</p> <p>I'm not against something like retools (which looks interesting), but it seems unlikely to me that changes like that would be accepted into the upstream tools. The tar change was accepted upstream because it didn't really have anything Lustre specific about it - it just changed the restore of xattrs to the start rather than the end.</p> <p>Another option that may be beneficial for Lustre in the vein of retools, but is totally generic, is to use fallocate() to have rsync/tar/gzip/bzip2 specify the file size before starting the restore. That would give Lustre a chance to know what the total file size is and make an appropriate striping decision, and then Lustre and all other file systems can preallocate this space on disk to avoid fragmentation. </p> Development Rank 1|hzxfh3: Rank (Obsolete) 9223372036854775807