Mover not moving and Cache is Read Only

[Slimer]

I was trying to copy some files to a user share that uses the cache and it was bitching that there was not enough space, which is odd because there is plenty of disk space. I just skipped the files last night and went to bed. Today it tells me that the Cache is Read Only and the Docker is Read Only. I tried to use the mover, but it did not move any files. So I rebooted and the Cache is still read only, but the Docker did not start. The Cache has 297GB free, so I'm not sure why the docker did not start, as the cache is only about 80% full.  The Share in question is set to Cache - Yes, although I do have some application shares that are Cache - Only.

 

Any bright ideas?

 

 

[John_M]

It sounds as though the file system on the cache might be corrupted. Diagnostics would reveal more.

[Squid]

1 hour ago, Slimer said:

Any bright ideas?

 

Diagnostics

[yippy3000]

This just happened to me too!

[John_M]

2 hours ago, yippy3000 said:

This just happened to me too!

 

Same answer as above.

[trurl]

2 hours ago, yippy3000 said:

This just happened to me too!

 

5 minutes ago, John_M said:

 

Same answer as above.

Except start your own thread.

[yippy3000]

I did:

 

My whole cache seems to be hosed. BTRFS is doing some serious crunching on something right now after I removed the questionable drive from the cache pool. Will see if that ever comes back up up with a single drive or if I need to rebuild everything (I have backups!). Still don't know if the drive is bad though but suspecting it might be.