So this is what happened from my POV, not sure if I'm describing the root cause tho which could be unrelated.

 

1. I completed filled Cache pool, 0B usable in UI

2. Started mover via UI, mover showing all errors due to fs read only, Docker containers are almost all stopped (presumably crashed due to not able to write into Appdata).

3. stopped array, reboot server, start array

4. Started mover via UI, mover running correctly.

5. Diagonistic generated at this time

6. notices BTRFS error in syslog:  https://pastebin.com/DfrCwigv

 

Everything seems to be working fine currently but still have a couple of questions:

 

1. What caused the original fs read only issue? Cache pool full shouldn't cause fs issue?

2. is my Cache/Array ok now?

3. When I'm trying to generate diagnostic through GUI, I see tons of log prints for individual files I have/had in cache and the GUI crashed. I ended up needing to generate the diag via terminal. Is my server ok? Is there any cleanups I need to do?

 

Thanks!

 

neleh-diagnostics-20241202-1201.zip

24 minutes ago, StylishQuoter said:

What caused the original fs read only issue? Cache pool full shouldn't cause fs issue?

It has been known to do so on btrfs file systems.  You should set the minimum Free Space value for the cache pool to be larger than the biggest file you expect to cache to avoid this.

3 minutes ago, itimpi said:

It has been known to do so on btrfs file systems.  You should set the minimum Free Space value for the cache pool to be larger than the biggest file you expect to cache to avoid this.

This actually reminds me of something..

 

So the reason Cache pool is filled is due to qbit downloading into a share called "data2"

 

data2 actually has (I think) correct setup with a 97.7GB minimum free space in Share Settings.

 

Qbit is set with "Pre-allocate disk space for all files", and it's downloading various medias so there'll be no single file that will be as close to 90GB.

 

How come in this case qbittorrent can still fill the Cache pool?

Edited December 2, 20241 yr by StylishQuoter

Just now, StylishQuoter said:

actually has (I think) correct setup with a 97.7GB minimum free space in Share Settings.

Note I said set the Minimum Free Space value for the pool - not for the share.

3 minutes ago, itimpi said:

Note I said set the Minimum Free Space value for the pool - not for the share.

ah got it.

 

Pool's MFS is currently 0 which is problematic. I'll fix that.

 

For the Share's setting. 

I've always thought that the Share's setting of say 100GB will result in this behavior:

When a disk in Cahce pool (or any pool and array disk that this share is allowed to write into) has less than 100GB available on that disk, then write to that disk will be disallowed and the write will automatically fall back to secondary location (if set), which in my case is set to array.

 

Am I interpreting the setting wrong?

 

thanks.

Edited December 2, 20241 yr by StylishQuoter

7 hours ago, StylishQuoter said:

So this is what happened from my POV, not sure if I'm describing the root cause tho which could be unrelated.

 

1. I completed filled Cache pool, 0B usable in UI

2. Started mover via UI, mover showing all errors due to fs read only, Docker containers are almost all stopped (presumably crashed due to not able to write into Appdata).

3. stopped array, reboot server, start array

4. Started mover via UI, mover running correctly.

5. Diagonistic generated at this time

6. notices BTRFS error in syslog:  https://pastebin.com/DfrCwigv

 

Everything seems to be working fine currently but still have a couple of questions:

 

1. What caused the original fs read only issue? Cache pool full shouldn't cause fs issue?

2. is my Cache/Array ok now?

3. When I'm trying to generate diagnostic through GUI, I see tons of log prints for individual files I have/had in cache and the GUI crashed. I ended up needing to generate the diag via terminal. Is my server ok? Is there any cleanups I need to do?

 

Thanks!

 

neleh-diagnostics-20241202-1201.zip 327.43 kB · 1 download

bumping for question 2 and 3

Thanks!