“cache and super generation don't match, space cache will be invalidated” what does this means and how to...
I'm having a little problem trying to grow a btrfs partition in my system, namely:
sudo btrfsck /dev/sdb9
[sudo] password for braiam:
Checking filesystem on /dev/sdb9
UUID: f7e9ac38-5068-4c55-97ab-41430b360d4f
checking extents
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
checking csums
There are no extents for csum range 0-69632
Csum exists for 0-69632 but there is no extent record
found 10204750230 bytes used err is 1
total csum bytes: 10835824
total tree bytes: 80138240
total fs tree bytes: 59863040
total extent tree bytes: 4743168
btree space waste bytes: 21830024
file data blocks allocated: 11097911296
referenced 11097911296
Btrfs v3.16
and I'm trying to fix it. Sadly, the patch that added that check (btw, if it fails it will return a exit code 1) doesn't explain what it is, nor how can we fix it. Now, the partition works seven wonders, but I cannot resize it. Is there a way that I can fix this issue and prevent it from occurring again in the future?
btrfs
asked Oct 6 '14 at 21:08
Braiam
23.1k1976137
add a comment |
I'm having a little problem trying to grow a btrfs partition in my system, namely:
sudo btrfsck /dev/sdb9
[sudo] password for braiam:
Checking filesystem on /dev/sdb9
UUID: f7e9ac38-5068-4c55-97ab-41430b360d4f
checking extents
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
checking csums
There are no extents for csum range 0-69632
Csum exists for 0-69632 but there is no extent record
found 10204750230 bytes used err is 1
total csum bytes: 10835824
total tree bytes: 80138240
total fs tree bytes: 59863040
total extent tree bytes: 4743168
btree space waste bytes: 21830024
file data blocks allocated: 11097911296
referenced 11097911296
Btrfs v3.16
and I'm trying to fix it. Sadly, the patch that added that check (btw, if it fails it will return a exit code 1) doesn't explain what it is, nor how can we fix it. Now, the partition works seven wonders, but I cannot resize it. Is there a way that I can fix this issue and prevent it from occurring again in the future?
btrfs
asked Oct 6 '14 at 21:08
Braiam
23.1k1976137
add a comment |
I'm having a little problem trying to grow a btrfs partition in my system, namely:
sudo btrfsck /dev/sdb9
[sudo] password for braiam:
Checking filesystem on /dev/sdb9
UUID: f7e9ac38-5068-4c55-97ab-41430b360d4f
checking extents
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
checking csums
There are no extents for csum range 0-69632
Csum exists for 0-69632 but there is no extent record
found 10204750230 bytes used err is 1
total csum bytes: 10835824
total tree bytes: 80138240
total fs tree bytes: 59863040
total extent tree bytes: 4743168
btree space waste bytes: 21830024
file data blocks allocated: 11097911296
referenced 11097911296
Btrfs v3.16
and I'm trying to fix it. Sadly, the patch that added that check (btw, if it fails it will return a exit code 1) doesn't explain what it is, nor how can we fix it. Now, the partition works seven wonders, but I cannot resize it. Is there a way that I can fix this issue and prevent it from occurring again in the future?
btrfs
asked Oct 6 '14 at 21:08
Braiam
23.1k1976137
I'm having a little problem trying to grow a btrfs partition in my system, namely:
sudo btrfsck /dev/sdb9
[sudo] password for braiam:
Checking filesystem on /dev/sdb9
UUID: f7e9ac38-5068-4c55-97ab-41430b360d4f
checking extents
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
checking csums
There are no extents for csum range 0-69632
Csum exists for 0-69632 but there is no extent record
found 10204750230 bytes used err is 1
total csum bytes: 10835824
total tree bytes: 80138240
total fs tree bytes: 59863040
total extent tree bytes: 4743168
btree space waste bytes: 21830024
file data blocks allocated: 11097911296
referenced 11097911296
Btrfs v3.16
and I'm trying to fix it. Sadly, the patch that added that check (btw, if it fails it will return a exit code 1) doesn't explain what it is, nor how can we fix it. Now, the partition works seven wonders, but I cannot resize it. Is there a way that I can fix this issue and prevent it from occurring again in the future?
btrfs
btrfs
asked Oct 6 '14 at 21:08
Braiam
23.1k1976137
asked Oct 6 '14 at 21:08
Braiam
23.1k1976137
edited Oct 6 '14 at 21:23
asked Oct 6 '14 at 21:08
Braiam
23.1k1976137
asked Oct 6 '14 at 21:08
Braiam
23.1k1976137
asked Oct 6 '14 at 21:08
Braiam
23.1k1976137
23.1k1976137
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
There's a post on the btrfs list that suggests using the --clear-space-cache option. The following command fixed the same problem for me:
btrfs check --clear-space-cache v1 /dev/sda5
answered Sep 9 '18 at 9:17
Mr. White
1011
add a comment |
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%2f159698%2fcache-and-super-generation-dont-match-space-cache-will-be-invalidated-what-d%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There's a post on the btrfs list that suggests using the --clear-space-cache option. The following command fixed the same problem for me:
btrfs check --clear-space-cache v1 /dev/sda5
answered Sep 9 '18 at 9:17
Mr. White
1011
add a comment |
There's a post on the btrfs list that suggests using the --clear-space-cache option. The following command fixed the same problem for me:
btrfs check --clear-space-cache v1 /dev/sda5
answered Sep 9 '18 at 9:17
Mr. White
1011
add a comment |
There's a post on the btrfs list that suggests using the --clear-space-cache option. The following command fixed the same problem for me:
btrfs check --clear-space-cache v1 /dev/sda5
answered Sep 9 '18 at 9:17
Mr. White
1011
There's a post on the btrfs list that suggests using the --clear-space-cache option. The following command fixed the same problem for me:
btrfs check --clear-space-cache v1 /dev/sda5
answered Sep 9 '18 at 9:17
Mr. White
1011
answered Sep 9 '18 at 9:17
Mr. White
1011
answered Sep 9 '18 at 9:17
Mr. White
1011
answered Sep 9 '18 at 9:17
Mr. White
1011
1011
add a comment |
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f159698%2fcache-and-super-generation-dont-match-space-cache-will-be-invalidated-what-d%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
