Jump to content

6.11.5 issue with btrfs subvolume growing after replacing cache drive


Recommended Posts

I previously had a 500 GB cache drive (single disk pool) and replaced it with a 1 TB drive. 

 

I shut down docker and virtual machines, set shares to Cache: Yes and invoked mover. After mover finished I took the 500 GB drive out and put the 1 TB drive in. I flipped the shares to Cache: Prefer and invoked mover. Mover has been going for over 24h now and it has somehow managed to move over 500 GB of data back to the 1 TB drive - which makes no sense since the 500 GB drive was only about 45% full to begin with.

 

Any idea why this is occurring? It appears to be related to btrfs subvolumes - it has been moving them for almost the entire time and somehow growing them to bigger than they were previously.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...