I have recently observed that Drivepool goes into the "Checking" mode about all 24 hours. I noticed that there is no activity on the pool prior to this, and all disks are in standby mode (spin down) too. Additionally, there are no error messages or disk removals/problems reported before this happens. Eventually, Drivepool then wakes up all disks and enters the "Checking" ("Working on the entire pool.") mode, which seems to be aimed at ensuring file duplication consistency as per the notification/feedback bubble in the GUI. However, I have not enabled any folder or file duplication.
As my pool has a size of 35TB and holds millions of files, such a check takes approximately 2 hours, which is unacceptable. Furthermore, this behavior leads to excessive wear on the disks and increases power consumption due to the spinning up of all disks each 24 hours, even when the pool is not used for days.
I would appreciate it if you could clarify whether this is intended behavior and suggest a way to prevent it from occurring automatically. Additionally, if this process is necessary, I would like to be able to schedule it at a more convenient time. Manually canceling the check puts the pool organization into an uncertain state afterward, which is not an ideal solution either.
An upgrade to the latest beta version 2.3.3.1497 didn´t change the situation either.
Question
lvau
Hi,
I have recently observed that Drivepool goes into the "Checking" mode about all 24 hours. I noticed that there is no activity on the pool prior to this, and all disks are in standby mode (spin down) too. Additionally, there are no error messages or disk removals/problems reported before this happens. Eventually, Drivepool then wakes up all disks and enters the "Checking" ("Working on the entire pool.") mode, which seems to be aimed at ensuring file duplication consistency as per the notification/feedback bubble in the GUI. However, I have not enabled any folder or file duplication.
As my pool has a size of 35TB and holds millions of files, such a check takes approximately 2 hours, which is unacceptable. Furthermore, this behavior leads to excessive wear on the disks and increases power consumption due to the spinning up of all disks each 24 hours, even when the pool is not used for days.
I would appreciate it if you could clarify whether this is intended behavior and suggest a way to prevent it from occurring automatically. Additionally, if this process is necessary, I would like to be able to schedule it at a more convenient time. Manually canceling the check puts the pool organization into an uncertain state afterward, which is not an ideal solution either.
An upgrade to the latest beta version 2.3.3.1497 didn´t change the situation either.
Thank you for your prompt assistance.
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.