Share via

Troubleshooting issues with container size or low disk space

Important

Similar symptoms will appear when the SMB file share has no free space. Be sure to check the file share and setup monitoring to alert when there is less than 20% of free space remaining.

Use the VHD disk compaction feature to shrink the container

In 2210 (2.9.8361.52623) and later versions of FSLogix, VHD disk compaction is enabled by default. Upgrading to the latest version of FSLogix adds the VHD disk compaction operation to the sign out process and reduces the storage inside the user's containers.

Recommendation

Increase SizeInMBs to larger value

In some cases, the user's container is warning of low disk space or has reached the maximum size.

Note

Increasing the SizeInMBs value will affect all users with dynamic disks where configured.

Verify the container size on disk

  1. Check the SizeInMBs setting on the virtual machine.
  2. Locate the user's container on the SMB file share.
  3. Right-click the VHD(x) file and Select Properties.
  4. Compare the Size on disk value with the value from SizeInMBs from the configuration settings.

Increase the container size

FSLogix automatically increases the size of the container when a larger value is used in the SizeInMBs value. Once the disk as been expanded, you can manually mount the container during off-hours and investigate what is consuming the most space. Deleting content from the user's container allows it to compact1 during sign out.

1 VHD disk compaction requires version 2210 (2.9.8361.52623) or later.

Warning

Deleting the wrong data from the user's container could lead to data loss or profile corruption.

Delete local profiles on the virtual machine

Implementing FSLogix profile containers on virtual machines with existing local profiles doesn't automatically remove the local profiles.

Recommendation

Enable the DeleteLocalProfileWhenVHDShouldApply setting.

Warning

Before enabling the DeleteLocalProfileWhenVHDShouldApply setting, users with local profiles must ensure all their data is saved external to their profile to ensure they don't lose the data when it is deleted.

Using redirections.xml exclusions doesn't remove existing profile data

Implementing the redirections.xml file to exclude content for existing FSLogix profiles doesn't remove or delete the exclusion from the user's profile.

Recommendations

  • Delete the user's profile container.
  • Create a script to run after sign in or part of the sign in process to delete the content from the container.

Note

FSLogix doesn't have tools or features to remove this data from the container.

Caution

Deleting a profile or content from a container may lead to unexpected data loss.

Use OneDrive policies to control sync settings