Unable to explain zfs referenced after rsync
I have an aging Centos NFS server with a few different ZFS datasets. I've been migrating the data to a newer NFS server using rsync. The new server is also a Centos ZFS host. My issue is that for one dataset, the referenced size is drastically different between old and new servers, and I can't determine the reason.
I'm not using compression or deduplication. I expected the zfs properties to be the same but I noticed the old host does have the following properties enabled for the dataset (devices, exec and setuid). The only other difference I found is the CentOS and ZFS version:
Old host: zfs 0.6.5, centos 7.3, zfs list shows 2.00T referenced
New host: zfs 0.7.2 centos 7.4, zfs list shows 1.29T referenced
To copy the data, I mounted the old export onto the new server and used the following rsync options: -avhH --delete. Looking at df, the inode count is the same but df does show a big difference in used space (1.3T vs 2T). I used 'find' to build a csv of all files in the dataset along with their size and disk usage. The row count and sum of the size column is identical between the two hosts (the size sum is about 1.29TB) The disk usage is only slightly different between the two hosts and matches closely with 1.3T. I've also tried running lsof on the old server to see if there is some unlinked file that was consuming the difference in capacity but nothing was returned as '(deleted)'... any other ideas or suggestions that might explain the difference?
zfs
asked 5 mins ago
useruser
61
add a comment |
I have an aging Centos NFS server with a few different ZFS datasets. I've been migrating the data to a newer NFS server using rsync. The new server is also a Centos ZFS host. My issue is that for one dataset, the referenced size is drastically different between old and new servers, and I can't determine the reason.
I'm not using compression or deduplication. I expected the zfs properties to be the same but I noticed the old host does have the following properties enabled for the dataset (devices, exec and setuid). The only other difference I found is the CentOS and ZFS version:
Old host: zfs 0.6.5, centos 7.3, zfs list shows 2.00T referenced
New host: zfs 0.7.2 centos 7.4, zfs list shows 1.29T referenced
To copy the data, I mounted the old export onto the new server and used the following rsync options: -avhH --delete. Looking at df, the inode count is the same but df does show a big difference in used space (1.3T vs 2T). I used 'find' to build a csv of all files in the dataset along with their size and disk usage. The row count and sum of the size column is identical between the two hosts (the size sum is about 1.29TB) The disk usage is only slightly different between the two hosts and matches closely with 1.3T. I've also tried running lsof on the old server to see if there is some unlinked file that was consuming the difference in capacity but nothing was returned as '(deleted)'... any other ideas or suggestions that might explain the difference?
zfs
asked 5 mins ago
useruser
61
add a comment |
I have an aging Centos NFS server with a few different ZFS datasets. I've been migrating the data to a newer NFS server using rsync. The new server is also a Centos ZFS host. My issue is that for one dataset, the referenced size is drastically different between old and new servers, and I can't determine the reason.
I'm not using compression or deduplication. I expected the zfs properties to be the same but I noticed the old host does have the following properties enabled for the dataset (devices, exec and setuid). The only other difference I found is the CentOS and ZFS version:
Old host: zfs 0.6.5, centos 7.3, zfs list shows 2.00T referenced
New host: zfs 0.7.2 centos 7.4, zfs list shows 1.29T referenced
To copy the data, I mounted the old export onto the new server and used the following rsync options: -avhH --delete. Looking at df, the inode count is the same but df does show a big difference in used space (1.3T vs 2T). I used 'find' to build a csv of all files in the dataset along with their size and disk usage. The row count and sum of the size column is identical between the two hosts (the size sum is about 1.29TB) The disk usage is only slightly different between the two hosts and matches closely with 1.3T. I've also tried running lsof on the old server to see if there is some unlinked file that was consuming the difference in capacity but nothing was returned as '(deleted)'... any other ideas or suggestions that might explain the difference?
zfs
asked 5 mins ago
useruser
61
I have an aging Centos NFS server with a few different ZFS datasets. I've been migrating the data to a newer NFS server using rsync. The new server is also a Centos ZFS host. My issue is that for one dataset, the referenced size is drastically different between old and new servers, and I can't determine the reason.
I'm not using compression or deduplication. I expected the zfs properties to be the same but I noticed the old host does have the following properties enabled for the dataset (devices, exec and setuid). The only other difference I found is the CentOS and ZFS version:
Old host: zfs 0.6.5, centos 7.3, zfs list shows 2.00T referenced
New host: zfs 0.7.2 centos 7.4, zfs list shows 1.29T referenced
To copy the data, I mounted the old export onto the new server and used the following rsync options: -avhH --delete. Looking at df, the inode count is the same but df does show a big difference in used space (1.3T vs 2T). I used 'find' to build a csv of all files in the dataset along with their size and disk usage. The row count and sum of the size column is identical between the two hosts (the size sum is about 1.29TB) The disk usage is only slightly different between the two hosts and matches closely with 1.3T. I've also tried running lsof on the old server to see if there is some unlinked file that was consuming the difference in capacity but nothing was returned as '(deleted)'... any other ideas or suggestions that might explain the difference?
zfs
zfs
asked 5 mins ago
useruser
61
asked 5 mins ago
useruser
61
asked 5 mins ago
useruser
61
asked 5 mins ago
useruser
61
asked 5 mins ago
useruser
61
61
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497592%2funable-to-explain-zfs-referenced-after-rsync%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497592%2funable-to-explain-zfs-referenced-after-rsync%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
