Rockstor 3.9.2-4 shares unmounted after reboot

I have seen there might be a lot of issue (latest) starting with Rockstor 3.9.2-3 and now /4.
I have a huge problem with my share, which are all not mounted and no clue how I can fix this.
I understood so fare the possibility of a btrfs quota enable, but I don`t know how I could do this.

@mluetz A belated welcome to the Rockstor community.
Easiest way currently until we fine the root cause for quotas not sticking is to manually apply the mount fix as per:

then reboot and then enable quotas on your pool via:

btrfs quota enable /mnt2/Cloud

This work around or it’s kin should be released soon if you are not happy with making the edit as per the pending review pull request commit.
Currently that pr only has a change on line 835 in file /opt/rockstor/src/rockstor/fs/

out, err, rc = run_command(cmd, log=True)


out, err, rc = run_command(cmd, log=True, throw=False)

ie we add a “, throw=False” to the end of the bracketed contents.

Note that this is not as yet a reviewed pull request and I’m pretty sure I’ve missed something but as an emergency fix if that is what is required it worked for me here. Though editing code is not advisable if you are unfamiliar with it.

An alternative is to apply the patch via the following wiki entry:

using the following url:

Please do read that wiki if you are to attempt the patch method, but essentially you (as root) do:

yum install patch
# answer y
curl > pending_1867.patch
patch -d /opt/rockstor/ -p1 < pending_1867.patch

And you should have the change made for you.

Then do the reboot and quota enable bit.

That should at least get your shares back up, else we await the ‘proper’ resolution.

Hope that helps and thanks for your report.

EDIT: As from version 3.9.2-5 the above referenced patch is already applied / included.

@phillxnet I applied the patch and did the following

patch.x86_64 0:2.7.1-8.el7


[root@nas ~]# curl > pending_1867.patch
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1071 0 1071 0 0 2401 0 --:–:-- --:–:-- --:–:-- 2401
[root@nas ~]# ls
anaconda-ks.cfg blkdevMonitor_v2.log pending_1867.patch

patch -d /opt/rockstor/ -p1 < pending_1867.patch
patching file src/rockstor/fs/

Then I rebooted the system and the Shares didn’t show the “unmounted” status.
After that I did the quota enabling stuff again

[root@nas ~]# btrfs quota enable /
[root@nas ~]# btrfs quota enable /mnt2/DATA1
[root@nas ~]# btrfs quota rescan /
quota rescan started
[root@nas ~]# btrfs quota rescan /mnt2/DATA1
ERROR: quota rescan failed: Operation now in progress
[root@nas ~]# btrfs quota rescan -w /mnt2/DATA1
[root@nas ~]# btrfs quota rescan -s /mnt2/DATA1
no rescan operation in progress
[root@nas ~]# btrfs quota rescan -s /
no rescan operation in progress
[root@nas ~]#

But still shows 0 bytes btrfs usage. So we have to wait for the proper fix, right?

And the resizing of these Shares is not possible.

        Traceback (most recent call last):

File “/opt/rockstor/src/rockstor/rest_framework_custom/”, line 41, in _handle_exception
File “/opt/rockstor/src/rockstor/storageadmin/views/”, line 219, in put
update_quota(share.pool, share.pqgroup, new_size * 1024)
File “/opt/rockstor/src/rockstor/fs/”, line 778, in update_quota
out, err, rc = run_command(cmd, log=True)
File “/opt/rockstor/src/rockstor/system/”, line 121, in run_command
raise CommandException(cmd, out, err, rc)
CommandException: Error running a command. cmd = /sbin/btrfs qgroup limit none 2015/2 /mnt2/DATA1. rc = 1. stdout = [‘’]. stderr = [‘ERROR: unable to limit requested quota group: No such file or directory’, ‘’]


Thanks for the feedback and glad you now have your shares auto mounting.

The btrfs_Usage column has in it’s ‘i’ icon: “Current share content including snapshots”
the regular usage at least is now working. Prior to the rescan you would also have zeros in the Usage column as well, so:

Yes. It seems the new docker-ce did a bit of a number here.

Correct, Rockstor depends on quotas and qgoups and these have been disrupted by the new docker to docker-ce move.

We have a seperate issue to address working with quotas disabled where the various side effects are indicated:

So all still in process I’m afraid.